Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] Default nginx config in docs gives lots of no live upstreams while connecting to upstream errors #1263

Closed
tsmethurst opened this issue Dec 14, 2022 · 2 comments · Fixed by #1264
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@tsmethurst
Copy link
Contributor

I was seeing lots of these on goblin.technology:

2022/12/14 13:16:29 [error] 1829#1829: *451 no live upstreams while connecting to upstream, client: REDACTED, server: goblin.technology, request: "GET /api/v1/streaming?stream=user&access_token=REDACTED HTTP/1.1", upstream: "http://localhost/api/v1/streaming?stream=user&access_token=REDACTED", host: "goblin.technology"

2022/12/14 13:16:30 [error] 1829#1829: *448 no live upstreams while connecting to upstream, client: REDACTED, server: goblin.technology, request: "GET /.well-known/nodeinfo HTTP/1.1", upstream: "http://loc
alhost/.well-known/nodeinfo", host: "goblin.technology"

2022/12/14 13:16:31 [error] 1829#1829: *452 no live upstreams while connecting to upstream, client: REDACTED, server: goblin.technology, request: "GET /api/v1/streaming?stream=user&access_token=REDACTED HTTP/1.1", upstream: "http://localhost/api/v1/streaming?stream=user&access_token=REDACTED", host: "goblin.technology"

2022/12/14 13:16:32 [error] 1829#1829: *453 no live upstreams while connecting to upstream, client: REDACTED, server: goblin.technology, request: "GET /api/v1/streaming?stream=user&access_token=REDACTED HTTP/1.1", upstream: "http://localhost/api/v1/streaming?stream=user&access_token=REDACTED", host: "goblin.technology"

2022/12/14 13:16:33 [error] 1829#1829: *455 no live upstreams while connecting to upstream, client: REDACTED, server: goblin.technology, request: "POST /users/tobi/inbox HTTP/1.1", upstream: "http://localho
st/users/tobi/inbox", host: "goblin.technology"

2022/12/14 13:16:33 [error] 1829#1829: *454 no live upstreams while connecting to upstream, client: REDACTED, server: goblin.technology, request: "POST /users/maloki/inbox HTTP/1.1", upstream: "http://local
host/users/maloki/inbox", host: "goblin.technology"

2022/12/14 13:16:35 [error] 1829#1829: *456 no live upstreams while connecting to upstream, client: REDACTED, server: goblin.technology, request: "GET /api/v1/streaming?stream=user&access_token=REDACTED HTTP/1.1", upstream: "http://localhost/api/v1/streaming?stream=user&access_token=REDACTED", host: "goblin.technology"

Turns out it's some nginx weirdness; doing the change described here fixed the issue: https://stackoverflow.com/questions/49767001/how-to-solve-nginx-no-live-upstreams-while-connecting-to-upstream-client#52550758

Just opening this to help others, I'll make a PR immediately to update our docs.

@tsmethurst tsmethurst added bug Something isn't working documentation Improvements or additions to documentation labels Dec 14, 2022
@igalic
Copy link
Contributor

igalic commented Dec 15, 2022

this is happening after #1099?
does GoToSocial default to IPv4?
or does go?

@hikari-no-yume
Copy link
Contributor

I only changed the documentation there. What did you set the bind address to in your GoToSocial config?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants