[GH-ISSUE #3845] [Feature Request] Replace SSL Cert upon delete of another #2529

Closed
opened 2026-02-26 07:35:54 +03:00 by kerem · 3 comments
Owner

Originally created by @brandoningli on GitHub (Jun 30, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3845

Is your feature request related to a problem? Please describe.

I'm in the process of migrating from using an SSL cert I uploaded to one Let's Encrypt fetches from within NPM. After creating the new LE cert and deleting the custom one, I now have to manually go in and update the SSL settings on each host to not only use the new cert, but use the other auxiliary settings they were using.

Describe the solution you'd like

When deleting an SSL cert, assuming another is configured, ask if the user would like to migrate to using a different cert. If so, replace the old cert with the new one in the host configs instead of resetting them all to HTTP Only, keeping the other settings like Force SSL along the way.

Describe alternatives you've considered

Additional context

Originally created by @brandoningli on GitHub (Jun 30, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3845 <!-- Are you in the right place? - If you are looking for support on how to get your upstream server forwarding, please consider asking the community on Reddit. - If you are writing code changes to contribute and need to ask about the internals of the software, Gitter is the best place to ask. - If you think you found a bug with NPM (not Nginx, or your upstream server or MySql) then you are in the *right place.* --> **Is your feature request related to a problem? Please describe.** <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] --> I'm in the process of migrating from using an SSL cert I uploaded to one Let's Encrypt fetches from within NPM. After creating the new LE cert and deleting the custom one, I now have to manually go in and update the SSL settings on each host to not only use the new cert, but use the other auxiliary settings they were using. **Describe the solution you'd like** <!-- A clear and concise description of what you want to happen. --> When deleting an SSL cert, assuming another is configured, ask if the user would like to migrate to using a different cert. If so, replace the old cert with the new one in the host configs instead of resetting them all to HTTP Only, keeping the other settings like Force SSL along the way. **Describe alternatives you've considered** <!-- A clear and concise description of any alternative solutions or features you've considered. --> **Additional context** <!-- Add any other context or screenshots about the feature request here. -->
kerem 2026-02-26 07:35:54 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 16, 2025):

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

<!-- gh-comment-id:2661191984 --> @github-actions[bot] commented on GitHub (Feb 16, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@brandoningli commented on GitHub (Feb 16, 2025):

Please keep this on the roadmap!

<!-- gh-comment-id:2661194803 --> @brandoningli commented on GitHub (Feb 16, 2025): Please keep this on the roadmap!
Author
Owner

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

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

<!-- gh-comment-id:3567389980 --> @github-actions[bot] commented on GitHub (Nov 23, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
Sign in to join this conversation.
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#2529
No description provided.