No worries. It's kinda convoluted. 
That Git has quite the list of authenticators. But certbot only supports a handful of these natively right? GD is not something I can call from the command line.
2 Likes
Certbot has quite a few plugins...
Look at DNS Plugins and Third-party plugins in particular.
3 Likes
Yeah I have seen those. Just no GoDaddy one. Azure and AWS as well but all of these seem to be in the ACME repo as examples.
1 Like
Between you and me, I raised a huge stench about lack of support for GoDaddy Shared Hosting a couple of weeks ago that garnered quite a bit of attention. I created a topic in the #issuance-policy category that I have since dragged into the #lounge, which is only open to Regulars, Community Leaders, and Staff. I'm actually in the process of developing a full certificate management system driven from a webpage that has an integrated ACME client. This is specifically a solution for GoDaddy Shared Hosting. It will use http-01 challenges and thus avoid the whole dns api issue entirely. You are the only one who knows of this (so far). I can let you see the hidden topic if you wish, but it will only be available for a few minutes. 
3 Likes
Nice. Well I am calling it a day but maybe tomorrow. Wildcard certs are more useful for me so for now I live with the DNS challenges . I am developing a set of scripts that tie into a REST api for a multi-platform application delivery controller (NetScaler). There is already an HTTP version out there just no DNS one for wildcards. I have most everything working just need to resolve a few other issues.
Jeff
2 Likes
Sounds good. Enjoy the night my friend!
1 Like
There one hitch in this equation.
Which is that this is actually NOT a fact:
There is NO written guarantee that successful authorizations must be cached for any length of time.
3 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.