starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #4476] 502 Bad Gateway #2866

New issue

Closed

opened 2026-02-26 07:37:02 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 07:37:02 +03:00

Owner

Originally created by @CLU91 on GitHub (Apr 8, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4476

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- Yes
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 have an Ubuntu 24.04.2 LTS with Portainer installed in Portainer i created a network for NPM and a seperate network for Grafana and another one for my Zabbix Stack. So far everything was working as expected. I configured the Grafana and Zabbix-Web Container to have a second IP in the NPM Network.

After a reboot of the server today the Zabbix-Web is not reachable via NPM Forward anymore. And can't seem to get a hold on the issue. I'm searching Google for hours and nothing is working. I even recreated entire containers but still not working. Grafana Container and also other Web Services are running fine, except Zabbix-Web.

We are using a custom SSL-Certificate from our Domain Provider.

I'm trying to find hints in log files or anywhere but nothing is shown. The only error is see is 502 Bad Gateway - Open Resty. When i am in the bash of the NPM and do a curl http://172.18.0.2:8080 it says "Couldn't Connect to server". Someone got an idea? Might be a bug in the new NPM Version that correlates with something in Zabbix?

Nginx Proxy Manager Version
2.12.3

To Reproduce

Expected behavior
To do a proper forward to HTTPS like it worked for months without any issues.

Screenshots

Operating System
Ubuntu 24.04.2 LTS and Portainer 2.21.5

Originally created by @CLU91 on GitHub (Apr 8, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4476 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - 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 have an Ubuntu 24.04.2 LTS with Portainer installed in Portainer i created a network for NPM and a seperate network for Grafana and another one for my Zabbix Stack. So far everything was working as expected. I configured the Grafana and Zabbix-Web Container to have a second IP in the NPM Network. After a reboot of the server today the Zabbix-Web is not reachable via NPM Forward anymore. And can't seem to get a hold on the issue. I'm searching Google for hours and nothing is working. I even recreated entire containers but still not working. Grafana Container and also other Web Services are running fine, except Zabbix-Web. We are using a custom SSL-Certificate from our Domain Provider. I'm trying to find hints in log files or anywhere but nothing is shown. The only error is see is 502 Bad Gateway - Open Resty. When i am in the bash of the NPM and do a curl http://172.18.0.2:8080 it says "Couldn't Connect to server". Someone got an idea? Might be a bug in the new NPM Version that correlates with something in Zabbix? **Nginx Proxy Manager Version** 2.12.3 **To Reproduce** **Expected behavior** To do a proper forward to HTTPS like it worked for months without any issues. **Screenshots** ![Image](https://github.com/user-attachments/assets/d30ce4f0-82e0-4c10-afee-723525551d79) ![Image](https://github.com/user-attachments/assets/7d38364e-21ad-43f3-bb82-ae2ac402d8a3) **Operating System** Ubuntu 24.04.2 LTS and Portainer 2.21.5

kerem

2026-02-26 07:37:02 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 07:37:02 +03:00

Author

Owner

@CLU91 commented on GitHub (Apr 8, 2025):

Okay, the problem magically solved itself. I just deleted the Container, Image, Volume and created a new network. It's ridiclious to be honest......

@CLU91 commented on GitHub (Apr 8, 2025): Okay, the problem magically solved itself. I just deleted the Container, Image, Volume and created a new network. It's ridiclious to be honest......

kerem commented

2026-02-26 07:37:02 +03:00

Author

Owner

@QazCetelic commented on GitHub (Jun 27, 2025):

This suddenly started happening to me too, despite not updating the container image

@QazCetelic commented on GitHub (Jun 27, 2025): This suddenly started happening to me too, despite not updating the container image

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#2866

No description provided.

Rows
Columns