How to fix connection not secure or not private errors at Hostinger

Fix connection not secure or not private errors at Hostinger by checking that your website is published, your domain points to Hostinger and has propagated, and HTTPS is forced. These browser warnings appear when the browser can’t verify your website’s identity or set up an encrypted connection. The usual causes are a missing SSL certificate, pending DNS propagation, or unpublished website content.

Resolve secure connection errors

Follow these steps to identify and fix the cause of the connection error:

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

You can also refer to this video tutorial for more options:

Following these steps will ensure your website establishes a secure connection for all visitors. Testing in an incognito window is the most effective way to confirm that the SSL is active and that the browser is no longer caching the old, insecure version of your site.