mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #3845] [Feature Request] Replace SSL Cert upon delete of another #2529
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#2529
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
@github-actions[bot] commented on GitHub (Feb 16, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@brandoningli commented on GitHub (Feb 16, 2025):
Please keep this on the roadmap!
@github-actions[bot] commented on GitHub (Nov 23, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍