wolstech

Krydos can do this for you.

Johnny databases were not recoverable which is why they were not included in the backups. If anything at all is available, it will be the raw server files (.ibd and .frm files) of individual tables in your database (.frm is the structure of a table and .ibd would be the data that goes in it), which are confusing and sometimes difficult to extract data from. If you know the names of the tables in the database, we can check if these are available for you.

The databases on Johnny were not recoverable because the server no longer booted and the mariadb partition on the server had trashed itself. If you know the name of the databases and the tables inside, it may be possible to locate the raw .ibd and .frm files for you, but actually recovering the data from those can be a challenge assuming we can even find them. I think we were able to find those for one or two other users so far of the ones who asked...

This user is actually on Tommy and has 7 domains, which is why I asked for the URL. That said, I just realized it's all of his domains, and it's because his IPs on Cloudflare are incorrect. His DNS is set to Morty's IP but the account is on Tommy because he didn't refill his Morty balance. He needs to correct the DNS in Cloudflare on his end to point to Tommy.

Please post the full, uncensored URL that's experiencing this problem so we can review the issue.

Remote database access doesn't follow you when the account moves servers. Escalating to have this turned on again. I assume same database info as the linked topic?

Fixed missing DNS zone. It should be available again shortly.

Your account is on Johnny, which crashed last week. Please see https://helionet.org/index/topic/67733-when-it-rains-it-pours/ for details.

That's the server performing an Apache restart. It happens approximately every 2 hours and lasts for a few minutes typically (the exact length of time depends on server load). The error is normal while the restart is in progress though.

An invite has been sent to create a Morty account. Please click the link and follow the instructions to create a new account. Data that was successfully recovered from your Johnny account can be downloaded from https://heliohost.org/backup/ Note that backups may not be available yet for all accounts, and not all data may have been recoverable (especially databases). If there is something specific you need that you don't have a backup of, let us know exact details of what you're looking for and we can take a second look to see if it can be recovered. If you need domains added, please let us know your new username and the domains you need once you finish creating the Morty account so we can get them set back up for you.

DNS issue is fixed, now just needs to provide a real email to get rid of the suspension page.

The server your account is on (Johnny) crashed last week. Please see https://helionet.org/index/topic/67733-when-it-rains-it-pours/ for details. A backup of your files can be had from https://heliohost.org/backup/ We are also offering free Morty trials for users affected by the Johnny crash. If you want, you can be sent a Morty invite at no cost to get your site back online, and we'll move you to Johnny once Johnny is working again. If you're interested, please let us know.

Yes the issue is DNS related, but as MoneyBroz said above, the terms of service violation has to be addressed first. From our terms of service: Please provide us with a valid, non-disposable email address and we can update your account, unsuspend it, and fix the DNS issue. If you are seen using a disposable email address a third time after we fix it again, your account may be subject to a ban.

Password protection does require an Apache restart to turn on or off. The error is because turning it off deletes the password file, but until Apache restarts it’s still looking for the file that Plesk deleted. Just waiting 2 hours after turning it off should clear the error. You may need to clear your cache after Apache restarts. Also, when you turn it on, it can take up to 2 hours before it requires a password.

High server load. 10022.40 CPU Looks like it was caused by a combination of backups being made and excessive scheduled task usage. Please fix the issue quickly, including disabling any scheduled backups or scheduled tasks so they stop using CPU. If this happens again, you’re going to have to move back to Morty. Also, we intentionally don’t send notifications when users are suspended for anything other than inactivity. It is normal for you to not receive any communications about your suspension prior to contacting support. Unsuspended. It can take up to two hours for your domains to function.