Krydos

We don't use cPanel anymore, but does WP Toolkit on Plesk work for you now?

Thanks for reporting it. Does it work for you now?

You're going to need to restore that directory from your most recent backup.

It looks like that config.php file is missing. You'll need to restore it from your most recent backup. To stop the emails in the meantime you can stop your cron job.

I tested PHP on your account and it seems to be working fine. https://goensch.helioho.st/krydos.php <?php echo "Krydos was here."; The only other PHP file I see is working too, but it's trying to access non-existent files so they are giving 404 errors.

Does it work now?

I just checked your site and it seems to be working now. Let us know if you're seeing garbled text still.

The invite has been resent.

Yes, transfers from Tommy cPanel to Plesk are still happening. Your invite to move has been resent.

Added. Since you're using Cloudflare make sure you create an A record with the value 65.19.141.67 and an AAAA record with the value 2001:470:1:1ee::2009

I also wanted to mention that due to the downtime we will be giving everyone 1 week of inactivity immunity since you couldn't log in for the last few days. Inactivity monitoring will resume on 2023-02-16.

Tommy is now back online and running! Since Tommy was powered off uncleanly there was quite a bit of corruption for anything that was being written to the disk at the time of the power loss. Most of it has been cleaned up, but there may be some issues here and there that still need to be fixed. The hard drive had it's partition table corrupted so we had to rebuild all of those. The XFS partitions had unwritten log data so we had to mount each one to write the log data to disk, then unmount them again, and run xfs_repair on each partition. Since the master boot record was corrupted we had to reinstall grub2 on the disk. The initramfs was corrupted too so we had to rebuild that as well. Then the main Plesk database uses InnoDB engine which always breaks whenever there is any sort of unclean shutdown, so we had to fix each table one by one until Plesk would run. The Apache config files and Nginx config files had a couple vhosts that were corrupted so that had to be fixed before they would boot up. Anyways, everyone's websites should be online now and you should be able to login. Please report any errors that you see so we can fix them. If you have an InnoDB database you might need to back it up, drop it, and import it back in. There isn't really any way to repair it otherwise. We still and always have recommended MyISAM tables for this reason.

A password reset link has been emailed to you.

A password reset link has been emailed to you.

65.19.141.67

Remote access enabled.

Did you read this news post? Or did you read this news post that you replied to? Since you're on Tommy, and the Tommy server is down, it makes sense that you would get no response from the server, and your website can't be reached. When Tommy is back up we'll make a news post to let you know.

Added. It should start working in about 40 minutes.

Deleted.

Please welcome our newest staff member, Kairion! He's been helping out quite a bit on Discord and on the forums over the last few years, so we decided to offer him a promotion so he can help out even more. If you're interested in volunteering for HelioHost too just do the same thing that Kairion has done and we'll notice and maybe offer you a promotion too. The worst way to get promoted is to ask for a promotion. The best way to get promoted is to just help without asking for anything in return.

The way I see it the internet is basically like the wild west of the US from back in the day. If you're not familiar with the wild west term, basically lawlessness was rampant, and bank robbers, train robbers, and highwaymen were extremely common. Everyone carried a gun to protect themselves because it was too big of an area to have enough sheriffs and deputies to protect everyone. Eventually we got it under control though and there are hardly any bank robberies or anything like that anymore. Eventually the internet will be better protected and criminals will become less common. Part of the problem is VMWare writing extremely buggy software with thousands of vulnerabilities.

Yeah, I only got 5 hours of sleep, and started working on it again this morning.

The HelioHost staff have been working tirelessly for the last 12 hours, and we're happy to announce that we've already completed the repairs on heliohost.org, and we have both nameservers running again. The next step is getting Tommy back online. We're going to let the backup run through the rest of the night and we should be able to get Tommy powered on sometime tomorrow as long as everything goes well.

Generally mail servers retry for 4 or 5 days before giving up entirely, but there isn't a rule that says you have to try for a certain number of days, so each sending mail system may have a different limit. Yes, if the email can't be delivered at all the sender should receive a bounce back message saying their message wasn't delivered, but again it might depend on which mail service they're using to send the mail. So if Tommy comes back online tomorrow or the day after you will probably not lose any mail, but it won't all show up as soon as the server comes online because the longer the server is down the less frequent the sending mail server will try. For instance, one failure means they will retry in 30 minutes or so, but after 24 hours of failures they may only try once every 4 hours. Once again all of these numbers are determined by the settings on the sending mail server, and there are no rules saying they have to do it a certain way. Another thing you could consider is setting up a free Zoho account, or another free mail hosting service, and changing your MX records on your domain. When the sending mail server retries they will see the new MX record and send it to Zoho or whoever you use instead.