starred/nginx-proxy-manager-NginxProxyManager

Fork 0

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

[GH-ISSUE #1316] Edit DNS challenge credentials #1049

New issue

Closed

opened 2026-02-26 06:35:33 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 06:35:33 +03:00

Owner

Originally created by @internetfreak on GitHub (Aug 13, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1316

Is your feature request related to a problem? Please describe.
Currently, when creating (wildcard) certificates there's no easy way to edit the credentials used as they are stored internally. If e.g. we need to update a password, we must also update it for NPM or the renewal will fail. Only way to easily update it would be to request a new certificate with the updated credentials and set that new certificate for all affected hosts before deleting the old one.

Describe the solution you'd like
Offer a possibility to edit credentials without having to delete and re-add the certificate

Describe alternatives you've considered
I know we could map the folder where the credentials are stored via docker volumes or use docker execute but that is not really comfortable. Also, in the case you have multiple users accessing their own hosts and certs you would need to grant everyone access to the server via ssh (and possibly root/sudo access depending on how you run the docker container) which is not always feasible from a security point.

Additional context
Nothing

Originally created by @internetfreak on GitHub (Aug 13, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1316 **Is your feature request related to a problem? Please describe.** Currently, when creating (wildcard) certificates there's no easy way to edit the credentials used as they are stored internally. If e.g. we need to update a password, we must also update it for NPM or the renewal will fail. Only way to easily update it would be to request a new certificate with the updated credentials and set that new certificate for all affected hosts before deleting the old one. **Describe the solution you'd like** Offer a possibility to edit credentials without having to delete and re-add the certificate **Describe alternatives you've considered** I know we could map the folder where the credentials are stored via docker volumes or use `docker execute` but that is not really comfortable. Also, in the case you have multiple users accessing their own hosts and certs you would need to grant everyone access to the server via ssh (and possibly root/sudo access depending on how you run the docker container) which is not always feasible from a security point. **Additional context** Nothing

kerem

2026-02-26 06:35:33 +03:00

closed this issue
added the
enhancement

stale
labels

kerem commented

2026-02-26 06:35:34 +03:00

Author

Owner

@chaptergy commented on GitHub (Aug 13, 2021):

Edit: what I said is totally wrong, I got things mixed up, just ignore this comment.

~~It should work to update the credentials and force-renew the certificate. This should update the credetials on file without having to delete the certificate and request a new one.~~

@chaptergy commented on GitHub (Aug 13, 2021): Edit: what I said is totally wrong, I got things mixed up, just ignore this comment. ~It should work to update the credentials and force-renew the certificate. This should update the credetials on file without having to delete the certificate and request a new one.~

kerem commented

2026-02-26 06:35:34 +03:00

Author

Owner

@internetfreak commented on GitHub (Aug 13, 2021):

But where can I update the credentials? Via docker volumes/docker execute? If I choose to renew a certificate, from which I know it should still have the old credentials, nothing happens

@internetfreak commented on GitHub (Aug 13, 2021): But where can I update the credentials? Via docker volumes/docker execute? If I choose to renew a certificate, from which I know it should still have the old credentials, nothing happens

kerem commented

2026-02-26 06:35:34 +03:00

Author

Owner

@chaptergy commented on GitHub (Aug 13, 2021):

Oh, sorry, I mixed up the interface for the host and certificate.

@chaptergy commented on GitHub (Aug 13, 2021): Oh, sorry, I mixed up the interface for the host and certificate.

kerem commented

2026-02-26 06:35:34 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 6, 2024):

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

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

kerem commented

2026-02-26 06:35:34 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 19, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 19, 2025): Issue was closed due to inactivity.

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

No description provided.

Rows
Columns