No luck getting my Lemmy instance up and running, is this a good place to get some help?
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.
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?
If you're looking to set up a server quickly and easily, check out Lemmy Easy Deploy by ubergeek77. Just change the host name to your domain name in the config file and you're good to go.
If you're trying to access your home server from the internet, I recommend a cloudflare tunnel. Let me know if you need assistance! My dms are open
Dude, I've been having the exact same problem for the last few days and have been banging my head against the wall with it too. Thanks for posting this, I'm eagerly awaiting the responses you get
If you're running a separate reverse proxy that handles HTTPS requests, and don't mind the app communicating with your reverse proxy on port 80, you can turn off Caddy TLS. That's what ultimately made everything work for me, and how I'm posting from my own instance now.
Came here to say the Ansible method is much, much easier than manual with Docker and from scratch.
I was banging my head for hours fixing all kinds of errors. I finally gave up and went the Ansible method and was able to get to the Lemmy login page within 5 minutes.
OP, if you decide to go the Ansible method, you’ll need to setup a separate server and install Ansible on it. From there clone the Git repo and modify the files the instructions tell you to. Make sure the two servers can talk to each other via SSH. Lastly, run the “ansible-playbook -i inventory/hosts lemmy.yml” command and your Lemmy instance should be online within a few minutes.
Honestly, my advice is to setup two temp VPS’s with Ubuntu on them. Don’t lock them down too tight and play with the Ansible deployment. Once you get a feel for how everything goes, you can redeploy the VPS’s and set them up properly with proper security.
there are also instructions to spin up ansible within a container on the host so you don't have to install anything else on the target and use only 1 machine. I havent tried it though.
ansible is an automation tool, it does all the things you would do manually, ssh, run commands, etc etc. The files provided bascially have it generate scripts that get pushed to the host and run. it can be run on a remote host or run on the machine you want to install on. either works.
I would imagine you could simply paste your domain and ports into those and get up and running. I can also provide the entire docker compose file with my secret stuff removed if you think that would be helpful
Oh I see your issue, you need to replace anything in curly braces with actual values. I'm away from my pc right now but I'll give you the correct image name shortly....
I recommend using the docker images directly. As you see, the ansible scripts are basically another abstraction layer used to build the docker containers and their configs (and has string substitutions like {{some_string}} which are not valid for docker-compose.yml). Some will disagree but I feel ansible adds unnecessary complexity to deploying lemmy containers.
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
# 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.
It assumes that you’ve got a Traefik gateway setup on a separate network already, which should be just one docker compose away. Hope this helps point in the right direction!
Hi there! This sounds like you might just have a typo in your docker-compose.yml file. It might be helpful if you posted your docker-compose.yml contents here (be sure to remove any sensitive information).
Line 26 of my docker-compose.yml file is the volume block/map for letsencrypt. Did you perhaps mix tabs and spaces, or have one too many spaces in your indentations, in your yaml file? That's a no-no...
Personally, I setup my instance using the same guide as you, opting for the docker containers. There were definitely a few pitfalls to deal with.