You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Checklist
jc21/nginx-proxy-manager:latest
docker image?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:
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:
Expected behavior
Should create a new entry or recreate the folders etc. properly.
The text was updated successfully, but these errors were encountered: