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 [2017/05/11 11:06]
dedibox [The Mixed Content issue]
en:web:web-hosting:web-management:certificat-ssl [2018/08/10 13:12]
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 69: Line 79:
 This means there is no certificate for this domain. ​ This means there is no certificate for this domain. ​
 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 ====
 +
 +When using Wordpress, you may encounter **Too many redirections** errors in your web browser.
 +
 +This can be fixed by installing the [[https://​wordpress.org/​plugins/​really-simple-ssl/​|Really Simple HTTPS]] plugin.
 +
 +Make sure that your <​nowiki>​DNS</​nowiki>​ zone is configured to the correct hosting platform, depending on if you are using a **Cloud** or **Web** hosting. ​
 +
 +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>​