Connection issues on 31st of August

On August 31st at around 7:30 UTC, reports started coming in about SSL errors on websites hosted here, mostly ERR_SSL_PROTOCOL_ERROR. By the time I was able to check at 16:00 UTC, the problem appeared to have been resolved already.

From what I’ve seen, HTTPS on free subdomains stopped working for the duration of the outage. I haven’t seen reports of custom domains being affected. Websites that were available on HTTP were still accessible.

I don’t know what caused it. InfinityFree runs on hosting infrastructure operated by iFastNet, and problems at this level are theirs to diagnose and resolve. It seems they identified and fixed it on their end.

I’m sorry for the disruption. A multi-hour SSL outage is a serious problem for anyone whose site was affected, and I understand the frustration in the topics that were opened today.

If your website is still showing SSL errors, please reply here with your domain so I can look into it.

It’s possible that other problems occurred today that I haven’t identified yet, or that were caused by the same underlying issue. If you ran into something else today that wasn’t SSL related, please open a topic describing what you saw, with your domain, rather than replying to an existing one.

There are a number of open topics about this. I’m closing them and pointing them here, since there’s nothing further to add to them individually.

Hi, i am having again problem in damatta.ct.ws, if you can have a look i would be honored

New issue. The name servers are down so all sites hosted here are down till it’s fixed

Please see the banner at the top of the page

I received more information about what happened.

The specific issue was caused by SSL renewal failing due to an outage at Let’s Encrypt. Due to how the SSL certificate renewal worked in the system, this resulted in temporarily no SSL certificate being available for free subdomains at all.

The certificates have been renewed now so this issue has been resolved for now.

It also definitively means that no custom domains were affected by this.