[GH-ISSUE #2791] NPM not loading after docker container update.

kerem commented

2026-02-26 07:33:14 +03:00

Owner

Originally created by @wilotas on GitHub (Apr 1, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2791

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

Just update today and I see this error message in Logs:

/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

Nginx Proxy Manager Version

I can not load NPM web interface.

To Reproduce
Steps to reproduce the behavior:

Just try to load webpage...

Expected behavior

Load webpage

Screenshots

Operating System
Ubuntu 22.04 with docker

Additional context

It was working perfectly since last update.

Originally created by @wilotas on GitHub (Apr 1, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2791  **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** Just update today and I see this error message in Logs: /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information. **Nginx Proxy Manager Version**  I can not load NPM web interface. **To Reproduce** Steps to reproduce the behavior: 1. Just try to load webpage... **Expected behavior**  Load webpage **Screenshots** ![image](https://user-images.githubusercontent.com/513370/229257313-65aac9a1-f173-4ec4-89af-4ecd42a0fac4.png) **Operating System** Ubuntu 22.04 with docker **Additional context** It was working perfectly since last update.

kerem

2026-02-26 07:33:14 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:33:14 +03:00

Author

Owner

@djk1983 commented on GitHub (Apr 1, 2023):

This suggestion fixed this issue for me. #2774

@djk1983 commented on GitHub (Apr 1, 2023): This [suggestion](https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2774#issuecomment-1489466154) fixed this issue for me. #2774

kerem commented

2026-02-26 07:33:14 +03:00

Author

Owner

@wilotas commented on GitHub (Apr 1, 2023):

This suggestion fixed this issue for me. #2774

Hi guy,

I am not using mysql, just npm container.

I did a rollback to 2752 and it worked. Stop updating image until hace clear.

@wilotas commented on GitHub (Apr 1, 2023): > This [suggestion](https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2774#issuecomment-1489466154) fixed this issue for me. #2774 Hi guy, I am not using mysql, just npm container. I did a rollback to 2752 and it worked. Stop updating image until hace clear.

kerem commented

2026-02-26 07:33:14 +03:00

Author

Owner

@Norsagir commented on GitHub (Apr 5, 2023):

Exact same problem here with the latest docker package update, I have to do docker restart to have NPM up and running correctly. I'm on Raspberry Pi 4, each time the Rapsberry reboots, I have to restart NPM manually.

@Norsagir commented on GitHub (Apr 5, 2023): Exact same problem here with the latest docker package update, I have to do `docker restart` to have NPM up and running correctly. I'm on Raspberry Pi 4, each time the Rapsberry reboots, I have to restart NPM manually.

kerem commented

2026-02-26 07:33:14 +03:00

Author

Owner

@CanonCan commented on GitHub (Apr 11, 2023):

This suggestion fixed this issue for me. #2774

Hi guy,

I am not using mysql, just npm container.

I did a rollback to 2752 and it worked. Stop updating image until hace clear.

can you please specify the tag in the docker config you used??

I had a cache file corruption on my unraid server...i ran scrub then filesystem repair now had to create a new docker.img file and reinstall all my containers. I cannot load the interface for NPM at all not by internal ip or my Cloudflare

@CanonCan commented on GitHub (Apr 11, 2023): > > This [suggestion](https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2774#issuecomment-1489466154) fixed this issue for me. #2774 > > Hi guy, > > I am not using mysql, just npm container. > > I did a rollback to 2752 and it worked. Stop updating image until hace clear. can you please specify the tag in the docker config you used?? I had a cache file corruption on my unraid server...i ran scrub then filesystem repair now had to create a new docker.img file and reinstall all my containers. I cannot load the interface for NPM at all not by internal ip or my Cloudflare

kerem commented

2026-02-26 07:33:14 +03:00

Author

Owner

@djk1983 commented on GitHub (Apr 11, 2023):

Hi @CanonCan I am using the latest tag (build 2.10.2) and everything remains operational

@djk1983 commented on GitHub (Apr 11, 2023): Hi @CanonCan I am using the latest tag (build 2.10.2) and everything remains operational

kerem commented

2026-02-26 07:33:14 +03:00

Author

Owner

@CanonCan commented on GitHub (Apr 11, 2023):

I'm on 2.10.2 as well. I can finally get to the web gui with the internal IP, my container was set to use port 81 for the interface but it was trying to use 80 for some reason I changed it to 181 and now I can get to the interface but all my reverse proxy stuffs gives me a cloud flare. 521 error

Sincerely,

Michael

On Apr 11, 2023 at 07:16, Dan Knight @.***> wrote:

Hi @CanonCan I am using the latest tag (build 2.10.2) and everything remains operational

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

@CanonCan commented on GitHub (Apr 11, 2023): I'm on 2.10.2 as well. I can finally get to the web gui with the internal IP, my container was set to use port 81 for the interface but it was trying to use 80 for some reason I changed it to 181 and now I can get to the interface but all my reverse proxy stuffs gives me a cloud flare. 521 error Sincerely, Michael > > On Apr 11, 2023 at 07:16, Dan Knight ***@***.***> wrote: > > > > Hi @CanonCan I am using the latest tag (build 2.10.2) and everything remains operational > > > > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you were mentioned.Message ID: ***@***.***> > >

kerem commented

2026-02-26 07:33:14 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 23, 2024):

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

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

kerem commented

2026-02-26 07:33:14 +03:00

Author

Owner

@runarorested commented on GitHub (Apr 13, 2024):

I had a similar issue after updating to v2.11.1. I do not know if it may be a regression or a new bug, but it is similar enough.

It started working, but after setting up 3 proxies it started hanging up, as in totally hanging up the web server. The most basic proxy did not cause problems: phpmyadmin, a proxy HTTP to HTTP did not cause any problems, but portainer or owncloud (HTTPS to HTTPS , or HTTPS to HTTP) caused it to fail after some time.

Both the GUI and the redirections worked for a few minutes, and then suddently stopped responding, and the only solution was to delete the data volume and recreate the docker to force a full reset. Restarting the dockers did nothing. The health-check stalled too, until the health failures started showing.

Because the proxy stalled, there where no logs about why it failed. And even then, because I needed to delete the log files, it seems it failed to recreate them and start logging data after that.

Going back toward v2.10.4 and resetting the configuration allowed me to keep setting them up completly, until they kept worked without stalling.

It would be nice to add some extra functionality to the startup script to verify the existence and integrity of the log files.
The command line healthcheck is miss-documented, it is located at /bin/check-health, not /usr/bin/check-health.
As a feature request:
a. when creating a new redirection/proxy/whatever, a quick check verfying that a A, AAAA or CNAME register exists showing as a checkmark or badge, would prevent errors due to typing mistakes.

b. Likewise when writing the target of the proxy, a checkmark showing that the configuration written matches with the target would be nice (ex: checking that the "portainer" docker with target HTTPS://local_IP:9433 it is really an HTTPS and not an HTTP listening port.

Given that you can't read the logs from the GUI, that would prevent some of the most basic mistakes.

@runarorested commented on GitHub (Apr 13, 2024): I had a similar issue after updating to v2.11.1. I do not know if it may be a regression or a new bug, but it is similar enough. It started working, but after setting up 3 proxies it started hanging up, as in totally hanging up the web server. The most basic proxy did not cause problems: phpmyadmin, a proxy HTTP to HTTP did not cause any problems, but portainer or owncloud (HTTPS to HTTPS , or HTTPS to HTTP) caused it to fail after some time. Both the GUI and the redirections worked for a few minutes, and then suddently stopped responding, and the only solution was to delete the data volume and recreate the docker to force a full reset. Restarting the dockers did nothing. The health-check stalled too, until the health failures started showing. Because the proxy stalled, there where no logs about why it failed. And even then, because I needed to delete the log files, it seems it failed to recreate them and start logging data after that. Going back toward v2.10.4 and resetting the configuration allowed me to keep setting them up completly, until they kept worked without stalling. 1. It would be nice to add some extra functionality to the startup script to verify the existence and integrity of the log files. 2. The command line healthcheck is miss-documented, it is located at /bin/check-health, not /usr/bin/check-health. 3. As a feature request: a. when creating a new redirection/proxy/whatever, a quick check verfying that a A, AAAA or CNAME register exists showing as a checkmark or badge, would prevent errors due to typing mistakes. b. Likewise when writing the target of the proxy, a checkmark showing that the configuration written matches with the target would be nice (ex: checking that the "portainer" docker with target HTTPS://local_IP:9433 it is really an HTTPS and not an HTTP listening port. Given that you can't read the logs from the GUI, that would prevent some of the most basic mistakes.

kerem commented

2026-02-26 07:33:14 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 11, 2024):

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

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

kerem commented

2026-02-26 07:33:15 +03:00

Author

Owner

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

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Nov 30, 2025): Issue was closed due to inactivity.

kerem referenced this issue

2026-02-26 08:31:36 +03:00

[PR #3392] [MERGED] Make auto-renew use built-in renew function #3694

Rows
Columns

[GH-ISSUE #2791] NPM not loading after docker container update. #1916