this post was submitted on 02 Jul 2023
12 points (92.9% liked)

Selfhosted

40736 readers
469 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud
Loki
CannaVet
devve
HybridSarcasm
[email protected]
12
[Question] hosting lemmy on ubuntu server - firewall configuration (self.selfhosted)
submitted 2 years ago by Solvena to c/selfhosted
4 comments fedilink hide all child comments
 

Hi, this is a follow-up on the 502 question earlier, which I think I got a step closer to solving. However, if I try to connect to my lemmy instance now, it results in a time out. Now, I have set up the ufw firewall to allow nginx http - do I need to allow anything else to get to connect? Or is my timeout error something else?

top 4 comments
sorted by: hot top controversial new old
[–] [email protected] 3 points 2 years ago

Basically you only need port 443 open. Maybe 80 also depending on how you generate the SSL certificates.

[–] [email protected] 1 points 2 years ago

Are you able to access (via curl or something else) the port the Lemmy is serving from behind the nginx server?

[–] footty 1 points 2 years ago

Well, I'm here again. I get a 504 gateway timeout after upgrading or doing docker-compose down, and found a weird fix for it.

  1. docker kill your postgres instance
  2. Go to your webpage and wait for it to tell you an error
  3. docker-compose up -d and now it'll work

I tried killing postgres and bringing it up immediately as well but that did not fix the problem. Weird magical incantation and downvote me all you want, just wanted to throw it out there.

[–] [email protected] 1 points 2 years ago

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.