mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #1189] DNS challenge DYNU configuration #970
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#970
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 @suhrke on GitHub (Jun 18, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1189
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
Hello,
I wanted to use the DNS challenge plugin Dynu, and this wants to get
certbot_dns_dynu:dns_dynu_auth_token = YOUR_DYNU_AUTH_TOKEN
I replaced YOUR_DYNU_AUTH_TOKEN with my own api token at dynu.com
and got only
"Internal error"
and
"This section requires some knowledge about Certbot and its DNS plugins. Please consult the respective plugins documentation."
In the corresponding python script inside the container /opt/certbot/lib/python3.7/site-packages/certbot_dns_dynu/dns_dynu.py I found also only the reference to the dynu auth token.
I use this DNS challenge on another platform (proxmox-ve) which uses auth-token and oauth2 Client-ID/secret what works properly. So I look for a way to configure this in nginx proxy manager properly, but found not any hint.
Nginx Proxy Manager Version
To Reproduce
Steps to reproduce the behavior:
certbot_dns_dynu:dns_dynu_auth_token = MY_OWN_DYNU_AUTH_TOKEN
Expected behavior
correct pull a certificate from letsencrypt with dns challenge provided by dynu.com
Screenshots
Operating System
ubuntu 20.04 LTS / Docker version 20.10.7, build f0df350
Additional context
@chaptergy commented on GitHub (Jun 23, 2021):
Could you take a look into the logs of the npm container to see what the actual error is?
@sillydanny commented on GitHub (Jul 3, 2023):
I have the same issue about the DNS challenge,
@randomDrops commented on GitHub (Jul 26, 2023):
Found a solution. Guess there might be a better solution.

Replace the text with
dns_dynu_auth_token=\<api-key\>. Of course, replace the angle-bracket with your own API-key from Dynu. Remove all the spaces on both sides of the equal sign.@randomDrops commented on GitHub (Jul 26, 2023):
Update: Remember to put 120 into the Propagation Seconds textbox. Please be patient and try a few times till it succeeds.
@DairyWeb3638077 commented on GitHub (Nov 29, 2023):
I get this error
@yuriw commented on GitHub (Jan 20, 2024):
I see this too in 2024
Were there any solutions found for this issue?
@st-ivan commented on GitHub (Feb 24, 2024):
This seems to be fixed in NPM version 2.11.
default text: dns_dynu_auth_token = YOUR_DYNU_AUTH_TOKEN
Just remove "YOUR_DYNU_AUTH_TOKEN" and put your API KEY. Wait for about 1 minute and the cert will be issued.
@mrt2nbl commented on GitHub (Feb 24, 2024):
Working for me even with default text (without space)
@yurii-karadzhov commented on GitHub (Jun 16, 2024):
I got unrecognized arguments error:
@yurii-karadzhov commented on GitHub (Jun 16, 2024):
pip install certbot-dns-dynusolves the issue@github-actions[bot] commented on GitHub (Feb 9, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Feb 22, 2026):
Issue was closed due to inactivity.