Skip to content

Deleting a wildcard cert and adding it again results in errors #4511

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
JohnGalt1717 opened this issue Apr 28, 2025 · 0 comments
Open

Deleting a wildcard cert and adding it again results in errors #4511

JohnGalt1717 opened this issue Apr 28, 2025 · 0 comments
Labels

Comments

@JohnGalt1717
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant