10
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Jun 2023
10 points (100.0% liked)
Selfhosted
40246 readers
1186 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
I would recommend you ditch the second nginx layer. It's a waste of resources and it can cause a multitude of issues if the configuration isn't done correctly.
docker-compose.ymlfile and copy Lemmy's nginx config into your system's nginx config (e.g./etc/nginx/).lemmyexternalproxynetwork, deleteinternal: trueon thelemmyinternalnetwork (required to enable port forwarding) and add port forwards to thelemmyandlemmy-uidocker services. Here's what that would look like: https://www.diffchecker.com/vjfEFuz6/docker-compose.ymlfile for theproxyservice to bind to whatever your external facing IP is.