If Hostinger Lifetime SSL still shows Failed after two hours, first confirm that the site is on an eligible Hostinger hosting plan and its domain points to Hostinger. Then check DNS records and any CDN proxy, and reinstall the certificate from hPanel only after correcting the setup. A site that still says Installing may simply need more time; AI Builder sites use a separate, automatic SSL process.
Check whether the SSL installation has actually failed
In your Hostinger dashboard, go to Websites, open the relevant site’s Dashboard, then select Security → SSL. Hostinger says installation commonly takes 1–2 hours and may retry automatically. If the status is Installing, wait and refresh the page rather than uninstalling the certificate prematurely. If it remains Failed or Inactive after two hours, troubleshoot the domain setup.
Make sure the site uses the right SSL workflow
File-based sites on Hostinger hosting
The manual steps below apply to supported websites added to a Hostinger hosting plan, such as PHP/HTML sites and WordPress sites. If your domain is registered with Hostinger but the website is hosted elsewhere, that hosting provider—not Hostinger—manages the site’s SSL certificate. See Hostinger’s failed-installation guide for current eligibility details.
Hostinger AI Builder sites
AI Builder SSL is managed automatically. Publish the website and allow the automatic process to activate SSL; the manual install and reinstall controls described here do not apply. Hostinger explains this distinction in its Lifetime SSL installation guide.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
Check DNS and domain settings before reinstalling
Confirm that the domain points to Hostinger
The domain or subdomain must use Hostinger nameservers or point to the correct hosting IP through its A record. If it points elsewhere, or a recent DNS change has not propagated, Hostinger may be unable to validate the domain. DNS changes can take up to 24 hours to propagate, so allow time before judging a recent change as unsuccessful.
Temporarily turn off CDN proxying
If Cloudflare or another CDN proxies the relevant A record, switch it to DNS only while Hostinger issues the certificate. Once SSL shows Active, you can restore proxying. Hostinger lists domain pointing and CDN proxying among the checks in its troubleshooting instructions.
Rank #2
Look for conflicting records and hostname-length limits
Hostinger’s current troubleshooting guide advises checking for multiple conflicting A records and removing CAA records if present. It also states that the complete hostname—including any subdomain and extension—must be no longer than 64 characters. DNS edits can affect where your site resolves, so save the existing values before changing records, and verify the current Hostinger instructions before removing or replacing anything.
Uninstall and reinstall the failed certificate
Reinstall only after the domain points correctly and you have addressed applicable DNS or proxy issues. In hPanel, open the site’s Dashboard → Security → SSL, use the menu for the failed certificate to uninstall it, and then install a new one. Hostinger says that if the domain is correctly set up, SSL should become active within a few minutes after reinstalling. The official failed Lifetime SSL guide has the current interface steps.
Verify activation—and distinguish it from a browser warning
Check that hPanel reports Active, then open the website in a private or incognito window, or clear the browser cache. If you use both the root domain (such as example.com) and www (such as www.example.com), test both: one hostname may resolve securely while the other does not.
If SSL is active but the browser still warns, follow Hostinger’s guide to “Not secure” or privacy-connection errors. A page that loads but shows insecure elements or a broken layout may contain mixed content—for example, an image or script still requested over HTTP. That is a post-install issue to investigate, not evidence by itself that you need another certificate.
Quick Recap
Rank #4
How to choose the right next step
| What you see | What to do |
|---|---|
| Installing, less than two hours | Wait, refresh the SSL page, and allow Hostinger’s automatic retry. |
| Failed or Inactive after two hours on a file-based site | Confirm hosting eligibility and domain pointing; check proxying, DNS conflicts, and hostname length; then reinstall. |
| AI Builder site | Publish the site and let Hostinger manage SSL automatically. |
| Active, but a browser warns or the page has insecure elements | Check root and www coverage, then investigate browser-specific issues or mixed content rather than repeating certificate installation. |
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
