[GH-ISSUE #4526] Allow editing DNS-Provider credentials in the UI after initial creation #2895

Open
opened 2026-02-26 07:37:07 +03:00 by kerem · 3 comments
Owner

Originally created by @t46g on GitHub (May 5, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4526

Is your feature request related to a problem? Please describe.:
Once you create a DNS-01 validated certificate via the UI, you cannot update its DNS provider API credentials. To change them, you must delete and recreate the certificate and change the certificate for every host which was using the old one.

Describe the solution you’d like:
Add an “Edit DNS Provider” option in the certificate UI to modify Customer Number, API Key, and API Password in place—no deletion or manual re-provisioning required.

Originally created by @t46g on GitHub (May 5, 2025). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4526 Is your feature request related to a problem? Please describe.: Once you create a DNS-01 validated certificate via the UI, you cannot update its DNS provider API credentials. To change them, you must delete and recreate the certificate and change the certificate for every host which was using the old one. Describe the solution you’d like: Add an “Edit DNS Provider” option in the certificate UI to modify Customer Number, API Key, and API Password in place—no deletion or manual re-provisioning required.
Author
Owner

@rgregg commented on GitHub (May 23, 2025):

I'd love to also be able to share the credentials across multiple certificates instead of needing to enter the same creds over and over again.

<!-- gh-comment-id:2903164849 --> @rgregg commented on GitHub (May 23, 2025): I'd love to also be able to share the credentials across multiple certificates instead of needing to enter the same creds over and over again.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 12, 2025):

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

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

@t46g commented on GitHub (Dec 13, 2025):

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

👍

<!-- gh-comment-id:3649579074 --> @t46g commented on GitHub (Dec 13, 2025): > Issue is now considered stale. If you want to keep it open, please comment 👍 👍
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#2895
No description provided.