Basically you only need port 443 open. Maybe 80 also depending on how you generate the SSL certificates.
this post was submitted on 02 Jul 2023
9 points (90.9% liked)
Selfhosted
39435 readers
7 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:
- 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
Are you able to access (via curl or something else) the port the Lemmy is serving from behind the nginx server?
How's your firewall set up? Some custom firewall rules can end up interfering with Docker's networking, that's worth checking that. It uses iptables to control what can go in and out of the bridge and if the host can access it. If you have a blanket drop policy that overrides Docker's your Docker networking can break.