Since yesterday afternoon (October 31st), many website are showing SSL errors.
What are the symptoms of this issue?
Some of the errors you may see include:
SSL_ERROR_INTERNAL_ERROR_ALERT (Mozilla Firefox)
ERR_SSL_PROTOCOL (Google Chrome)
525 SSL Handshake failed (Cloudflare)
What is causing this issue?
iFastNet is currently making some changes to how SSL is handled on the free hosting platform. In preparation of this, the default, self signed SSL certificate has been removed from the system.
If your website currently relies on the self signed SSL certificate (for example, if youâre using it with Cloudflareâs âFullâ SSL mode), your website will not work over HTTPS.
What can I do to fix this?
There are a couple of things you can do to fix this, depending on how you use the self signed SSL certificate.
If youâre using Cloudflare, you can switch your website from âFullâ SSL mode to âFlexibleâ. However, not every website will like it if they are configured to use HTTPS URLs but they donât detect the SSL connection on the server themselves. If that happens, youâll likely see a redirect loop error (like ERR_TOO_MANY_REDIRECTS). Youâll need to check the documentation of your software or search the web for a solution which works for you.
You can install a valid SSL certificate signed by a real certificate authority. These certificates still work (both with and without having Cloudflare on your site). You can get an SSL certificate like that using the SSL Certificates tool in the client area.
Disable HTTPS on your site and only use HTTP at this moment.
When will this issue be resolved?
We expect the first changes to go live within the next 48 hours. However, this may not fix all websites immediately. Itâs highly recommended to implement one of the workarounds listed above to bring your website back online.
A week on, and my site is still entirely inaccessible. Admin/folks, do you all have any idea when this SSL issue is to be resolved? http also not working for Wordpress admin pagesâŠ
I know! Driving me insane! Iâm moving free host! I understand that itâs free and I canât expect much, but the service has been abysmal. âWeâre changing thisâ; âweâre updating thatâ. But when problems are solved I donât notice a thing! Hopefully the one Iâm changing to is better! And right now I canât access my website to make a Google Drive Backup on WordPress so I can move my website!
Yes, this issue is still going on. And this issue will go on for quite a while. For how long? I suspect weeks at least, but it could even be a couple of months, depending on how well things go.
Does this mean you website is down until then. Absolutely not! Or at least, itâs doesnât need to be, if you donât want it to be.
So I would like to repeat what I wrote in my original announcement very clearly.
IF YOU DONâT WANT YOUR WEBSITE TO BE DOWN UNTIL THEN, IMPLEMENT ONE OF THE SUGGESTED WORKAROUNDS!
I understand you all are angry that nothing has happened and your website is still down. But let me be very clear: your website doesnât have to be done for a minute longer than you want it to be. All you have to do is implement one of the workarounds above and your website will be working perfectly again very soon.
So if this downtime is driving you insane, I cannot stress more that you should try to implement a workaround for this issue. There is so much you can do than just repeat that there is an error.
If you need help implementing one of the workarounds, please donât hesitate to create a new topic and ask for it! If you do, we can actually help you get your website back online quickly. We canât help you if you just complain here that the SSL is not fixing itself magically. We can only help you if you let us.
Appreciate your reply; But to be clear, nothing I wrote is, nor is it intended to be, a complaint. And never did I yell. The last time-table for any resolution was stated as 48 hours, and then, it âmay not fix all websites.â
All problems have resolutions and work-arounds and I am not opposed to using either or both.
For now, free subdomains will be fixed first. I donât know when that will be. It could take days or it could take weeks.
Custom domains will likely take longer to be fixed. This is more likely to take weeks or months. So if you use Cloudflare, you should use Flexible SSL in the mean time. And if you donât use Cloudflare (and just connect with the self signed certificate), you could disable HTTPS on your website entirely for now.
You can disabled HTTPS in the same way that you enabled it: through .htaccess rules, Cloudflare configuration or website settings.
What exactly you need to do on your website depends entirely on how you configured your website. Our hosting platform by default does not enforce HTTPS.
As you can see, on the page, you get an âHTTP 500 errorâ. Thatâs not an SSL issue, or it would have said something about SSL or secure connections. Please donât hijack this topic to ask this question, but check the knowledge base instead. And if you canât find the issue, please post a new topic about this.
Youâre looking at the file manager. This topic is about SSL issues on websites, not about file manager issues.
As a reminder to everyone: This topic is about SSL issues on websites. If you experience any kind of issues which is not related to SSL, it should not be reported in this topic. Any posts created in this topic from now on which are not about the SSL issues described in the first post will be deleted.
We do our best to help everyone and keep everyone informed about issues. And we canât do effectively that if all questions about all subjects get dumped into a single topic.
