{"id":1530,"date":"2019-02-08T10:35:56","date_gmt":"2019-02-08T10:35:56","guid":{"rendered":"https:\/\/blog.hostinger.io\/support\/2019\/02\/08\/1583317-how-to-fix-not-secure-or-not-private-connection-errors-at-hostinger\/"},"modified":"2026-04-27T12:27:31","modified_gmt":"2026-04-27T12:27:31","slug":"1583317-how-to-fix-not-secure-or-not-private-connection-errors-at-hostinger","status":"publish","type":"post","link":"https:\/\/www.hostinger.com\/support\/1583317-how-to-fix-not-secure-or-not-private-connection-errors-at-hostinger\/","title":{"rendered":"How to fix connection not secure or not private errors at Hostinger"},"content":{"rendered":"

A ‘Not Secure’ or ‘Your connection is not private’ warning appears when a browser cannot verify your website’s identity or establish a secure encrypted connection. This typically occurs due to missing SSL certificates, pending domain propagation, or unpublished website content on Hostinger platforms.<\/p>

Resolve secure connection errors<\/h2>

Follow these steps to identify and fix the cause of the connection error:<\/p>

    \n
  1. Verify the website status<\/strong>. If your website is created using Hostinger Website Builder or Hostinger Horizons, ensure it has been published at least once. If already live, click Update<\/strong> or Publish<\/strong> after making any change and wait a few minutes.<\/li>\n
  2. Point your domain<\/strong>. Hostinger Lifetime SSL requires the domain to be pointing<\/a> to your website at Hostinger, using nameservers or alternative pointing methods (A record for custom PHP\/HTML websites, and CNAME records for Hostinger Horizons and Hostinger Website Builder).<\/li>\n
  3. Allow for propagation<\/strong>. If you recently registered your domain or updated its DNS records, wait up to 24 hours for propagation<\/a> to complete. After this period, clear your browser cache<\/a> or check the site in an incognito window.<\/li>\n
  4. Check for www<\/code> vs. root domain consistency<\/strong>. Sometimes a website is secure at domain.tld<\/code> but shows a warning at www.domain.tld<\/code>, or viceversa.\n
      \n
    1. Ensure your domain is fully pointed to Hostinger, as Hostinger Lifetime SSLs are designed to automatically cover both versions.<\/li>\n<\/ol>\n<\/li>\n
    2. Test the HTTPS protocol<\/strong>. Manually enter https:\/\/<\/code> followed by your domain in the browser address bar (e.g., https:\/\/domain.tld<\/code>). If the site loads with a padlock icon, follow the steps to force HTTPS<\/a> in your hosting settings so visitors are automatically redirected to the secure version.<\/li>\n
    3. Inspect for mixed content<\/strong>. If the website loads but the layout appears broken or “insecure” elements are flagged, it is likely due to mixed content<\/a>. This occurs when a secure page attempts to load resources like images or scripts via an insecure HTTP connection.<\/li>\n
    4. Check for protocol errors<\/strong>. If you specifically get the ERR_SSL_PROTOCOL_ERROR<\/a> message, the SSL certificate may be have failed. Uninstall the SSL through your hPanel and perform a new installation to reset the protocol.<\/li>\n<\/ol>

      You can also refer to this video tutorial for more options:<\/p>

      \n