[GH-ISSUE #1187] npinxpm container unhealthy when stopped container name used in host config #971

New issue

Closed

opened 2026-02-26 06:35:15 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 06:35:15 +03:00

Owner

Originally created by @jacgl on GitHub (Jun 18, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1187

Hi,
I am using nginxpm to redirect traffic to another containers in docker, and typically I use container name instead of direct ip address. It works perfectly unless all containers are healthy.
BUT, when you restart docker and at least 1 container is not, nginxpm has the issue with start as well. Moreover, there is no access to web page, so no chance to even disable problematic container. In the log something like the line below can be found:

nginx: [emerg] host not found in upstream "mpd_mpc" in /data/nginx/proxy_host/21.conf:47,

(this is case when mpd_mpc is used in custom locations, but I believe the similar situation exists for "forward hostname")

Regards.

Originally created by @jacgl on GitHub (Jun 18, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1187 Hi, I am using nginxpm to redirect traffic to another containers in docker, and typically I use container name instead of direct ip address. It works perfectly unless all containers are healthy. BUT, when you restart docker and at least 1 container is not, nginxpm has the issue with start as well. Moreover, there is no access to web page, so no chance to even disable problematic container. In the log something like the line below can be found: nginx: [emerg] host not found in upstream "mpd_mpc" in /data/nginx/proxy_host/21.conf:47, (this is case when mpd_mpc is used in custom locations, but I believe the similar situation exists for "forward hostname") Regards.

kerem

2026-02-26 06:35:15 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:35:16 +03:00

Author

Owner

@chaptergy commented on GitHub (Jun 18, 2021):

Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/633

@chaptergy commented on GitHub (Jun 18, 2021): Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/633

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#971

No description provided.

Rows
Columns