starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00

[GH-ISSUE #3465] Deleting Active SSL Certificate Breaks All Hosts Using It #2312

New issue

Open

opened 2026-02-26 07:34:57 +03:00 by kerem · 4 comments

kerem commented

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

Owner

Originally created by @coanghel on GitHub (Jan 18, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3465

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

Deleting a certificate that is currently in use sends NPM into a reboot loop. Similar to #3420

Nginx Proxy Manager Version

2.10.4

To Reproduce
Steps to reproduce the behavior:

Configure a proxy host
Configure an SSL cert and add it to the above
Delete the proxy host
NPM will now return "internal error" for any attempted activities (such as swapping hosts to a new certificate); recreating the container presents the below error, where npm-# is the certificate you just deleted.

[emerg] cannot load certificate "/etc/letsencrypt/live/npm-3/fullchain.pem": BIO_new_file() failed

Expected behavior

Either do not allow an actively used certificate to be deleted, or update the nginx.conf files for all hosts using it prior to resolving the delete request.

Operating System

Docker running on Ubuntu server

Additional context

Upon investigating, I found that the sqlite database reflected the new SSL certificate in the certificate table and the hosts I swapped to the new certificate reflected the correct certificate in the proxy_host table, however the nginx .conf files in /proxy_host/ folder still had the path of the old certificate in them. Manually editing these config files and then restarting the container allowed it to start up as expected.

Originally created by @coanghel on GitHub (Jan 18, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3465  **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**  Deleting a certificate that is currently in use sends NPM into a reboot loop. Similar to #3420 **Nginx Proxy Manager Version**  2.10.4 **To Reproduce** Steps to reproduce the behavior: 1. Configure a proxy host 2. Configure an SSL cert and add it to the above 3. Delete the proxy host 4. NPM will now return "internal error" for any attempted activities (such as swapping hosts to a new certificate); recreating the container presents the below error, where npm-# is the certificate you just deleted. ``` [emerg] cannot load certificate "/etc/letsencrypt/live/npm-3/fullchain.pem": BIO_new_file() failed ``` **Expected behavior**  Either do not allow an actively used certificate to be deleted, or update the nginx.conf files for all hosts using it prior to resolving the delete request. **Operating System**  Docker running on Ubuntu server **Additional context**  Upon investigating, I found that the sqlite database reflected the new SSL certificate in the `certificate` table and the hosts I swapped to the new certificate reflected the correct certificate in the `proxy_host` table, however the nginx .conf files in /proxy_host/ folder still had the path of the old certificate in them. Manually editing these config files and then restarting the container allowed it to start up as expected.

kerem added the

bug

label

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

kerem commented

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

Author

Owner

@zimbres commented on GitHub (Mar 7, 2024):

Same problem here

@zimbres commented on GitHub (Mar 7, 2024): Same problem here

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Oct 30, 2024):

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

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

kerem commented

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

Author

Owner

@flinthamm commented on GitHub (Feb 20, 2025):

Same problem here

@flinthamm commented on GitHub (Feb 20, 2025): Same problem here

kerem commented

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

Author

Owner

@PietroBer commented on GitHub (Sep 6, 2025):

unfortunately i made the same mistake of deleting 1 ssl certificate and now NPM is in a loop.

@PietroBer commented on GitHub (Sep 6, 2025): unfortunately i made the same mistake of deleting 1 ssl certificate and now NPM is in a loop.

kerem referenced this issue

2026-02-26 08:31:04 +03:00

[PR #2312] [MERGED] Added Namecheap certbot dns plugin #3554

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

No description provided.

Rows
Columns