starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #4488] ALL (local) proxy hosts MUST be running or NPM doesn't start (no WebUI; affects VM usage) #2877

New issue

Open

opened 2026-02-26 07:37:04 +03:00 by kerem · 1 comment

kerem commented

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

Owner

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

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 use Proxmox LXCs and VMs often for testing. Some of these are proxied through NPM. Now with almost every NPM upgrade, it doesn't start, or at least shows no WebUI on port 81. Usually because I have shut down one or more (proxied) VMs.

The Docker log messages show something like nginx: [emerg] … (sorry, can't look it up anymore), and nothing more happens.

So I have to unnecessarily start up lots of LXCs and VMs just to be able to start NPM!

Could this possibly be changed, please? So it will start up even wwhen one or more local hosts are currently unreachable?

For the time being, is there a workaround? Like maybe disabling the currently switched off VMs in the NPM UI or something like that?

Nginx Proxy Manager Version

v2.12.3

To Reproduce
Steps to reproduce the behavior:

Have one or more defined proxy hosts locally unavailable.
docker-compose down
docker-compose up -d
This might be enough. If not, do a pull in between (like for upgrading).

Expected behavior

Normal start, possible upgrade migrations, and the WebUI available even when one or more local proxy hosts unavailable.

Screenshots

Operating System

Proxmox LXC

Additional context

Originally created by @Moonbase59 on GitHub (Apr 19, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4488  **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 use Proxmox LXCs and VMs often for testing. Some of these are proxied through NPM. Now with almost every NPM upgrade, it doesn't start, or at least shows no WebUI on port 81. _Usually because I have shut down one or more (proxied) VMs._ The Docker log messages show something like `nginx: [emerg] …` (sorry, can't look it up anymore), and nothing more happens. So I have to unnecessarily start up lots of LXCs and VMs _just to be able to start NPM!_ **Could this possibly be changed, please?** So it will start up even wwhen one or more local hosts are currently unreachable? For the time being, is there a **workaround**? Like maybe disabling the currently switched off VMs in the NPM UI or something like that? **Nginx Proxy Manager Version**  v2.12.3 **To Reproduce** Steps to reproduce the behavior: 1. Have one or more defined proxy hosts locally unavailable. 2. `docker-compose down` 3. `docker-compose up -d` 4. This might be enough. If not, do a pull in between (like for upgrading). **Expected behavior**  Normal start, possible upgrade migrations, and the WebUI available even when one or more local proxy hosts unavailable. **Screenshots**  **Operating System**  Proxmox LXC **Additional context**

kerem added the

stale

bug

labels

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

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Nov 15, 2025):

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

@github-actions[bot] commented on GitHub (Nov 15, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:

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

No description provided.

Rows
Columns