mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #3176] Support for DuckDNS Aliases #2150
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#2150
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 @Veldkornet on GitHub (Sep 2, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3176
Is your feature request related to a problem? Please describe.
Please provide support for DNS aliases on the certificate when doing DNS challenge certificate requests, I’m specifically referring to the DuckDNS option; but I suppose this would be valid for any provider.
Describe the solution you'd like
Describe alternatives you've considered
There is a HomeAssistant Add-On which already does something similar (LetsEncrypt certificates for DuckDNS domains) -> https://github.com/home-assistant/addons/tree/master/duckdns
See original implementation details at: https://github.com/home-assistant/addons/pull/1253
Additional context
@github-actions[bot] commented on GitHub (Apr 6, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@mdhemmi commented on GitHub (Oct 25, 2024):
Do you have a update about this feature request? Thanks
@github-actions[bot] commented on GitHub (Jun 3, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@C-Fu commented on GitHub (Jun 3, 2025):
love this!
@github-actions[bot] commented on GitHub (Jan 23, 2026):
Issue is now considered stale. If you want to keep it open, please comment 👍