“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

Updating an Old Docker Version to Community Edition

The following was used to upgrade an antiquated version of docker to the newest community edition...

Can I setup SSL on my account?

Yes, you can purchase a secure certificate through us so you can use SSL. You can also give us...

How to create a temporary 302 redirect via htaccess

An easy way to create a temporary redirect from one page to another web page is to use the 302...

What is the location of curl?

Curl is located @ /usr/bin/curl

What are these htaccess files that keep popping up?

.htaccess files are default files the server uses to perform certain tasks. Features such as...