Status: Issued, created 2026-10-11 06:33 UTC, expires 2027-01-09 UTC
I clicked “Install SSL Certificate Automatically” and the page says “The SSL certificate has been installed! It may take up to 1 hour for it to become active.” That was days ago, so it should already be active.
Step 5 “Verify Installation on cheezybeats.shop” still shows Status: Not Found, Issuer: -, Expires at: -
The _acme-challenge.cheezybeats.shop CNAME is present in my DNS Records page.
Questions:
Is the certificate really installed on the server for cheezybeats.shop?
If not, why does the dashboard say it was installed, and what do I need to do to fix it?
Is there a problem with the server at 185.27.134.217 that causes the connection to time out (even before SSL)?
Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.
Your domain is attached to your hosting account, and the website IP on the account is 185.27.134.217, the same one your A records point to. So the DNS and domain setup looks right. The first thing to find out is whether the timeout happens only for you or for everyone.
Please run your site through the HTTP test on check-host.net and tell me whether most locations succeed or fail. Also try opening http://cheezybeats.shop (typed in full, not https) on mobile data with Wi-Fi off, or through a VPN.
I’m asking because this knowledge base article covers connection timeouts like yours:
It says a timeout means your browser couldn’t set up a connection at all, which is a different problem from an SSL error. If check-host shows failures from most locations, the server or the website itself has a problem. If it works from most locations but not for you, something is blocking you: your device, your network or provider, or the server blocking your IP address. That article also covers that last case.
That also affects your SSL questions. If nothing can connect to the site, that may be why “Verify Installation” shows Not Found. I can’t confirm that from here. Another topic had the same “installed but Not Found” symptom, and its author said the cause turned out to be on the hosting side. That thread didn’t say what the cause was, so I wouldn’t assume yours is the same.
The check-host result will show which case you’re in. If it fails from most locations, a person will need to look at the server side, because nothing you can change on your end will fix it.
I simplified your message to make it easier to understand for others in a recent attempt to streamline support requests.
First of all your website works for me. if it works for you too, and the only problem is that the Client Area displays some scary warnings, you could just ignore that.