[GH-ISSUE #2751] Certificate not found. Nginx not starting after newest update #1889

New issue

Closed

opened 2026-02-26 07:32:57 +03:00 by kerem · 1 comment

kerem commented

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

Owner

Originally created by @boehser-enkel on GitHub (Mar 27, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2751

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
[](ginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-23/fullchain.pem": BIO_new_file() 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))

Nginx Proxy Manager Version
Newest and also tried out some old ones now

To Reproduce
Start Nginx Proxy Manager after updating.
Check: the path is not there. Also not in my backups
The error comes right after loading of default_host\site.conf

Expected behavior
Clean start

Screenshots

Operating System
Ubuntu

Additional context

Originally created by @boehser-enkel on GitHub (Mar 27, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2751  **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** [](ginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-23/fullchain.pem": BIO_new_file() 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)) **Nginx Proxy Manager Version** Newest and also tried out some old ones now **To Reproduce** Start Nginx Proxy Manager after updating. Check: the path is not there. Also not in my backups The error comes right after loading of default_host\site.conf **Expected behavior** Clean start **Screenshots**  **Operating System** Ubuntu **Additional context**

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@boehser-enkel commented on GitHub (Mar 28, 2023):

I have same issue, how are you fix it @boehser-enkel ?

I deleted the corresponding files and recertified after nginx started again after that

@boehser-enkel commented on GitHub (Mar 28, 2023): > I have same issue, how are you fix it @boehser-enkel ? I deleted the corresponding files and recertified after nginx started again after that

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

No description provided.

Rows
Columns