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 #229] npm-8/fullchain.pem no such file #199

New issue

Closed

opened 2026-02-26 06:31:25 +03:00 by kerem · 7 comments

kerem commented

2026-02-26 06:31:25 +03:00

Owner

Originally created by @danmed on GitHub (Nov 6, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/229

I've just rebooted my docker server and now nginxproxymanager wont start.. the docker logs are filling up with this :

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

Last thing i remeber doing was deleting a proxy host and then deleting it's associated ssl certificate.

Originally created by @danmed on GitHub (Nov 6, 2019). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/229 I've just rebooted my docker server and now nginxproxymanager wont start.. the docker logs are filling up with this : nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-8/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-8/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) Last thing i remeber doing was deleting a proxy host and then deleting it's associated ssl certificate.

kerem

2026-02-26 06:31:25 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:31:27 +03:00

Author

Owner

@danmed commented on GitHub (Nov 6, 2019):

Managed to figure out that the proxy host i deleted, the conf file was still sat in the nginx/proxy_host folder.. Deleting that fixed the issue.. though that still signifies a problem no?

@danmed commented on GitHub (Nov 6, 2019): Managed to figure out that the proxy host i deleted, the conf file was still sat in the nginx/proxy_host folder.. Deleting that fixed the issue.. though that still signifies a problem no?

kerem commented

2026-02-26 06:31:27 +03:00

Author

Owner

@esticle commented on GitHub (Jan 8, 2020):

similar problem here, when deleting, editing and recreating a SSL'd host the certbot npm-n directories increment but the proxy_host configuration still exists / or points to a previous npm-n directory which no longer exists.

@esticle commented on GitHub (Jan 8, 2020): similar problem here, when deleting, editing and recreating a SSL'd host the certbot npm-n directories increment but the proxy_host configuration still exists / or points to a previous npm-n directory which no longer exists.

kerem commented

2026-02-26 06:31:27 +03:00

Author

Owner

@oldgeezy commented on GitHub (May 5, 2020):

Similar problem here. Deleting the conf file in /nginx/proxy_host/ didn't help

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

@oldgeezy commented on GitHub (May 5, 2020): Similar problem here. Deleting the conf file in /nginx/proxy_host/ didn't help `nginx: [emerg] BIO_new_file("/etc/letsencrypt/live/npm-10/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-10/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file) `

kerem commented

2026-02-26 06:31:27 +03:00

Author

Owner

@ndaringer commented on GitHub (Jun 17, 2020):

NPM won't start. Same error these folks are facing.

error.log just fills up with this repeatedly.

2020/06/17 05:55:05 [emerg] 9666#9666: BIO_new_file("/etc/letsencrypt/live/npm-23/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-23/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)

@ndaringer commented on GitHub (Jun 17, 2020): NPM won't start. Same error these folks are facing. error.log just fills up with this repeatedly. `2020/06/17 05:55:05 [emerg] 9666#9666: BIO_new_file("/etc/letsencrypt/live/npm-23/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-23/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)`

kerem commented

2026-02-26 06:31:27 +03:00

Author

Owner

@downtime0 commented on GitHub (Mar 13, 2021):

I just had the same issue after deleting a certificate. The certificate was still attached to the Host record, but I've not had issues with deleting those before.
I determined from the Audit Log that certificate # 13 was the one I deleted and it matched the missing folder number .../live/npm-13/

I resolved this issue by recreating the .../live/npm-13/ folder that was logged as missing, then copied all the files from another /npm-## folder and restarted the container with success.

I was expecting an error somewhere with the duplicate certificates, or at least two displayed in the GUI but no issues at all.
I finally renamed the folder I created so the app would not go looking for it, fully stopped and restarted the container, and so far no issues.

@downtime0 commented on GitHub (Mar 13, 2021): I just had the same issue after deleting a certificate. The certificate was still attached to the Host record, but I've not had issues with deleting those before. I determined from the Audit Log that certificate # 13 was the one I deleted and it matched the missing folder number .../live/npm-13/ I resolved this issue by recreating the .../live/npm-13/ folder that was logged as missing, then copied all the files from another /npm-## folder and restarted the container with success. I was expecting an error somewhere with the duplicate certificates, or at least two displayed in the GUI but no issues at all. I finally renamed the folder I created so the app would not go looking for it, fully stopped and restarted the container, and so far no issues.

kerem commented

2026-02-26 06:31:27 +03:00

Author

Owner

@wendingtuo commented on GitHub (May 5, 2021):

@downtime0 When you say you renamed the folder, are you talking about the replacement npm-13 folder you created? Every time I change the folder name or rm the folder nginx fails to start again.

How do I remove this certificate completely and correctly so that NPM will start again without some old folder with a duplicate certificate in it?

----- EDIT -----

The host was still present in my redirect hosts and was looking for the SSL cert I was trying to delete. Confirmed that once I removed that host, NPM was able to boot without error.

@wendingtuo commented on GitHub (May 5, 2021): @downtime0 When you say you renamed the folder, are you talking about the replacement npm-13 folder you created? Every time I change the folder name or rm the folder nginx fails to start again. How do I remove this certificate completely and correctly so that NPM will start again without some old folder with a duplicate certificate in it? ----- EDIT ----- The host was still present in my redirect hosts and was looking for the SSL cert I was trying to delete. Confirmed that once I removed that host, NPM was able to boot without error.

kerem commented

2026-02-26 06:31:27 +03:00

Author

Owner

@chaptergy commented on GitHub (May 11, 2021):

Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/208

@chaptergy commented on GitHub (May 11, 2021): Duplicate of https://github.com/jc21/nginx-proxy-manager/issues/208

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

No description provided.

Rows
Columns