Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FreeDNS Afraid.org #2352

Open
privatesam opened this issue Nov 1, 2022 · 4 comments · May be fixed by #3750
Open

FreeDNS Afraid.org #2352

privatesam opened this issue Nov 1, 2022 · 4 comments · May be fixed by #3750
Labels
dns provider request This issue is a request to integrate a new DNS-challenge provider

Comments

@privatesam
Copy link

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

@privatesam privatesam added the dns provider request This issue is a request to integrate a new DNS-challenge provider label Nov 1, 2022
@DFS-90
Copy link
Contributor

DFS-90 commented 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
Copy link

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.

bricas added a commit to bricas/nginx-proxy-manager that referenced this issue Feb 16, 2024
Copy link

Issue is now considered stale. If you want to keep it open, please comment 👍

@arsenicks
Copy link

@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 github-actions bot removed the stale label Jun 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dns provider request This issue is a request to integrate a new DNS-challenge provider
Projects
None yet
4 participants