OVHCloud Web Hosting Status

Current status
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
FS#18027 - Activation of the HTTPS protocole
Scheduled Maintenance Report for Web Cloud
As you are aware, at OVH, we are very concerned about security. This is why, when Let's Encrypt launched, we wanted to support this initiative so that as many websites as possible could deploy HTTPS.

As we host several thousands of websites, we realise that we can play an important role in spreading encryption on the internet. So! We asked ourselves: how we can have as much impact as possible? We could have suggested letting you activate the HTTPS protocol for free through a button in the control panel. But that still wasn't simple enough in our opinion.

So instead we decided to enable the HTTPS protocol and encrypt connections to all websites on your web hosting packages. All of them. With no exception. Even existing websites.

We have already generated certificates for 95% of the web hosting accounts that we manage (this has been displayed on the Let's Encrypt graph since the beginning of May: We have a few cases left to deal with out of our 1.5 million accounts, but it is very likely that your web hosting package already has a certificate.

On our part, we had to change some parts of the infrastructure. Because encrypting connections on several millions of websites is no mean feat. To do this, we added a new load balancing block so that it can manage all of the encrypted flow. If you want to try it, it has been available in beta for a few days.

We are currently in the process of replacing our old load balancers with this new system. This will take some time, as we need to make sure that the service works without fail. At this point in time, 4 clusters have already switched to the new load balancer:

cluster012 (1000gp)
cluster013 (20gp)
cluster002 (90plan)
cluster007 (xxlplan)

You can check your web hosting cluster in the control panel, in the \"Cluster Access\" field. The other clusters will all be migrated in the upcoming days. We will specify which clusters have been deployed here.

So, if one of the clusters is relevant to you, how can you benefit from HTTPS?

You don't have to do anything! It is already enabled!

You just have to add the \"s\" in HTTPS when you type the URL and it will work.

Please note, your websites’ code may not be entirely compatible with HTTPS. If this is the case, we have written a guide which details the main
issues and their resolution:

All of your websites are accessible in HTTPS. In other words, your websites’ certificate includes all of the websites which you have made accessible from your web hosting package. There is nothing left for you to do!

Finally, for those who already have an SSL certificate, we haven't forgotten you. We are going to offer other types of certificates in the following days and you will be migrated to these new certificates. We will keep you informed.

The SSL compatible CDN is also in the pipeline. We still have some work to do on this before we can provide it, but it is also on the way.

The web hosting team


Date: 2016-05-20 09:17:27 UTC
The IPLB has been reconfigured correctly.

We have just returned cluster007 (xxlplan) behind our IPLBs. As such, this cluster now once again benefits from SSL certificates.

Date: 2016-05-17 18:42:21 UTC
We are currently preparing the deployment of new clusters. During deployment, we realised that there was an issue with some of our IPLBs which is likely to impact the service during load peaks. We decided to reset the configuration of these IPLBs.

While we are doing so, we have deactivated cluster007, which is based on one of these IPLBs. This cluster should be available again tomorrow.

Date: 2016-05-16 08:40:46 UTC
Many of you have noted that your HTTPS website returns the error \"Your connection is not secure\".
You get this error when there is no active certificate on your website. There could be a number of reasons behind this:

- Check that your website is on one of the four clusters deployed (cluster012, cluster013, cluster002 ou cluster007)
- If it is, check that your domain is pointing to your web hosting package's IP address. You can find your IP address in your control panel, in the IPv4 field.
- Finally, it could be that your certificate is not yet generated and that it is part of the 5% of certificates which we still have to generate. Do not worry, it is in progress and all of the certificates should be available next week (week commencing the 16th May)

Please do not hesitate to provide feedback on (subscribe on
Posted May 13, 2016 - 10:52 UTC