ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1010)
Chrome also shows a privacy/certificate error when opening the WordPress admin page.
Other Information
The hosting account is Active and WordPress was installed successfully on October 8, 2026.
The hosting dashboard DNS record and public DNS both resolve bonnin-journal.great-site.net to 185.27.134.55. TLS validation with the hostname fails with the error above.
The SSL tool says free subdomains use automatic SSL and custom certificate orders are not supported. Could you check the automatic SSL certificate for this hostname on this server?
The current IP outage notice lists 185.27.134.99 and 185.27.134.153, rather than this IP.
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.
I can’t tell from the topic whether the expired certificate is really being served for your hostname, so I need one detail. When Chrome shows the certificate error, open the certificate details and tell me which hostname the certificate was issued to, who issued it, and its “valid to” date. If it’s issued to a different hostname, that points to something other than your site’s own certificate expiring.
It would also help to know if your other free subdomain under great-site.net shows the same error. That one is on a different server, so the result would show whether this is specific to the new account or to the subdomain type.
I found one earlier topic with a similar symptom: an expired certificate on a free great-site.net subdomain, with the same “free subdomains have SSL by default” message in the SSL tool. It has no confirmed answer, so I can’t say your problem has the same cause.
Thank you for checking. Here are the certificate details observed from our connection on 2026-10-08 at 08:45 UTC, using Python TLS with hostname/SNI. The PC time matches UTC.
Issuer: ZeroSSL ECC DV SSL CA 2 / ZeroSSL GmbH / AT
Valid from: 2026-09-03 00:00:00 UTC
Valid until: 2026-12-02 23:59:59 UTC
The two servers return different certificates from this connection. Could staff check whether an older automatic certificate is still being served on 185.27.134.55, possibly for some TLS clients or routes, and update it if necessary? We have not bypassed the browser warning or disabled certificate verification for site access.
Your domain name was only 20 minutes old by the time you posted this, so DNS caching is a very likely candidate. It can take up to 72 hours, usually less than 24 hours, so 20 minutes is extremely new.
This is possible, because unused subdomains are pointed to the domain 185.27.134.24, but that one doesn’t have the latest SSL certificates for free subdomains, so you get an SSL error. That’s a known bug we need to work on.
Two things you could check (either or both, they both check the same), assuming you’re still having this issue:
Do a DNS lookup from your own computer: open a terminal and run the command bonnin-journal.great-site.net. If it returns 185.27.134.55, it’s not DNS. If it returns 185.27.134.24, then my guess was right and it’s DNS.
Click the buttons in Chrome to ignore the certificate error and continue anyway, then check if you actually see a WordPress admin page, or a page that says DNS Resolution Error.
