“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

Inode issues

There are many issues that can arise from reaching your inode limit. The inode limit is the total...

Can you write a script for me?

We do not write scripts but will be more than happy to guide you in the right direction. Most the...

When should I use ascii and when should I use binary?

Many FTP client programs support and auto mode to detect the proper upload type based on file...

https:// with Weebly

To enable and force https:// with your Weebly website, be sure to go into your editor area,...

Meta Redirect

Adding this code to your web page will redirect your visitors to any address that you have...