mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-28 10:55:54 +03:00
[GH-ISSUE #1948] Add SSL Certificate not remembering Credentials File Content in UI #1416
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#1416
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 @FormBurden on GitHub (Mar 23, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1948
Describe the bug
When using the UI and creating an SSL Certificate with my provider Cloudflare, and using a DNS Challenge, the API token that the UI shows is the default every time I try and use it. Even though under the
letsencrypt/credentials/credentials-Xwhen I view it, it is my actual API token. But for whatever reason the the UI can't get the correct info from the credential file. Anything I can do? Or this is an actual bug? I tried just doing it as is, on the UI to see if it would go through, but it fails, because it's not the correct API.Not sure if it's permissions or anything? But when reading the docs, from what I could find, it doesn't state to create a specific user or anything. So not sure if it would be that.
Docker-Compose on Debian 10
v2.9.16
@palitu commented on GitHub (Jul 31, 2023):
i also have the same type of issue, but i would like to have it pull the default API key (or entire file) when requesting a new certificate.
Can that be set somewhere?
@github-actions[bot] commented on GitHub (Feb 21, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Apr 5, 2025):
Issue was closed due to inactivity.