Nginx-proxy Incorrect proxy_pass, no live upstreams while connecting to upstream. 502 bad gateway #2156
Unanswered
duongptryu
asked this question in
Q&A
Replies: 2 comments
-
Hi. Could you gave us the whole configurations of both the proxy and the proxied container plus the generated nginx configuration file instead of snippets ? Also please copy and paste text rather than take screenshots. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Without seeing the full configs it's hard to say, but I'd guess that your nginx-proxy container is not connected to the same network as your proxied container, therefore it can't reach it. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I follow step by step to setup nginx-proxy, but when I call API, it's response 502 Bad Gateway. When I saw file default.conf in nginx-proxy container, I saw the proxy_pass line have more a string of numbers after my domain.
This is my command to start nginx-proxy
This is my config of my container app
The error no live upstream because the domain have more string number after.
The default.conf I saw in nginx-container
Please tell my why nginx-proxy automate add more string number after my domain and how I can fix it
Beta Was this translation helpful? Give feedback.
All reactions