-
Notifications
You must be signed in to change notification settings - Fork 519
-
Notifications
You must be signed in to change notification settings - Fork 519
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
Integrate dynu.com that also support ACME #1315
Comments
Make a "HTTPS-Domain"-Subscription out of this - you dont choose a shop here - but you have DuckDNS and FreeDNS here as free options. Let the user enter the needed credentials and then trigger the ACME script accordently and exchange the cert nginx. |
"Bad" news: acmesh-official/acme.sh#2305 (comment)
This - kind of - defeats the idea to require almost "nothing" from our users. I will focus on Duckdns. |
@rootzoll please be aware that the DuckDNS API does not work (with E.g. The cause for this is that For our current setup this doesn't hurt and is just something to keep in mind (and maybe point out to users). But my idea was to always set the primary subdomain and a wildcard: Also bare in mind that the certificate for |
@frennkie ok I added dynu.com to for the v1.6.1 release - works fine on my tests with ACME and LetsEncrypt. Marking for final testing. |
Tested it a few more times and works well. Will be part of v1.6.1 release. Cosing issue. |
There are at least two (free) services that offer DynDNS like features which seem to support ACME:
Works:
In testing:
Ruled out:
The text was updated successfully, but these errors were encountered: