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?
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.
docker kill your postgres instance
Go to your webpage and wait for it to tell you an error
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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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
Basically you only need port 443 open. Maybe 80 also depending on how you generate the SSL certificates.
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.docker killyour postgres instancedocker-compose up -dand now it’ll workI 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.
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.