How to Troubleshoot Site Not Secure Message
If you receive a "Site Not Secure" error message when accessing a Product or Page, refer to this guide to ensure that your site is secure.
In this article:
Understanding Secure vs. Not Secure
Site Not Secure Message:
What can cause this message?
This message can be caused by conflicting temporary internet files (from web browser caching) or your domain may be directing your visitors to your site using HTTP instead of HTTPS.
What is the difference between HTTP and HTTPS?
In short, HTTPS is HTTP encrypted. The S in HTTPS stands for "secure." HTTPS uses an encryption protocol known as a Secure Sockets Layer (SSL) to encrypt HTTP requests and responses. As a result, HTTPS is more secure than HTTP.
To determine if your site is using HTTP or HTTPS:
-
http://is using HTTP -
https://is using HTTPS
When your website displays http:// in the URL instead of https:// you may encounter a "Site Not Secure" message:
Read CloudFlare's Guide to HTTPS to learn more.
Troubleshoot your site
Step 1. Clear your web browser's cache and cookies
Clearing your web browser's cache and cookies provides a "clean slate" for you. Your browser will be reset and you can try again with a fresh browsing setup.
Read popular web browser guides on clearing your browser's cache:
- Learn to clear cache and cookies in Chrome.
- Learn to clear history, cache, and cookies in Safari.
If you are using another web browser, check its support site for instructions on clearing cache and cookies.
Step 2. Check if your domain redirects to http or https
If your cache and cookies have been cleared but the "Not Secure" message persists, check to see if your website is using http://or https://:
- Enter your domain into the address bar of your web browser.
- Click into the URL to expand and view the entire URL:
Step 3. Set up a forwarding rule with your domain host
In order to secure your custom domain, ensure that you've set up a forwarding rule for your domain to always go to https://.
Each domain provider has their own flow for setting up a forwarding rule, so depending on your domain host (e.g., GoDaddy, Bluehost, etc.) your setup may differ slightly.
If your custom domain still requires a forwarding rule to always go to https://, refer to the guide corresponding with your domain provider. If you're using another domain provider, please refer to their support site for instructions on creating a forwarding rule.
Learn how to add/edit a Forwarder for a few popular hosting services:
Step 4. Ensure that all 5 records have been added to your custom domain properly
Learn more about configuring DNS settings in Kajabi.
Still Experiencing Issues? Contact Support!
Lastly, if you've cleared your browser's cache and cookies and your custom domain is set to always go to https:// instead of http://, please reach out to our support team.
And that's how to troubleshoot the Site Not Secure message! Please vote below and let us know if you found this article helpful. We value your feedback. Thanks for being the best part of Kajabi!