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

fullchain.pem" #1771

New issue

Closed

opened 2026-02-26 07:32:23 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 07:32:23 +03:00

Owner

Originally created by @NetoSimoes on GitHub (Jan 13, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2538

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
Manager can't start, crashes at boot. Problem related with certificates

Nginx Proxy Manager Version
2.9.19

To Reproduce
Steps to reproduce the behavior:

Assign a certificate to a proxy host
Delete the ssl certificate
(The proxy host will switch to http only)
Reassigning a new certificate will return internal error
Restart proxy manager crashes

Expected behavior
Handle ssl certificate deletion

Screenshots
None applicable

Operating System
Docker

Client: Docker Engine - Community
 Version:           20.10.21
 API version:       1.41
 Go version:        go1.18.7
 Git commit:        baeda1f
 Built:             Tue Oct 25 18:01:58 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.21
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.18.7
  Git commit:       3056208
  Built:            Tue Oct 25 17:59:49 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.10
  GitCommit:        770bd0108c32f3fb5c73ae1264f7e503fe7b2661
 runc:
  Version:          1.1.4
  GitCommit:        v1.1.4-0-g5fd4c4d
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

Additional context
What I understand from this is that there are "hanging" pointers

Docker Logs

❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
  ❯ /etc/nginx/conf.d/default.conf
  ❯ /etc/nginx/conf.d/include/assets.conf
  ❯ /etc/nginx/conf.d/include/proxy.conf
  ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
  ❯ /etc/nginx/conf.d/include/block-exploits.conf
  ❯ /etc/nginx/conf.d/include/ip_ranges.conf
  ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
  ❯ /etc/nginx/conf.d/include/force-ssl.conf
  ❯ /etc/nginx/conf.d/include/resolvers.conf
  ❯ /etc/nginx/conf.d/production.conf
❯ Enabling IPV6 in hosts: /data/nginx
  ❯ /data/nginx/proxy_host/15.conf
  ❯ /data/nginx/proxy_host/4.conf
  ❯ /data/nginx/proxy_host/36.conf
  ❯ /data/nginx/proxy_host/6.conf
  ❯ /data/nginx/proxy_host/28.conf
  ❯ /data/nginx/proxy_host/30.conf
  ❯ /data/nginx/proxy_host/44.conf
  ❯ /data/nginx/proxy_host/29.conf
  ❯ /data/nginx/proxy_host/35.conf
  ❯ /data/nginx/proxy_host/41.conf
  ❯ /data/nginx/proxy_host/32.conf
  ❯ /data/nginx/proxy_host/40.conf
  ❯ /data/nginx/proxy_host/12.conf
  ❯ /data/nginx/proxy_host/14.conf
  ❯ /data/nginx/proxy_host/39.conf
  ❯ /data/nginx/proxy_host/33.conf
  ❯ /data/nginx/proxy_host/2.conf
  ❯ /data/nginx/default_host/site.conf
nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-27/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-27/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)

Originally created by @NetoSimoes on GitHub (Jan 13, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2538 **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** Manager can't start, crashes at boot. Problem related with certificates **Nginx Proxy Manager Version** 2.9.19 **To Reproduce** Steps to reproduce the behavior: 1. Assign a certificate to a proxy host 2. Delete the ssl certificate (The proxy host will switch to http only) 3. Reassigning a new certificate will return internal error 4. Restart proxy manager crashes **Expected behavior** Handle ssl certificate deletion **Screenshots** None applicable **Operating System** Docker ``` Client: Docker Engine - Community Version: 20.10.21 API version: 1.41 Go version: go1.18.7 Git commit: baeda1f Built: Tue Oct 25 18:01:58 2022 OS/Arch: linux/amd64 Context: default Experimental: true Server: Docker Engine - Community Engine: Version: 20.10.21 API version: 1.41 (minimum version 1.12) Go version: go1.18.7 Git commit: 3056208 Built: Tue Oct 25 17:59:49 2022 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.10 GitCommit: 770bd0108c32f3fb5c73ae1264f7e503fe7b2661 runc: Version: 1.1.4 GitCommit: v1.1.4-0-g5fd4c4d docker-init: Version: 0.19.0 GitCommit: de40ad0 ``` **Additional context** What I understand from this is that there are "hanging" pointers Docker Logs ``` ❯ Enabling IPV6 in hosts: /etc/nginx/conf.d ❯ /etc/nginx/conf.d/default.conf ❯ /etc/nginx/conf.d/include/assets.conf ❯ /etc/nginx/conf.d/include/proxy.conf ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf ❯ /etc/nginx/conf.d/include/block-exploits.conf ❯ /etc/nginx/conf.d/include/ip_ranges.conf ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf ❯ /etc/nginx/conf.d/include/force-ssl.conf ❯ /etc/nginx/conf.d/include/resolvers.conf ❯ /etc/nginx/conf.d/production.conf ❯ Enabling IPV6 in hosts: /data/nginx ❯ /data/nginx/proxy_host/15.conf ❯ /data/nginx/proxy_host/4.conf ❯ /data/nginx/proxy_host/36.conf ❯ /data/nginx/proxy_host/6.conf ❯ /data/nginx/proxy_host/28.conf ❯ /data/nginx/proxy_host/30.conf ❯ /data/nginx/proxy_host/44.conf ❯ /data/nginx/proxy_host/29.conf ❯ /data/nginx/proxy_host/35.conf ❯ /data/nginx/proxy_host/41.conf ❯ /data/nginx/proxy_host/32.conf ❯ /data/nginx/proxy_host/40.conf ❯ /data/nginx/proxy_host/12.conf ❯ /data/nginx/proxy_host/14.conf ❯ /data/nginx/proxy_host/39.conf ❯ /data/nginx/proxy_host/33.conf ❯ /data/nginx/proxy_host/2.conf ❯ /data/nginx/default_host/site.conf nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-27/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-27/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) ```

kerem

2026-02-26 07:32:23 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:32:24 +03:00

Author

Owner

@NetoSimoes commented on GitHub (Jan 13, 2023):

related to #2243

@NetoSimoes commented on GitHub (Jan 13, 2023): related to #2243

kerem commented

2026-02-26 07:32:24 +03:00

Author

Owner

@kikearciniegas commented on GitHub (Oct 19, 2023):

any fix or workaround for this scenario? currently facing the same issue...

@kikearciniegas commented on GitHub (Oct 19, 2023): any fix or workaround for this scenario? currently facing the same issue...

kerem commented

2026-02-26 07:32:24 +03:00

Author

Owner

@lorenzopicoli commented on GitHub (Nov 25, 2023):

@kikearciniegas @NetoSimoes I think it's the same error I had. I fixed it like this https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/3349

@lorenzopicoli commented on GitHub (Nov 25, 2023): @kikearciniegas @NetoSimoes I think it's the same error I had. I fixed it like this https://github.com/NginxProxyManager/nginx-proxy-manager/discussions/3349

kerem commented

2026-02-26 07:32:24 +03:00

Author

Owner

@AlissonSantos95 commented on GitHub (Jan 12, 2024):

hi, easy fix is those steps:

as you can see he complains about "/etc/letsencrypt/live/npm-27/fullchain.pem" that means no folder or certs are found
sudo docker-compose down
(find your nginx proxy folder) mine was at /home
cd letsencrypt
sudo mkdir nmp-27(or the folder its missing)
sudo ls live (see any npm-xx there)
sudo cp -r live/npm-xx/. npm-27(or other that he is complaining)
sudo cp npm-27 live
cd ..
sudo docker-compose up
It will renew that cert becouse the cert is incorrect ans will pass wihtou error.
if you have any question fell free to pm or respond here.

@AlissonSantos95 commented on GitHub (Jan 12, 2024): hi, easy fix is those steps: 1. as you can see he complains about "/etc/letsencrypt/live/npm-27/fullchain.pem" that means no folder or certs are found 2. sudo docker-compose down 3. (find your nginx proxy folder) mine was at /home 4. cd letsencrypt 5. sudo mkdir nmp-27(or the folder its missing) 6. sudo ls live (see any npm-xx there) 7. sudo cp -r live/npm-xx/. npm-27(or other that he is complaining) 8. sudo cp npm-27 live 9. cd .. 10. sudo docker-compose up 11. It will renew that cert becouse the cert is incorrect ans will pass wihtou error. 12. if you have any question fell free to pm or respond here.

kerem commented

2026-02-26 07:32:24 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 30, 2024):

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

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

kerem commented

2026-02-26 07:32:24 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 14, 2025):

Issue was closed due to inactivity.

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

kerem referenced this issue

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

[GH-ISSUE #2881] Temp workaround (that works for me!) for SSL certificate renewal bug #1972

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

No description provided.

Rows
Columns