THIS ISSUE HAS BEEN RESOLVED ALREADY. IF YOU GET SIMILAR ISSUES, YOU’RE NOT AFFECTED BY THIS ISSUE.
Many websites at this time are inaccessible and only show timeout issues. We’re aware of the issue and working to get this resolved as quickly as possible.
Right now, the issue seems to be largely concentrated on hosting volumes vol6_2 and vol6_4, but there may be other volumes with issues as well.
How do I know which hosting volume my website is on?
You can see your hosting volume in the control panel. After logging in to the control panel, check the “Hosting Volume” field in the sidebar.
When will this issue be resolved?
We’re doing our best to get this issue resolved as soon as possible. That is the most specific I can be at this time. If there is any news, I will update this post.
What can I do?
Unfortunately, there is not much you can do from your end right now. If there is a good workaround, I will update this topic.
I just removed my domain from my account, created a new account (hosting volume vol11_1) and registered my domain in this new account, and still can’t see the website.
so the way to do it is to register a brand new account with vpn in usa wich is 14_2
and you can optionally use cloudflare to cache in cdn
i know that this is not proper but what else can we do
also i will really appreciate the option to comperes and decompress files in the online file manager because uploading 5000 files via ftp 3 times was around 1 day of waiting
@John_38 said:
I just removed my domain from my account, created a new account (hosting volume vol11_1) and registered my domain in this new account, and still can’t see the website.
Recreating a domain on a different volume assigns a different IP address on the domain as well. So you need to wait a day or two for DNS propagation.
@raga70 said:
so the way to do it is to register a brand new account with vpn in usa wich is 14_2
For your information, account distribution is pretty random. It should be mostly based on which server has the most room (although that clearly didn’t work very well in this case). You don’t need to spoof your IP address location to get an account on a different server, your location does not affect where your account is created.
@Joo_Nath said:
14_7 seems affected too, didn’t had this problem earlier, so it must be happened not too long ago.
Quick update: I added a section with symptoms to the original post, to help make sure this discussion is only used for this particular issue, and not other unrelated issues.
Oh nevermind, it goes back online now @Admin
It’s https://joo-nath.cf (ssl seems goes invalid because its info was changed to all wildcard, which isn’t supposed to happen. Maybe it’s one of Lets Encrypt problem)