5 ms·
Sorry for the newbie question.... So if I have apache running http://example.com http://example.com on port 80 and I follow the instructions ($ lets-encrypt ex
by grecy 12y ago
Sorry for the newbie question....
So if I have apache running http://example.com http://example.com on port 80 and I follow the instructions ($ lets-encrypt example.com)
Will Apache now be correctly serving encrypted traffic on port 443 with a cert for https://example.com https://example.com ?
- haroldp 12y agoThat's the idea. It assumes you are using an OS with a package manager, and letting it manage your software and (to some extent) config files.
- st3fan 12y agoAnd if you don't, or if you don't want to, it is easy to configure Apache or any web server manually. All you really need are three things: * the letsencrypt command line tool that will do the API dance to request the certificate * a file in your web site root with a ownership verification token or a DNS record with said token * a configuration file snippet for your server I'm sure all of this will be documented very well.
- grecy 12y agoNice, thanks. (I'm running on Ubuntu, so should be good)
- bifurcation 12y agoThe ultimate vision is to make it even easier than that -- you set the "turn on HTTPS" option, and the platform auto-configures HTTPS with a certificate and appropriate ciphers. That will require upgrades to apache, nginx, IIS, etc., though, so in the meantime, we have the "lets-encrypt" script to semi-automate things.
- ivok 12y agoSo going from a single command to a different single command? How much simpler could it get?