-
Notifications
You must be signed in to change notification settings - Fork 3k
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
502 Bad Gateway on Centos 8 #1529
Comments
Same on Debian 10 here. |
Is this project dead? I see many issues mentioning 502 error. |
Same issue here on an Unbutu 20.04 host: I have some older containers that I configured a month or so ago and continue to work fine with this proxy. But everything I've tried to set up with this proxy over the last few weeks has this same 502 error. Very weird and not too helpful I know, but the change roughly correlates to the creation date on the newest nginx-proxy image (Created 2020-10-30 09:46:00 sha256:5e6f392e99e5454851caa8a3dbb021560a32375edff772b64f862c4d7831d038) so maybe that is related? In any case here's the tail of the log from nginx-proxy for while I try to access the proxy:
Looks like the mDNS cname has been setup but nginx can't connect to the container. Any idea what is going on and how I could fix things? |
Hi, here is what I got
|
Did you try to enabling masquerading in CentOS 8? |
I did not. I just switched to Traefik. |
That looks like a good replacement - what is your experience with it so far ? |
It is very powerful, but also a bit tricky to configure. |
This might have been fixed by #1601 @mamyn0va, @nickv2002, care to test ? |
I pulled the latest image with sha256:
|
Could you post the output of those commands ?
|
A long dump of text from running those commands on my system |
Are you certain the mylar.local container is sharing a network with the nginx-proxy (or docker-gen if you use a two container setup) container ?
|
Ahh so they're on different networks... hmm. Must be related to having different docker-compose stacks for them in my case.
Thanks for you help debugging that. I'll work on figuring out how to bridge that networking unless you have any tips offhand. |
I usually create a separate Docker network outside of Docker compose then use it as an external network in the compose file.
then version: '3'
services:
nginx:
[...]
networks:
- nginx-proxy
# Do not forget to 'docker network create nginx-proxy' before launch
# and to connect the proxied containers to the nginx-proxy network.
networks:
nginx-proxy:
external: true Repeated in every compose file for services that will be proxied. Also take a look at https://github.com/buchdag/letsencrypt-nginx-proxy-companion-compose |
Is there something special we have to do to get it running on Centos 8?
I tried to run the basic docker-compose.yaml example from README
And I got:
The text was updated successfully, but these errors were encountered: