4 ms·
It is relatively straightforward if you have a single site hosted on a well-supported operating system and web server. It suddenly becomes really, really compl
by jwr 7y ago
It is relatively straightforward if you have a single site hosted on a well-supported operating system and web server.
It suddenly becomes really, really complicated if you have multiple servers, multiple domains, nginx configurations that the tool does not expect (but insists on rewriting).
- dx034 7y agoThe rewrite is optional, it's also fairly trivial to let certbot create certificates and adapt nginx afterwards.
- squiggleblaz 7y agoYes, but at that point it's not two lines with let's encrypt any more. For my part, I had to write around a thousand lines of script and alter various existing code in order to switch from manual ssl (whenever the client paid for it) to automatic ssl (everywhere), because there was no way I was going to manually buy hundreds of certificates a year when I took over this role. Nowadays we're 100% ssl but it was harder for an existing person already accustomed to the existing system than doing nothing. I'm just too lazy to check a site every week and renew many certificates manually and copy around stupid files and generally go crazy. Plus, if it's automated, I think there's less chance of the keys being copied. So in my mind it was worth the effort, but it was surely effort.