mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #824] Support zonomi for Lets Encrypt DNS challenge #699
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#699
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 @timwnl on GitHub (Jan 13, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/824
I fully setup the NGINX and I am trying to setup a Lets Encrypt certificate for my domain. Earlier I have used acme.sh dns challenge with Zonomi.
I see a lot of DNS providers are supported but I miss Zonomi. Are there any plans to add Zonomi to the list? I am not sure which ACME client is supported though, but acme.sh, lego and Posh-ACME are.
see https://community.letsencrypt.org/t/dns-providers-who-easily-integrate-with-lets-encrypt-dns-validation/86438
KR, Tim
@chaptergy commented on GitHub (May 9, 2021):
For now nginx proxy manager only supports dns challenges via
certbotdns plugins, so this has to exist in order to offer it in the proxy manager. Unfortunately there is no zonomi dns plugin. So unless a plugin like this is published, it is unlikely this will be implemented in the near future.In the meantime you can follow issue https://github.com/jc21/nginx-proxy-manager/issues/836, in case acme.sh will ever be implemented.
@github-actions[bot] commented on GitHub (Mar 21, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (May 1, 2025):
Issue was closed due to inactivity.