Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:web:web-hosting:web-management:certificat-ssl [2016/05/31 16:50]
dedibox
en:web:web-hosting:web-management:certificat-ssl [2018/08/10 13:12] (current)
dedibox [HTTPS with Wordpress]
Line 1: Line 1:
 ====== HTTPS on cloud and web hostings ====== ====== HTTPS on cloud and web hostings ======
 +
 +<note tip> ​
 +**Requirements:​**
 +  * You have an account at [[https://​console.online.net|console.online.net]]\\
 +  * You have a web or cloud hosting
 +</​note>​
  
 {{en:​web:​web-hosting:​web-management:​https-twitter-lien-raccourci.jpg|}} {{en:​web:​web-hosting:​web-management:​https-twitter-lien-raccourci.jpg|}}
Line 15: Line 21:
 ===== Conditions ===== ===== Conditions =====
     - You have a web or cloud hosting at Online.net     - You have a web or cloud hosting at Online.net
-    - You have configured a <​nowiki>​DNS</​nowiki>​ record pointing to pfXXX.mutu-perf.online.net ​[212.47.231.228( A record for the domain and an A or CNAME record for each subdomain (or A * / CNAME *)+    - You have configured a <​nowiki>​DNS</​nowiki>​ record pointing to your platform: 
 + 
 +  * WEB HOSTING : pfXX-web.online.net **62.210.16.61** or **62.210.16.62** 
 +  * CLOUD HOSTING : pfXXX.mutu-perf.online.net ​**212.47.231.228** ( A record for the domain and an A or CNAME record for each subdomain (or A * / CNAME *)
  
 ===== How does it work? ===== ===== How does it work? =====
Line 23: Line 32:
 The site is then accessible via <​nowiki>​http://​www.domain.tld</​nowiki>​ or <​nowiki>​https://​www.domain.tld</​nowiki>​ The site is then accessible via <​nowiki>​http://​www.domain.tld</​nowiki>​ or <​nowiki>​https://​www.domain.tld</​nowiki>​
  
 +<note tip>SSL is enabled by default for all **WEB** and **CLOUD** hostings and does not require configuration from your side.</​note>​
  
 <​note>​ <​note>​
Line 33: Line 43:
  
 ===== How to force HTTPS for the whole site ===== ===== How to force HTTPS for the whole site =====
-To force a site to accept SSL, such as a <​nowiki>​CMS</​nowiki>,​ simply add the .htaccess file the following code:+To force a site to accept SSL, such as a <​nowiki>​CMS</​nowiki>,​ simply add the following code to the .htaccess file:
  RewriteEngine On  RewriteEngine On
  RewriteCond %{HTTP:​HTTPS} !on  RewriteCond %{HTTP:​HTTPS} !on
Line 46: Line 56:
 ===== Error messages ===== ===== Error messages =====
  
-There are two types of errors ​that may occur.+==== The Mixed Content issue ==== 
 + 
 +When using HTTPS, it needs to be used everywhere.\\ 
 +It means that all the loaded elements on the webpage (pictures, CSS, <​nowiki>​JavaScripts</​nowiki>​) have to be loaded through HTTPS as well. 
 + 
 +A website that loads for example <​nowiki>​JavaScript</​nowiki>​ scripts or external images by http, will display a https alert in the browser (e.g.: "non Secure Content"​). 
 + 
 +In some cases it could not display it (Chrome did that in some cases).
  
 ==== Insecure connection ==== ==== Insecure connection ====
Line 63: Line 80:
 You need to verify the <​nowiki>​DNS</​nowiki>​ records and force the regeneration by creating a sub-domain You need to verify the <​nowiki>​DNS</​nowiki>​ records and force the regeneration by creating a sub-domain
  
 +==== HTTPS with Wordpress ====
  
-==== Notes==== ​+When using Wordpress, you may encounter **Too many redirections** errors in your web browser.
  
-When using https, it needs to be used everywhere.+This can be fixed by installing the [[https://​wordpress.org/​plugins/​really-simple-ssl/​|Really Simple HTTPS]] plugin.
  
-For example a site that loads for example ​<​nowiki>​JavaScript</​nowiki> ​scripts or external images by httpwill display ​https alert in the browser (style "non Secure Content"​).+Make sure that your <​nowiki>​DNS</​nowiki> ​zone is configured to the correct hosting platformdepending on if you are using **Cloud** or **Web** hosting
  
-In some cases it could not display it (Chrome did that in some cases).+When using the plugin, make sure that the following lines are **not** present ​in your ''​*.htaccess''​ file:  
 + 
 +<​code>​ 
 +RewriteEngine On 
 +RewriteCond %{HTTP:​HTTPS} !on 
 +RewriteRule (.*) https://​%{SERVER_NAME}/​$1 [QSA,​L,​R=301] 
 +</​code>​
  
 +<note tip>If you have installed Wordpress according to the Wordpress documentation,​ simply replace in the table (prefix)_options the siteurl and home entries from https to http before installing the aforementioned plugin.</​note>​