view the rest of the comments
Selfhosted
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:
- 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!
The default Lemmy nginx config should handle websockets properly. Are you putting it behind a second nginx layer?
I might be. See my response here: https://lemmy.world/comment/101425
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.yml
file and copy Lemmy's nginx config into your system's nginx config (e.g./etc/nginx/
).lemmyexternalproxy
network, deleteinternal: true
on thelemmyinternal
network (required to enable port forwarding) and add port forwards to thelemmy
andlemmy-ui
docker services. Here's what that would look like: https://www.diffchecker.com/vjfEFuz6/docker-compose.yml
file for theproxy
service to bind to whatever your external facing IP is.