Selfhosted

39435 readers

6 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:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Federation Upstream Error of my Lemmy Instance (feddit.de)

submitted 9 months ago by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

Hello again,

thanks to your great feedback last time, I set up SSL with letsencrypt and got HTTPS working.

However, federation is still not working.

When troubleshooting as described in the docs I get the following Bad-Gateway error:

"~# curl -H "Accept: application/activity+json" https:///u/blueberry

So apparently, its again the reverse-proxy, but this time, its not able to speak to the backend.

My nginx-error-file shows the following error: "2024/02/08 12:37:46 [error]: connect() failed (111: Connection refused) while connecting to upstream, client: , server: , request: "GET /u/blueberry HTTP/2.0", upstream: "http://0.0.0.0:8536/u/blueberry", host: "

But using "docker ps" I find port 8536 open, so it should work.

Do you have any idea whats the problem here?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 7 points 9 months ago* (last edited 9 months ago) (1 children)

When you get a 502 it usually means that your reverse proxy is unable to connect to your backend server. I'm not sure if you've obfuscated the URL in your post but 0.0.0.0 is not a valid IP (it just means ALL IPs). If you are attempting to connect on the same machine that is hosting use 127.0.0.1. if you are on the same network then use the local IP.

[–] [email protected] 3 points 9 months ago

Thanks. It was due to me using a wrong port. Its working now.

Sorry for the inconvinience