Starting May 15, iFastNet has been upgrading the free hosting cluster with additional capacity and necessary updates. Unfortunately, this has not gone very smoothly, and has resulted in the following issues:
- Home directories not being setup, resulting in:
- FTP error: 421 Home directory not available
- Softaculous: Something went wrong, please allow 20 minutes then retry
- File manager not logging in
- The control panel being down and the client area being unresponsive.
- Database/DNS issues:
php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution.
- Domains being setup with multiple IP addresses in our nameservers, redirecting them to suspendeddomain.org.
- SSL certificates not being applied to sites after uploading.
At this time, all issues except for the SSL certificate issue appear to have been fixed.
iFastNet is continuously working to resolve the final issues and restore the system to a reliable and fast state. We’re sorry for the inconvenience caused.
PLEASE DO NOT SUBMIT ADDITIONAL SUPPORT REQUESTS ABOUT THIS. We’re aware of the issues and are trying to keep everyone informed in this topic. Any additional topics about these issues will be removed.
Two new issues have popped up:
- The FTP server seems to be overloaded. When trying to connect, you’ll see an error like
421 6900 users (the maximum) are already logged in, sorry
- This means the file manager won’t work either.
- Account creation appears to have stalled. No new accounts have been activated since yesterday around 16:30 UTC.
I’m not sure about it, but I suspect the issues are related.
As before, iFastNet is still working hard to get everything up and running again.
The pending account issue appears to have been resolved. The FTP server also seems to be back up.
There may still be some issues regarding SSL certificates which we are investigating.
The SSL certificate issues seem to have been resolved too, all sites I checked seem to have active SSL.
There are no more current issues as far as I know!
The SSL issue still appears to be present, or has reappeared.
After installing an SSL certificate, the certificate isn’t applied on the web server. So even with a valid SSL certificate, you can’t open the website with HTTPS. The SSL status checker in the client area will also say that no certificate was found.
This issue is still being worked on.
I’m also seeing reports of sites getting corrupted somehow. This may also be caused by these issues.
The SSL issue has been fixed now. All sites that have uploaded an SSL certificate should see it active on their website now.
A sizeable number of sites do seem to be corrupted. If so, you’ll usually see code printed on the web page. If you have issues like that, the best way to fix this is to simply overwrite the files on your site with a clean copy. This is how you can do that for WordPress: How to fix a corrupted WordPress installation - InfinityFree Knowledge Base