How to solve ERR_SSL_PROTOCOL_ERROR at Hostinger

The ERR_SSL_PROTOCOL_ERROR occurs when a browser cannot establish a secure connection with the server, often due to an SSL certificate issue or local configuration. While Hostinger installs a free SSL automatically on web, cloud and agency hosting plans, certain factors like pointing issues, propagation or unpublished status can trigger this error.

Before you start

Ensure the following before proceeding with SSL troubleshooting.

• Your domain must be pointed to Hostinger.
• You have waited up to 24 hours after a new domain registration or DNS changes for propagation to complete.
• If using Hostinger AI Builder websites, ensure your website is published and updated. Unpublished or draft websites may show SSL errors.
  • For Hostinger AI Builder websites (manual mode), refer to this guide: How to publish a website.
  • For Hostinger AI Builder websites (agentic mode), check this article: How to publish your Hostinger AI Builder app in agentic mode.

Troubleshooting

After verifying that your website is published, and the domain is pointing and propagated, follow these steps:

1. Use an incognito window. Open your website in a private or incognito browser window to rule out issues caused by local browser cache or history.
2. Verify domain pointing. Use a DNS checker tool to confirm that your domain points correctly to your website at Hostinger and that the records have fully propagated.
3. Check SSL validity. Use an SSL checker tool to verify the certificate.
   1. If you’re using a custom SSL, get in contact with your SSL vendor for further assistance.
   2. For custom PHP/HTML and WordPress websites using Lifetime SSL, uninstall the existing certificate and installing a new one.
      1. This option is not available for websites created using Hostinger AI Builder websites.

4. Adjust local security settings. Temporarily disable your device’s antivirus or firewall to ensure these programs are not blocking the secure protocol.

If you’re seeing a different SSL-related warning instead, see how to fix “Not Secure” or “Not Private” connection errors at Hostinger.

You can also check this video tutorial for more alternatives: