search

NginxProxyManager / nginx-proxy-manager

Docker container for managing Nginx proxy hosts with a simple, powerful interface
https://nginxproxymanager.com
MIT License
23.19k stars 2.69k forks source link

NPM GUI not visible after docker installation #1541

Open akashkj opened 3 years ago

akashkj commented 3 years ago

Checklist

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

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.

akashkj commented 3 years ago

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

chaptergy commented 3 years ago

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?

akashkj commented 3 years ago

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?

chaptergy commented 3 years ago

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.

github-actions[bot] commented 8 months ago

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