mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #813] Support certbot manual DNS challenge #686
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#686
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 @krouter on GitHub (Jan 8, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/813
Checklist
What is troubling you?
Currently using nginx reverse proxy and have been using the command line to manually renew the SSL every 3 months using DNS challenge at google domain registrar.
After moving to NPM, i'm unable to get letsencrypt to work with manual DNS challenge. I don't see an option in the gui.
Letsencrypt gui in NPM throws an 'Internal Error' without any information.
How can i move the current LE SSL certs from the nginx to NPM without having to reissue?
@krouter commented on GitHub (Jan 20, 2021):
Can someone pls advise.
@MaxCarritt commented on GitHub (Jan 25, 2021):
I think you have to install certbot somewhere, run it with the manual challenge, and then upload your certs to the SSL page with the add cert button.
@chaptergy commented on GitHub (May 10, 2021):
A manual challenge is not yet available. I have updated the title of this issue to be a feature request of this.
@github-actions[bot] commented on GitHub (Mar 21, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@rrd911 commented on GitHub (Oct 23, 2024):
I am having the same issue. Using noip dns provider
@CrownKingClown commented on GitHub (Feb 6, 2025):
would love to have this
@ohjohnsen commented on GitHub (Apr 21, 2025):
Would also love to have this possibility.
@github-actions[bot] commented on GitHub (Nov 11, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍