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.
Understand secure vs. not secure
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 HTTPhttps://is using HTTPS
When your website displays http:// in the URL instead of https:// you may encounter this site "Not Secure" message:
Read CloudFlare's Guide to HTTPS to learn more.
Troubleshoot a site
Clear a web browser's cache and cookies
Clearing your web browser's cache and cookies provides a clean slate. 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 how to clear cache and cookies in Chrome.
Learn how 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.
Note: When managing your browser settings to clear cache and cookies from your web browser, be sure to continue allowing third-party cookies to avoid experiencing the Login Page error.
Check if a 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 site domain into the address bar of your web browser (e.g.,
mysite.com)Click into the URL to expand and view the entire URL:
Warning: If your domain was connected to Kajabi using the nameserver method, do NOT set up a forwarding rule at your registrar. GoDaddy's forwarding feature (and some other registrars') resets your domain's nameservers back to the registrar's own servers, which will disconnect your site from Kajabi and cause 404 errors, redirect loops, and security warnings for your visitors.
If you used the nameserver method and arev seeing HTTP instead of HTTPS, contact Kajabi Support — the redirect to HTTPS is handled at the Kajabi/Cloudflare level and does not require a registrar forwarding rule.
If you used the subdomain (CNAME) method, a forwarding rule at your registrar is safe and appropriate, and you can now set up a forwarding rule with your domain host.
Set up a forwarding rule with the 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) 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 forwarding rule for popular hosting services:
Note: GoDaddy's 'Forwarding' feature resets nameservers.
Learn how to fix this or work around it.
Ensure that all five records have been added to your custom domain properly
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.