“Not Secure” Web Error

In this day and age browsers now default to using https:// instead of http://. We make SSL available to all of our clients for free with Let's Encrypt SSL. As a result of this, it is important to make your content surface-able via https:// by not using http:// in your code when you link to pages, images, .css, .js, .etc

An easy way to track the offenders is to view your source and perform a search for http:// and change those over to https:// in your code.

You may also create an .htaccess in your public_html directory with the following contents:


RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteRule ^(.*)$ https://www.yourdomain.com/$1 [R,L]


which will redirect any request for http:// to https://

 

If you are using WordPress, installing the Really Simple SSL plugin makes life a lot easier for this. Once it is installed set your WordPress settings to point the domain to https:// instead.

 

  • 2 Users Found This Useful

Was this answer helpful?

Related Articles

When I upload an htaccess file it disappears

On unix/linux systems, files that start with a . are considered hidden so many ftp programs do...

Cross Origin Request Error

When receiving a cross-origin / cross original request, CORS header 'Access-Control-Allow-Origin'...

Adding HTML to Site Builder

When adding HTML code/source in site builders be sure you are in HTML mode. There is often a...

How to use SharedSSL

SharedSSL is now available with our Ultra Unlimited. It is not as professional looking as having...

How do I parse html files as shtml?

Create an .htaccess file in the directory needed and add the following: AddHandler...