4 ms·
Looking at guides for LetsEncrypt on internal IPs/domains, it seems to be as painful as creating and managing your own CA: https://geontech.com/using-letsencryp
by makeitdouble 5y ago
Looking at guides for LetsEncrypt on internal IPs/domains, it seems to be as painful as creating and managing your own CA:
https://geontech.com/using-letsencrypt-ssl-internally/ https://geontech.com/using-letsencrypt-ssl-internally/
- pests 5y agoI had a chance to skim through the link you posted - they are doing the http challenge verification (in step 6) for some reason which involves forwarding their domain into their internal network. The DNS methods we already mentioned does not involve any of that - just a simple zone file change or a few clicks in a web UI to add a new record.
- jupp0r 5y agoDNS challenge is easy to pass and automate if you can programmatically add txt records to your DNS zone. Every major cloud provider supports this with command line tools, so it's a matter of moving the DNS zone there and writing a shell script and a cron item in the worst case.
- pests 5y agoExactly. The steps for an intranet or regular domain is exactly the same if you use the DNS challenge as the web server is no longer involved regardless.
- ivoc 5y agoCan someone productize this as a service please ?
- jupp0r 5y agoHere you go: https://cloud.google.com/load-balancing/docs/ssl-certificates/google-managed-certs https://cloud.google.com/load-balancing/docs/ssl-certificate...