[GH-ISSUE #961] Afraid / Free DNS Challenge #810

Open
opened 2026-02-26 06:34:30 +03:00 by kerem · 8 comments
Owner

Originally created by @brombomb on GitHub (Mar 19, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/961

I currently use afraid/freedns. I pay for a private listing there and was able to set up wildcard ssl certs by using the acme.sh dns_api. I was hoping to see this ported to nginx-proxy-manager.

My workflow:
https://gist.github.com/ammgws/381b4d9104c4e2b43b9210f33f03a15a

Afraid api
https://github.com/acmesh-official/acme.sh/blob/master/dnsapi/dns_freedns.sh

More API Options.

I'm sure that there are quite a few configs here and that's why you haven't yet supported it.

Thanks!

Originally created by @brombomb on GitHub (Mar 19, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/961 I currently use afraid/freedns. I pay for a private listing there and was able to set up wildcard ssl certs by using the acme.sh dns_api. I was hoping to see this ported to nginx-proxy-manager. My workflow: https://gist.github.com/ammgws/381b4d9104c4e2b43b9210f33f03a15a Afraid api https://github.com/acmesh-official/acme.sh/blob/master/dnsapi/dns_freedns.sh More API Options. I'm sure that there are quite a few configs here and that's why you haven't yet supported it. Thanks!
Author
Owner

@chaptergy commented on GitHub (May 9, 2021):

Unfortunately the DNS challenge within nginx proxy manager is only available for certbot dns plugins. FreeDNS does not have a plugin for this. Using the acme.sh script is a very significant deviation from this and would require a just as significant amount of work. It also would require support for two separate DNS challenge mechanisms instead of just one. So I don't think it is very likely to be implemented for now, unless a certbot plugin for FreeDNS is published.

If anyone is interested in publishing a certbot dns plugin for this, this netcup plugin can serve as inspiration.

<!-- gh-comment-id:835847572 --> @chaptergy commented on GitHub (May 9, 2021): Unfortunately the DNS challenge within nginx proxy manager is only available for [certbot dns plugins](https://certbot.eff.org/docs/using.html#dns-plugins). FreeDNS does not have a plugin for this. Using the acme.sh script is a very significant deviation from this and would require a just as significant amount of work. It also would require support for two separate DNS challenge mechanisms instead of just one. So I don't think it is very likely to be implemented for now, unless a certbot plugin for FreeDNS is published. If anyone is interested in publishing a certbot dns plugin for this, [this netcup plugin](https://github.com/coldfix/certbot-dns-netcup/blob/master/certbot_dns_netcup.py) can serve as inspiration.
Author
Owner

@Technetium1 commented on GitHub (Jan 28, 2022):

It has been created: https://github.com/schleuss/certbot_dns_freedns.
This is probably not too hard to adapt if the first one isn't useful: https://github.com/TRPB/docker-certbot-freedns

<!-- gh-comment-id:1024052684 --> @Technetium1 commented on GitHub (Jan 28, 2022): It has been created: https://github.com/schleuss/certbot_dns_freedns. This is probably not too hard to adapt if the first one isn't useful: https://github.com/TRPB/docker-certbot-freedns
Author
Owner

@github-actions[bot] commented on GitHub (Mar 16, 2024):

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

<!-- gh-comment-id:2001057030 --> @github-actions[bot] commented on GitHub (Mar 16, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@Technetium1 commented on GitHub (Mar 19, 2024):

This is still desired functionality.

<!-- gh-comment-id:2008059877 --> @Technetium1 commented on GitHub (Mar 19, 2024): This is still desired functionality.
Author
Owner

@github-actions[bot] commented on GitHub (Dec 13, 2024):

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

<!-- gh-comment-id:2540380288 --> @github-actions[bot] commented on GitHub (Dec 13, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@Technetium1 commented on GitHub (Dec 25, 2024):

👍

<!-- gh-comment-id:2562001110 --> @Technetium1 commented on GitHub (Dec 25, 2024): :+1:
Author
Owner

@github-actions[bot] commented on GitHub (Aug 21, 2025):

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

<!-- gh-comment-id:3208733467 --> @github-actions[bot] commented on GitHub (Aug 21, 2025): Issue is now considered stale. If you want to keep it open, please comment :+1:
Author
Owner

@Technetium1 commented on GitHub (Aug 21, 2025):

👍

<!-- gh-comment-id:3209108560 --> @Technetium1 commented on GitHub (Aug 21, 2025): 👍
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#810
No description provided.