-
Hi everyone, I am trying to get a container working behind an nginx-proxy, but I am getting 502 Bad Gateway when running container with docker-container.yml when I am running like this, everything working perfectly:
but when I am launching similar config with docker compose up I get 502 Bad Gateway error when opening a domain in browser.
In logs I see following error: What am I missing? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi. Please post your whole proxy config (cmd line or compose file used to start the proxy container plus any additional config), not just the proxied container. I suspect that your are either using two different compose files for the proxy and the proxied container or starting the proxy via cmd line and the proxied container via Docker Compose, which result in the two containers being connected to two different networks, and as the documentation mention this does not work. |
Beta Was this translation helpful? Give feedback.
Hi. Please post your whole proxy config (cmd line or compose file used to start the proxy container plus any additional config), not just the proxied container.
I suspect that your are either using two different compose files for the proxy and the proxied container or starting the proxy via cmd line and the proxied container via Docker Compose, which result in the two containers being connected to two different networks, and as the documentation mention this does not work.