Welcome to the InfinityFree community forum! Good to have you here.
Most people answering here are volunteers. They’re often the fastest source of help. Admin (the only staff member) checks in about once a day for issues on our end.
Volunteers can’t see your account or website. Share what you actually see, like error messages and what happens when you try something. That’s more useful than your theory of what’s wrong.
AI tools often get InfinityFree wrong. If a volunteer’s advice differs from what an AI told you, please try the volunteer’s suggestion first.
Solving an issue is a joint effort. Try the suggestions you get and report back what happened.
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.
The empty “SSL Certificates” list is normal for your site. According to our article, all free subdomains are covered by a system-wide SSL certificate that is active from the moment the subdomain is created. Nothing gets installed on your account, so there’s nothing for you to restore or reinstall, and waiting won’t change it. hahos.free.je is a direct subdomain, which is the kind the article says is covered.
The article is here:
Your lack of an .htaccess file or HTTPS redirect isn’t the cause. Those control whether visitors get sent to HTTPS, not whether the certificate is valid.
I can’t tell from the post why your browser rejects the certificate. Two checks would help:
Open https://hahos.free.je/HAHOS/trang_chu.php in a private window on a different network, for example a phone on mobile data. Does the same error show up? If it doesn’t, the problem is on your device or network, such as the device clock, antivirus HTTPS scanning, or a school or college network.
In the browser’s warning, open the certificate details and tell me who issued the certificate (the “Issued by” line) and what domain it is for.
I checked your website and for SSL, everything is working as intended: your website is fully protected with our system wide certificates.
There have been few similar cases recently and we never were able to find out what caused the issue.
My best guess for these types of issues is something intercepting the request between you and our servers, and responding with their own, invalid SSL certificate.
But the real tell is to check the certificate that your browser actually sees. On the certificate warning page, or in the address bar, should be an option to view information about the SSL certificate used. Can you check that and share a screenshot of it here so we can see if it reveals anything?