starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #4511] Deleting a wildcard cert and adding it again results in errors #2889

New issue

Open

opened 2026-02-26 07:37:06 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 07:37:06 +03:00

Owner

Originally created by @JohnGalt1717 on GitHub (Apr 28, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4511

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
If I delete a wild card certificate from the list of ssl certs so that I can recreate it with new dns credentials (because there doesn't appear to be an edit function so that you can update. credentials or change dns hosts) and then create it again you then get errors in the logs like this:

nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-5/fullchain.pem": BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/etc/letsencrypt/live/npm-5/fullchain.pem, r) error:10000080:BIO routines::no such file)
nginx: configuration file /etc/nginx/nginx.conf test failed

It appears to be trying to use the same directory for the cert that was there before because it appears to think it still exists somehow.

Nginx Proxy Manager Version
v2.12.3

To Reproduce
Steps to reproduce the behavior:

Go to SSL Certificates
Delete an existing wildcard cert.
Create the same wildcard cert again, but change the dns challenge credentials
See error

Expected behavior
Should create a new entry or recreate the folders etc. properly.

Originally created by @JohnGalt1717 on GitHub (Apr 28, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4511 **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** If I delete a wild card certificate from the list of ssl certs so that I can recreate it with new dns credentials (because there doesn't appear to be an edit function so that you can update. credentials or change dns hosts) and then create it again you then get errors in the logs like this: ``` nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-5/fullchain.pem": BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/etc/letsencrypt/live/npm-5/fullchain.pem, r) error:10000080:BIO routines::no such file) nginx: configuration file /etc/nginx/nginx.conf test failed ``` It appears to be trying to use the same directory for the cert that was there before because it appears to think it still exists somehow. **Nginx Proxy Manager Version** v2.12.3 **To Reproduce** Steps to reproduce the behavior: 1. Go to SSL Certificates 2. Delete an existing wildcard cert. 3. Create the same wildcard cert again, but change the dns challenge credentials 4. See error **Expected behavior** Should create a new entry or recreate the folders etc. properly.

kerem added the

bug

label

2026-02-26 07:37:06 +03:00

kerem commented

2026-02-26 07:37:06 +03:00

Author

Owner

@Whys8182 commented on GitHub (May 6, 2025):

me, too!

@Whys8182 commented on GitHub (May 6, 2025): me, too!

kerem commented

2026-02-26 07:37:06 +03:00

Author

Owner

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

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

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

kerem commented

2026-02-26 07:37:06 +03:00

Author

Owner

@JohnGalt1717 commented on GitHub (Nov 14, 2025):

Comment.

@JohnGalt1717 commented on GitHub (Nov 14, 2025): Comment.

kerem commented

2026-02-26 07:37:06 +03:00

Author

Owner

@muchowsky commented on GitHub (Dec 10, 2025):

For me i deleted certificate because i wanted to try different configuration. When i tried to create new one it returned some internal error
i tired to restart docker image but in this state it couldn't bring itself up
It did started working after i deleted config in proxy host folder that used this non existing ssl certificate so looking at this issue it could be good to remove this ssl certificate from all proxy hosts configs before proceeding with deletion or block deletion until user does it by him self.

Container log (After restart):

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

Nginx Proxy Manager Version
v2.13.5

@muchowsky commented on GitHub (Dec 10, 2025): For me i deleted certificate because i wanted to try different configuration. When i tried to create new one it returned some internal error i tired to restart docker image but in this state it couldn't bring itself up It did started working after i deleted config in proxy host folder that used this non existing ssl certificate so looking at this issue it could be good to remove this ssl certificate from all proxy hosts configs before proceeding with deletion or block deletion until user does it by him self. #### Container log (After restart): ``` nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-9/fullchain.pem": BIO_new_file() failed (SSL: error:80000002:system library::No such file or directory:calling fopen(/etc/letsencrypt/live/npm-9/fullchain.pem, r) error:10000080:BIO routines::no such file) ``` Nginx Proxy Manager Version v2.13.5

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

No description provided.

Rows
Columns