---
title: How to enable HTTPS for Webhosting Classic
description: This page explains how to enable HTTPS for Webhosting Classic
tags: webhosting https webhosting-classic ios
dates:
  validation: 2025-09-03
  posted: 2021-08-05
---
import Requirements from '@macros/iam/requirements.mdx'
import WebhostingOnline from '@macros/webhosting/webhosting-online.mdx'

import image from './assets/scaleway_insecure_connection.webp'
import image2 from './assets/scaleway_connection_failed.webp'


<WebhostingOnline />

<Requirements />

- A Dedibox account logged into the Online [console](https://console.online.net)
- Created a **Webhosting Classic**

Scaleway Dedibox offers HTTPS on all its webhosting services by default. HTTPS allows you to secure the exchanges between the client (visitor of your site) and the server (our platform).

It is usually preferred for online shops, but HTTPS is becoming more and more a standard on the web.

The certificate is issued by [Let's Encrypt](https://letsencrypt.org), an initiative that allows the generation of free SSL certificates known by all browsers.

<Message type="tip">
  TLS/SSL is enabled by default for all webhostings and does not require any configuration from you.
</Message>

<Message type="note">
  TLS/SSL is only compatible with OS/browsers that support [SNI](https://en.wikipedia.org/wiki/Server_Name_Indication). This means that the following clients cannot connect to sites hosted in HTTPS:
  * Windows XP (IE6/IE7)
  * Android 2.x
  * Versions below iOS 4 (iPhone)
</Message>

## How to force HTTPS for the whole website

To force a site to accept SSL, such as a CMS, simply add the following code to the `.htaccess` file:

```
RewriteEngine On
RewriteCond %{HTTP:HTTPS} !on
RewriteRule (.*) https://%{SERVER_NAME}/$1 [QSA,L,R=301]
```

## How to disable HTTPS for the whole website

To disable SSL, you need to put the following code in the `.htaccess` file

```
RewriteEngine On
RewriteCond %{HTTP:HTTPS} on
RewriteRule (.*) http://%{SERVER_NAME}/$1 [QSA,L,R=301]
```

## How to troubleshoot HTTPS issues

### How to fix 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, JavaScripts) have to be loaded through HTTPS as well.

A website that loads, for example, JavaScript scripts or external images by HTTP, will display an HTTPS alert in the browser (e.g.: “non Secure Content”).

In some cases, it could not display it (Chrome did that in some cases).

### How to fix the "insecure connection" issue

<Lightbox image={image} />

This may happen for example if the subdomain does not exist in the certificate.

In this case, you need to add the subdomain in the console, or if it exists already to add/delete it - or to create another subdomain (this will force the regeneration of the certificate).

### How to fix the "connection error" issue

<Lightbox image={image2} />

This error message means that there is no certificate for this domain. You need to verify the DNS records and force the regeneration by creating a subdomain from the Dedibox console.

### How to fix the "too many redirections" issue

When using WordPress, you may encounter **Too many redirections** errors in your web browser.

This can be fixed by installing the [Really Simple HTTPS](https://wordpress.org/plugins/really-simple-ssl/) plugin.

When using the plugin, make sure that the following lines are not present in your `.htaccess` file:

```
RewriteEngine On
RewriteCond %{HTTP:HTTPS} !on
RewriteRule (.*) https://%{SERVER_NAME}/$1 [QSA,L,R=301]
```

<Message type="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.
</Message>