mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #4450] Using cached credentials for dns challenge #2850
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#2850
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 @lugaetsch on GitHub (Mar 24, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4450
Is your feature request related to a problem? Please describe.
I am using wildcards and distinct subdomains in npm and using dns challenge to request certificates.
Describe the solution you'd like
Using saved credentials from earlier dns-certificate-challenges for new proxy-hosts i set up.
used credentials already stored in the docker default directory (letsencrypt/credentials/).
@github-actions[bot] commented on GitHub (Sep 23, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@lugaetsch commented on GitHub (Sep 23, 2025):
Please keep this open