mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #2352] FreeDNS Afraid.org #1667
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#1667
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 @privatesam on GitHub (Nov 1, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2352
What provider would you like to see added to NPM?
freeDNS (afraid.org)
Have you checked if a certbot plugin exists?
Appears to be one here: https://gist.github.com/AnthonyWharton/a0e8faae7195a5c1dea210466eda1c92
@DFS-90 commented on GitHub (Nov 6, 2022):
The link you cited shows a script, not a certbot plugin.
Guess you need to create a certbot plugin for FreeDNS prior to inclusion into npm.
Alternatively, you could have a look here:
https://community.letsencrypt.org/t/dns-providers-who-easily-integrate-with-lets-encrypt-dns-validation/86438
All providers that are listed with "Certbot" under "ACME Client Support" can be integrated into npm or might even already be included.
@ShawnCorey commented on GitHub (Sep 17, 2023):
Will Python certbot plugins be acceptable? There is one that is publicly available through pip installation that works for my custom stealth domain on FreeDNS using the examples and command lines listed in the Project README.
FreeDNS Python certbot plugin project link:
https://github.com/schleuss/certbot_dns_freedns
If not, is there anyway to import an existing Let's Encrypt cert that has already been requested and setup for certbot renewal? The block on importing Let's Encrypt certs stop people from using ones they have gotten though means other than requesting through the frontend. I did a hacky workaround of adding another test cert and then replacing the pem files with symlinks to the ones in /etc/letsencrypt/live directory. I would really like to not have to result to these kind of workarounds just because this project doesn't support a plugin for my DNS providers AND blocks manual install of the Let's Encrypt certs I get though other means.
@github-actions[bot] commented on GitHub (Apr 24, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@arsenicks commented on GitHub (May 13, 2024):
@bricas I just submitted a PR that would fix the current version that doesn't work for all people that are not paid subscriber. see #3750 if you can take a look please :)
@github-actions[bot] commented on GitHub (Jan 22, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍
@Joey4tunato commented on GitHub (Apr 9, 2025):
👍🏻
@github-actions[bot] commented on GitHub (Dec 29, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍