this post was submitted on 11 Jun 2023
5 points (100.0% liked)

Lemmy Support

4719 readers
33 users here now

Support / questions about Lemmy.

Matrix Space: #lemmy-space

founded 5 years ago
MODERATORS
 

I followed the docker installation instructions and added the certificate successfully but I get this status:

400 Bad Request | nginx

host nginx error logs:

2023/06/11 12:12:45 [debug] 10161#10161: *16 http upstream process header
2023/06/11 12:12:45 [error] 10161#10161: *16 connect() failed (111: Connection refused) while connecting to upstream, client: 198.199.109.53, server: mydomain.tld, request: "GET /version HTTP/1.1", upstream: "http://127.0.0.1:82/version", host: "xxx.xxx.xx.xxx"
2023/06/11 12:12:45 [debug] 10161#10161: *16 http next upstream, 2
2023/06/11 12:12:45 [debug] 10161#10161: *16 free rr peer 2 4
2023/06/11 12:12:45 [warn] 10161#10161: *16 upstream server temporarily disabled while connecting to upstream, client: 198.199.109.53, server: mydomain.tld, request: "GET /version HTTP/1.1", upstream: "http://127.0.0.1:82/version", host: "xxx.xxx.xx.xxx"

I replaced my host IP and domain for privacy

Please see my comments below for more info. I tried putting all text here in the body but it won't let me post.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 2 points 2 years ago (1 children)

The lemmy service needs access to the external network, too. It's not in the docs, but there's a bug on GitHub about it (on mobile, can't find it).

I created a third network called lemmybridge and added it to my lemmy service definition.

[โ€“] [email protected] 2 points 2 years ago

Thank you for the tip, I've been fighting this damn problem for hours trying to figure out why my instance wasn't able to make external requests.

Popped in a third network into the docker compose file and now things seem to be working