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 #1541] NPM GUI not visible after docker installation #1173

New issue

Closed

opened 2026-02-26 06:36:03 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 06:36:03 +03:00

Owner

Originally created by @akashkj on GitHub (Nov 1, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1541

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
NPM container, afte re-deployed, is not accessible via GUI.

Nginx Proxy Manager Version
2.9.11

To Reproduce
Steps to reproduce the behavior:

Create NPM container with Let's Encrypt certificate inmported via GUI
Delete current container + db container + all volumes
Recreate container
GUI not acessible anymore

Expected behavior
Login page available

Screenshots

Operating System
Docker image jc21/nginx-proxy-manager:latest - on ARM64

Additional context

Using portainer for container management
In logs of NPM container, following error logs are seen repeatedly.

nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-2/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-2/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)

Mentioned path is not present in the container. Instea, file fullchain.pem is present in folder npm-3

[root@docker-7bcf1f8b1d19:/app]# ls -ltr /etc/letsencrypt/live/npm-3/             
total 4
lrwxrwxrwx 1 root root  32 Nov  1 10:39 privkey.pem -> ../../archive/npm-3/privkey1.pem
lrwxrwxrwx 1 root root  34 Nov  1 10:39 fullchain.pem -> ../../archive/npm-3/fullchain1.pem
lrwxrwxrwx 1 root root  30 Nov  1 10:39 chain.pem -> ../../archive/npm-3/chain1.pem
lrwxrwxrwx 1 root root  29 Nov  1 10:39 cert.pem -> ../../archive/npm-3/cert1.pem
-rw-r--r-- 1 root root 692 Nov  1 10:39 README

[root@docker-7bcf1f8b1d19:/app]# ls -ltr /etc/letsencrypt/live/      
total 8
-rw-r--r-- 1 root root  740 Nov  1 10:03 README
drwxr-xr-x 2 root root 4096 Nov  1 10:39 npm-3

I am not sure if something wrong done from my side as I am relatively new to this. Thanks is advance.

Originally created by @akashkj on GitHub (Nov 1, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1541  **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** NPM container, afte re-deployed, is not accessible via GUI. **Nginx Proxy Manager Version** 2.9.11 **To Reproduce** Steps to reproduce the behavior: 1. Create NPM container with Let's Encrypt certificate inmported via GUI 2. Delete current container + db container + all volumes 3. Recreate container 4. GUI not acessible anymore **Expected behavior** Login page available **Screenshots**  **Operating System** Docker image jc21/nginx-proxy-manager:latest - on ARM64 **Additional context** - Using portainer for container management - In logs of NPM container, following error logs are seen repeatedly. ![image](https://user-images.githubusercontent.com/14318173/139664144-d7bf345f-76c7-495c-aec9-bf423fb3c93f.png) ``` nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-2/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-2/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) ``` Mentioned path is not present in the container. Instea, file fullchain.pem is present in folder npm-3 ``` [root@docker-7bcf1f8b1d19:/app]# ls -ltr /etc/letsencrypt/live/npm-3/ total 4 lrwxrwxrwx 1 root root 32 Nov 1 10:39 privkey.pem -> ../../archive/npm-3/privkey1.pem lrwxrwxrwx 1 root root 34 Nov 1 10:39 fullchain.pem -> ../../archive/npm-3/fullchain1.pem lrwxrwxrwx 1 root root 30 Nov 1 10:39 chain.pem -> ../../archive/npm-3/chain1.pem lrwxrwxrwx 1 root root 29 Nov 1 10:39 cert.pem -> ../../archive/npm-3/cert1.pem -rw-r--r-- 1 root root 692 Nov 1 10:39 README [root@docker-7bcf1f8b1d19:/app]# ls -ltr /etc/letsencrypt/live/ total 8 -rw-r--r-- 1 root root 740 Nov 1 10:03 README drwxr-xr-x 2 root root 4096 Nov 1 10:39 npm-3 ``` I am not sure if something wrong done from my side as I am relatively new to this. Thanks is advance.

kerem

2026-02-26 06:36:03 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 06:36:04 +03:00

Author

Owner

@akashkj commented on GitHub (Nov 1, 2021):

After copying content of npm-3 to npm-2, it started working.

@akashkj commented on GitHub (Nov 1, 2021): After copying content of npm-3 to npm-2, it started working.

kerem commented

2026-02-26 06:36:04 +03:00

Author

Owner

@chaptergy commented on GitHub (Nov 1, 2021):

How is there even any data if you have deleted all volumes? Are you sure you haven't just deleted a certificate which was used in the proxy host and haven't updated the proxy host?

@chaptergy commented on GitHub (Nov 1, 2021): How is there even any data if you have deleted all volumes? Are you sure you haven't just deleted a certificate which was used in the proxy host and haven't updated the proxy host?

kerem commented

2026-02-26 06:36:04 +03:00

Author

Owner

@akashkj commented on GitHub (Nov 1, 2021):

I had used portainer to delete the nginx deployment(which deleted contianers for npm and db). Assuming that volumes were persisted, how does directory name change?

@akashkj commented on GitHub (Nov 1, 2021): I had used portainer to delete the nginx deployment(which deleted contianers for npm and db). Assuming that volumes were persisted, how does directory name change?

kerem commented

2026-02-26 06:36:04 +03:00

Author

Owner

@chaptergy commented on GitHub (Nov 1, 2021):

I can't think of a way the directory names could have been automatically changed. That's why I'm trying to rule out other possibilities first, like a certificate used four your proxy host 2 which was later deleted and a different certificate uploaded, but proxy host 2 was never updated to use that new certificate.

@chaptergy commented on GitHub (Nov 1, 2021): I can't think of a way the directory names could have been automatically changed. That's why I'm trying to rule out other possibilities first, like a certificate used four your proxy host 2 which was later deleted and a different certificate uploaded, but proxy host 2 was never updated to use that new certificate.

kerem commented

2026-02-26 06:36:04 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 2, 2024):

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

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

kerem commented

2026-02-26 06:36:04 +03:00

Author

Owner

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

Issue was closed due to inactivity.

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

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

No description provided.

Rows
Columns