This is a slow learning process for me and some of you already helped me a lot to figure out reverse proxies in general. However, I’m not there yet … so:

How can I set up Lemmy (and Mastodon down the line) behind my existing reverse proxy? I’m trying to install from docker and the docker compose files come with templates for reverse proxy configuration, but these are (probably) only valid, if I’m installing on a dedicated server with nothing else running there.

I tried commenting out the stuff for the proxy configuration, but I can’t seem to get it to work. The Lemmy install ends up with 5 docker containers (lemmy, lemmy-ui, …) and I’m not sure which of them need to be adressed by my proxxy setup. Just getting the lemmy-ui container addressed by nginx didn’t work out.

I’m probably way out of my league with what I’m trying here, but if any of you have some useful tips I’d be really grateful.

  • Matthew@lemmy.piperservers.netEnglish
    1·
    1 year ago

    You can use the FQDN of your Lemmy instance in the nginx.conf file. I’ve uploaded my files to a gist here as an example.

    You should be able just to replace any mention of lemmy.mydomain.com with your FQDN of your Lemmy instance and replace any your-postgres-password with your real Postgres password. You must also set your SMTP provider settings in the email section of config.hjson (I use Brevo). In the docker-compose.yml file, you can change which port you want to map from the host; I used 8976 in mine. Then just point your internet-facing reverse proxy to the host and whichever port you chose.

    I’m not using Ansible to automate it at all. I’m just updating the files manually, as needed, and doing docker compose commands. I’m using Docker volumes to persist the data on them, so feel free to change any of those basic things you want.

    • Solvena@lemmy.worldOPEnglish
      1·
      1 year ago

      thanx! I got it running now, not sure yet if federation is working, but at least I have my instance up and could register admin + standard user :)