4 ms·
My experience with Let's Encrypt hasn't been great, but that's not LE's fault. Long story short, don't use Namecheap, at the very least not their shared servers
by Fej 10y ago
My experience with Let's Encrypt hasn't been great, but that's not LE's fault. Long story short, don't use Namecheap, at the very least not their shared servers.
From their support:
"Though we believe increased web security is a good thing, we also think that using certificates from free providers can get more risk and uncertainty into your business.
Additionally, we would like to draw your attention to several disadvantages and drawbacks of Let's Encrypt certificates:
1. No OV/EV support or possibility (no possibility to issue a certificate with medium or high assurance and user trust level);
2. Insufficient level of domain validation and the absence of brand validation ( All publicly trusted CAs are flagging the certificate containing IT, financial and other public words, brands etc for additional security checks, which is not applicable for LE.)
3. Short validity period (for LE certificates - only 90 days, for all trusted certificate provides - up to 39 months).
Since the nature of shared and reseller hosting implies having a significant number of independent customers' accounts on the same server instance, we cannot put at risk our other clients by enabling not fully secure technology.
These and other concerns (for example the fact that ACME-script for Let's Encrypt requires root access and is able to overwrite server configs) make us refrain from supporting Let's Encrypt on our shared servers. We hope for your kind understanding on the matter."
----------
Feel free to reply with other hosts that don't support LE, so I can avoid them (and hopefully others too!)
- devwastaken 10y ago"These and other concerns (for example the fact that ACME-script for Let's Encrypt requires root access and is able to overwrite server configs) make us refrain from supporting Let's Encrypt on our shared servers. We hope for your kind understanding on the matter." This is one of the problems I've had with LE, and the community defends it by saying that there are other tools, and forks of tools you can use, when the problem with those is that they could easily go out of date if LE changes anything and they'd never be fixed. Updating your certificates needs to be done in a reliable and contained manner, but nobody wanted to admit that LE tools doesn't do that. I don't recommend LE unless you're actively maintaining a server and can invest the time into creating your own contained update script. I know hosters like Dreamhost have it built in and will auto-update for you, which is nice.