Selfhosted

40329 readers

383 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

-3

No luck getting my Lemmy instance up and running, is this a good place to get some help? (lemmy.world)

submitted 1 year ago by IchNichtenLichten@lemmy.world to c/selfhosted@lemmy.world

6 comments fedilink hide all child comments

I'm not exactly a linux beginner but I'm far from an expert and I could use some pointers. I have a domain and a VPS through Namecheap, I chose Ubuntu 20.04 LAMP and I've tried several guides to get this working but something always goes wrong sooner or later.

My latest attempt is to follow along with this guide: https://join-lemmy.org/docs/administration/install_docker.html

No errors until the docker-compose up -d command, then

ERROR: yaml.constructor.ConstructorError: while constructing a mapping in "./docker-compose.yml", line 26, column 12 found unhashable key in "./docker-compose.yml", line 26, column 13

which leads to image: {{ lemmy_docker_image }}

I guess I could start over with a different guide but I'm just chasing my tail at this point. Could any kind soul suggest where to go from here?

you are viewing a single comment's thread
view the rest of the comments

[–] SeaMauFive@lemm.ee 0 points 1 year ago (1 children)

I skimmed the guide you sent and the top says that the portions in brackets are placeholders and need to be replaced with real values. If you change {{ lemmy_docker_image }} to be the name of the image to use dessalines/lemmy:0.18.0 for example, do you get further

[–] IchNichtenLichten@lemmy.world 0 points 1 year ago

I didn't do that because I'm apparently a moron :)

I'm trying with

dessalines/lemmy:0.18.0 dessalines/lemmy-ui:0.18.0

In this section

  # actual and only port facing any connection from outside
  # Note, change the left number if port 1236 is already in use on your system
  # You could use port 80 if you won't use a reverse proxy
  - "80:8536"

this fails with Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use

I tried 8080 instead and got no errors but I wasn't able to load the Lemmy page.

I can now get the "Apache2 Ubuntu Default Page - It works!" So that's something.