Getting 502 Bad Gateway error

[nidhin077]

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • No
• Are you sure you're not using someone else's docker image?
  • Yes
• Have you searched for similar issues (both open and closed)?
  • Yes

Describe the bug I'm getting a 502 Bad Gateway error when adding a location in the nginx proxy manager. Could you please help?

Nginx Proxy Manager Version v2.10.4

To Reproduce Steps to reproduce the behavior: Use a v2.10.4 version image and try to add the location

[MarcS1975]

i had the same bug - Docker image 2.10.4. works. thanks

[lilws]

I have just upgrade to v2.11.x and got the same problems 502 Bad gateway, but it is only happen to 1 specific host. Other hosts is running fine. But rollback to 2.10.4 eveything back to normal.

My situation:

I have a network A: LAN - 192.168.1.1 and internet - 116.x.x.x - Home 1 I have a network B: LAN - 192.168.1.1 and internet - 171.y.y.y - Home 2 in another place

All the NPM setup was running on Network A and eveything is fine with this. In the network B I have 2 hosts through NPM in Network A - yes, I must forward these 2 ports in network B so A can forward to it, and this is where the problems happen when upgrade to 2.11.x. I can access the first host in network B without any problems, then the second host in network B always return 502 Bad Gateway.

There is no error in log so it seems I can't track what the problems here because when test server reachability it works.

[github-actions[bot]]

Issue is now considered stale. If you want to keep it open, please comment :+1: