But that’s just as much “automated” as our own Free SSL Certificates tool is if you’re using the Let’s Encrypt provider. GoGetSSL isn’t quite as automatic because they create a new CNAME record for every validation, but our Let’s Encrypt CNAMEs are consistent.
Looking at _acme-challenge.thebotfactory.net, it points to a CNAME record from acme-dns.io. Which is pretty much what we do too, but with our own DNS servers to push the TXT records to.
I also played around with the wildcard certificates, and it seems fairly straight forward to reproduce here. So then people would only have to add one CNAME record instead of two.
Web scraping has also crossed my mind, but it just seems too fragile to rely on website parsing for such an important feature.
Sadly, we aren’t any more able to automate this than you are. InfinityFree gets the hosting from iFastNet, and until they provide an API to install SSL certificates, I can’t automate it.
Interesting, I didn’t know some of those companies had ACME API’s! There might be something useful in there.
You’re using external software (Certify The Web) and an external service (Acme DNS). So I would say that’s most definitely with external tools.
There are tons of tools to issue Let’s Encrypt certificates. Certbot is the most well known one for Linux, but I’ve also used Dehydrated and GetSSL.
But the client area doesn’t use the “Linux tools” per se, it actually uses AcmePHP Core, a library which can be hooked into other PHP code bases. Like the client area.
No problem! I love discussions like this, it’s always great to learn from the experience of others!