mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 01:15:51 +03:00
[GH-ISSUE #4291] Add Dreamhost support to DNS challenge #2761
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#2761
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 @freakma on GitHub (Jan 12, 2025).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4291
What provider would you like to see added to NPM?
Dreamhost
Have you checked if a certbot plugin exists?
Yes, https://pypi.org/project/certbot-dns-dreamhost/
@TiggsPanther commented on GitHub (Apr 20, 2025):
I second this.
I mainly use NPM on my internal domain but do have one or two things I expose externally, but locked down to specific IPs at the firewall level.
LE doesn't publish an IP range for allowlisting, so the DNS-01 challenge would be a no-brainer for me, except that my domain is hosted in DreamHost and, currently, not supported in NPM. So I have to periodically open port 80 or the world, which I'd really rather not do, just to get the certificate to renew.
@dylanrhodes0 commented on GitHub (Oct 3, 2025):
Yes please!