this post was submitted on 22 Jun 2023
4 points (100.0% liked)

Self Hosted - Self-hosting your services.

11345 readers
2 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

Important

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

Cross-posting

If you see a rule-breaker please DM the mods!

founded 3 years ago
MODERATORS
 

I know everyone is still fiddling around with setup, but I have tried and tried to get my own compose working but have had no luck. If anyone can share their working compose, it would be really helpful. I have an existing Nginx Proxy Manager container serving as my reverse proxy, so I don’t want to install the nginx container in the sample compose either. Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] thomas@lemmy.zell-mbc.com 1 points 1 year ago

<<so I don’t want to install the nginx container in the sample compose either>> Thought the same initially but it turned out both nginx instances are required. I have a working setup with an installed nginx instance + certbot and an almost unmodified docker-compose.yml The modifications I made were changing container names (so they fit my standard) and the http port

The lemmy documentation https://join-lemmy.org/docs/administration/install_docker.html recommends the following location block for the installed nginx:

  location / {
       proxy_pass http://localhost:LEMMY_PORT;
       proxy_set_header Host $host;
       include proxy_params;
}

This did not work for me! I had to comment the proxy_set_header line to make things work. With it I run into an error 400.