Web Hosting who support Let's Encrypt


MyDevil.net (unfortunately, in Polish language only)
Facebook info: https://www.facebook.com/MyDevil.net/posts/1270477369645033
Twitter info: https://twitter.com/MyDevilnet/status/675392511892955136


Hostinger have no plans to support LE

Applying Let's Encrypt SSL through WP Encrypt

Thank! added.

@iNathan Thanks, do you have a link by any chance of their confirmation of no plans for supporting LE?


why mydevil on the not supported list? they even have a wiki entry for it on how to make it work.


Rolling since day one :wink: https://www.cyon.ch/blog/Lets-Encrypt-ist-da-Kostenlose-SSL-Zertifikate-fuer-alle


Don’t hosting providers run into problems with the “10 registrations per IP in 3 hours” limit?


I read they didnt support it but found the wiki entry. Added them!

@zedpelin Thanks! added!

@ardijyrgens That means 80 registrations per day :wink:


I don’t have a link as I sent them a support ticket regarding Let’s Encrypt.

I’ve uploaded the picture but I’ll see if I can get a more public response.

My provider doesn't want to cooperate

No, hosting providers set up one account per server (== per IP) and then request all certificates with this account.


We supported letsencrypt from the first hour of public beta: https://www.schokokeks.org/
(Fully automated, customers just switch on “Let’s Encrypt” for their host and all magic is done behind the scenes.)

But apart from that: I don’t like such lists. They are incomplete. And they don’t represent details such as if it’s working stable or easy to use. If your desired hoster cares about security does not simply mean if letsencrypt is supported or not. There’s more about that topic.


KeyCDN just launched free SSL based on Let’s Encrypt for all their customers


At Pressjitsu we rolled out full support for Let’s Encrypt at launch day, we actually had a party. We don’t use the LE client though, we have custom Python scripts that handle everything, including updating nginx configs for user nodes using our configuration templating and scheduling a certificate renewal job.

For our customers’ domains we never hit the current (or private beta) rate limiting since the requests originate from the customer node and each has a unique IP address.


That’s true, but you have to do something smart when 11 users request a certificate within 3 hours. Also afaik renewals count towards rate limiting as well, so that could potentially be a problem, but hey, you can always tunnel it through a different IP…


Thank you, added hosting.

That’s why people should contact support before signing up to a hosting provider to confirm everything they are looking for. This is common sense. I’ve always talked to customer care before signing up because then I will actually know what I am getting. Maybe this isn’t common?

This list will never be perfect, but it’s better than having people asking who is supported over and over and over. Should we give a star based system for ease of setup?

Extend SSL certificate

novatrend.ch launched free SSL certificates based on Let’s Encrypt for all hosting customers. It’s well integrated in cpanel and customers can request and install the certificate with just one click. The certificate is automatically renewed in the background.


That would be madly expensive (assuming you mean IPv4). What provider does that?


@hobarrera: Did you read my message in the right context? I replied to post #9.
One Server has one (or few) IP address, registers one LE account, requesting many LE certificates with this account.

What’s the expensive part about that?!


Thank you; I have updated my OP with this information!


We (https://www.openminds.be) support it. Even more: shared hosting customers first :slight_smile:

We currently have it integrated in our controlpanel (written in-house), and have it enabled for a few customers. Once of the reasons we don’t enable it for everyone, is the API limitations…

So yes, you can add us to the list, and if there is a way for hosting providers to get around the API limitations, please let us know :slight_smile:


Which limitation are you running into? If it’s the per domain limit because you use a shared domain for your customers, you probably should add that domain the public suffix list anyway. If it’s the registrations per IP limit, I’d argue that it’s okay if you use a single shared account, since you handle it for you customers. If you have customers with their own domains but too many third level names, consider issuing a cert for all of them together, since you can add 100 SANs into a single cert.