OVHcloud Web Hosting Status
Current status
Legend
- Operational
- Degraded performance
- Partial Outage
- Major Outage
- Under maintenance
HTTPS call from website itself or cron / Appels HTTPS depuis son site ou un cron
Scheduled Maintenance
Report for Web Cloud
Completed
Since the HTTPS deployment, it cannot be possible to call a link from their site with https using curl (PHP), or calling their website in HTTPS from a cron. The standard error message received is \"cURL error 35: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol\"
A workaround was to call http://myweb.site:443 instead of https://myweb.site.
We will deploy a solution to do https call working. But, in this case, the workaround will not work anymore. We planned to deploy it in January. We will add the deployment planning soon in this task, and on community.ovh.com and on web@ml.ovh.net mailing list (send an email to web-subscribe@ml.ovh.net to subscribe).
----------
Depuis le déploiement de HTTPS, il n'est pas possible d'appeler un lien de son propre site en HTTPS en utilisant curl (PHP), ou en appelant son propre site en HTTPS depuis un cron. L'erreur standard dans ce cas est \"cURL error 35: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol\".
Une solution était d'appeler http://monsite.web:443 à la place de https://monsite.web.
Nous allons déployer une solution qui va rendre le HTTPS fonctionnel. Cependant, avec cette solution, le moyen détourné ne fonctionnera plus. Nous prévoyons de le déployer en janvier. Le planning du déploiement sera ajouté dans cette tâche prochainement, sur community.ovh.com et sur la mailing list web@ml.ovh.net (envoyez un email à web-subscribe@ml.ovh.net pour vous inscrire).
Update(s):
Date: 2017-02-09 07:29:04 UTC
Done on cluster020 since 8.28am UTC+0001
Date: 2017-02-09 06:27:40 UTC
Done on cluster015 / mp since 7.25am UTC+0001
Date: 2017-02-08 12:47:26 UTC
Done on cluster013 / 20gp since 1.47pm UTC+0001
Date: 2017-02-08 12:44:48 UTC
Done on cluster011 / 300gp since 1.28pm UTC+0001
Date: 2017-02-08 10:46:31 UTC
Done on cluster010 / 60gp since 11.45am UTC+0001
Date: 2017-02-08 10:19:20 UTC
Done on cluster007 / xxl since 11.15am UTC+0001
Date: 2017-02-03 06:44:16 UTC
3 days ahead :
Done on cluster003 and cluster006 since 7:40 am UTC+1
Date: 2017-02-02 07:06:54 UTC
Done on cluster002 since 8:00 am UTC+1
Date: 2017-02-02 06:43:52 UTC
Done on cluster005 since 7:40 am UTC+1
Date: 2017-02-01 14:45:47 UTC
Done on cluster021 since 3:30 pm UTC+1
Date: 2017-02-01 08:20:23 UTC
Done on cluster017 since 8:00 am UTC+1
Date: 2017-01-31 08:12:45 UTC
Done on cluster014 since 8.00 am UTC+1
Date: 2017-01-30 13:08:07 UTC
Done on cluster012 / 1000gp since 7.00 am UTC+1
Date: 2017-01-23 14:38:13 UTC
Here is the deployment planning.
2017-01-30: cluster012
2017-01-31: cluster014
2017-02-01: cluster017 & cluster021
2017-02-02: cluster002 & cluster005
2017-02-06: cluster003 & cluster006
2017-02-07: cluster007 & cluster010
2017-02-08: cluster011 & cluster013
2017-02-09: cluster015 & cluster020
Of course, this planning could changed in case of unplanned issue.
A workaround was to call http://myweb.site:443 instead of https://myweb.site.
We will deploy a solution to do https call working. But, in this case, the workaround will not work anymore. We planned to deploy it in January. We will add the deployment planning soon in this task, and on community.ovh.com and on web@ml.ovh.net mailing list (send an email to web-subscribe@ml.ovh.net to subscribe).
----------
Depuis le déploiement de HTTPS, il n'est pas possible d'appeler un lien de son propre site en HTTPS en utilisant curl (PHP), ou en appelant son propre site en HTTPS depuis un cron. L'erreur standard dans ce cas est \"cURL error 35: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol\".
Une solution était d'appeler http://monsite.web:443 à la place de https://monsite.web.
Nous allons déployer une solution qui va rendre le HTTPS fonctionnel. Cependant, avec cette solution, le moyen détourné ne fonctionnera plus. Nous prévoyons de le déployer en janvier. Le planning du déploiement sera ajouté dans cette tâche prochainement, sur community.ovh.com et sur la mailing list web@ml.ovh.net (envoyez un email à web-subscribe@ml.ovh.net pour vous inscrire).
Update(s):
Date: 2017-02-09 07:29:04 UTC
Done on cluster020 since 8.28am UTC+0001
Date: 2017-02-09 06:27:40 UTC
Done on cluster015 / mp since 7.25am UTC+0001
Date: 2017-02-08 12:47:26 UTC
Done on cluster013 / 20gp since 1.47pm UTC+0001
Date: 2017-02-08 12:44:48 UTC
Done on cluster011 / 300gp since 1.28pm UTC+0001
Date: 2017-02-08 10:46:31 UTC
Done on cluster010 / 60gp since 11.45am UTC+0001
Date: 2017-02-08 10:19:20 UTC
Done on cluster007 / xxl since 11.15am UTC+0001
Date: 2017-02-03 06:44:16 UTC
3 days ahead :
Done on cluster003 and cluster006 since 7:40 am UTC+1
Date: 2017-02-02 07:06:54 UTC
Done on cluster002 since 8:00 am UTC+1
Date: 2017-02-02 06:43:52 UTC
Done on cluster005 since 7:40 am UTC+1
Date: 2017-02-01 14:45:47 UTC
Done on cluster021 since 3:30 pm UTC+1
Date: 2017-02-01 08:20:23 UTC
Done on cluster017 since 8:00 am UTC+1
Date: 2017-01-31 08:12:45 UTC
Done on cluster014 since 8.00 am UTC+1
Date: 2017-01-30 13:08:07 UTC
Done on cluster012 / 1000gp since 7.00 am UTC+1
Date: 2017-01-23 14:38:13 UTC
Here is the deployment planning.
2017-01-30: cluster012
2017-01-31: cluster014
2017-02-01: cluster017 & cluster021
2017-02-02: cluster002 & cluster005
2017-02-06: cluster003 & cluster006
2017-02-07: cluster007 & cluster010
2017-02-08: cluster011 & cluster013
2017-02-09: cluster015 & cluster020
Of course, this planning could changed in case of unplanned issue.
This scheduled maintenance affected: Web Hosting || Datacenter GRA (Cluster002, Cluster003, Cluster006, Cluster007, Cluster011, Cluster012, Cluster013, Cluster014, Cluster015, Cluster017, Cluster020, Cluster021, Cluster023, Cluster024, Cluster025, Cluster026, Cluster027, Cluster028, Cluster029, Cluster030, Cluster031).