wolstech

All Johnny accounts were manually archived regardless of activity because the server had to be rebuilt. Please renew your account if you wish to continue using the service. Please see the news section for more information.

Krydos can do this for you

It's actually not related to inactivity at all (though restoring the archives created as part of the recovery process do show the inactivity messaging as the system doesn't differentiate the reason for them being archived), it's related to the recent disk crash on Johnny. Your account was one of the ones that rolled back to March 8 during recovery, which means any changes made after that date were lost. In your case, the other account had been merged in late June, the result being that the merged account's data was lost (along with any other changes you made after March 8.) You'll need to re-create these databases from any local backups you may have. For more details on the Johnny incident, please see the news section.

Please clear your cache. I see a website for Seiho engineering on your domain, so it's definitely working.

It only gives you a few attempts in a 60 minute window. If you exceed that it blocks you. The issue with FTP passwords should be fixed, but you’ll need to reset your password again through our website or change the FTP password manually in Plesk to sync them up.

Try again now. You were blocked for too many failed sftp logins.

Weird. The connection issue and round cube error is something Krydos will need to look at. Also, there are bounced emails showing in plesk for you because of spf and dkim needing to be set back up...I'd set these up for you but can't due to being on mobile, so Krydos will need to do that as well.

It takes up to two hours for the domains to work. Give it some time, and please let me know in a little while if it still doesn't work.

Krydos can do this for you.

For the MX you can put johnny.heliohost.org as the mail server hostname. For A and AAAA and records, please use the IPs shown in Plesk (refrain from posting them as it makes it easier for bots and attackers to scrape them from the forum), or you can perform a lookup on johnny.heliohost.org to get them.

Please make sure the MX record for the orcagroup.top domain is pointed to us for email (MX set to johnny.heliohost.org), otherwise the domain and all subs will get disabled during domain cleanup. I'll configure this shortly for you.

This does not appear to be supported on Plesk (though it technically is possible in mariadb). It's generally considered to be poor practice anyway, insomuch that mysql/mariadb is one of the only major engines that even supports it. Postgres and SQL Server expressly refuse to support this (in Postgres you can do it between schemas but not databases, and sql server simply has no support at all, you need to use triggers). Allowing this actually causes all sorts of issues with database integrity too, for example, what happens if one of the two databases goes missing or is rolled back to a backup?

If you aren't hosting it here, it would be best if we not add it as it will result in the subdomains being incorrectly disabled. If you want it added for email only, then Krydos has to make an exception in the system so it doesn't disable the domain for not being hosted here. Do you want us to have it set up for email or would you rather just have subdomains added?

Unsuspended. It may take a few minutes to work again.

We had this happen with another users archive. If you view the damaged tzst file in a hex editor , you’ll likely see an error message right at the top. Remove that so the magic bytes (28 B5 2F FD if Wikipedia is right) are the first bytes in the file, save, and open in 7zip.

Krydos can set this back up for you.

Krydos can reinstall these for you.

Krydos will need to check this for you. Can you please post the transaction ID of the donation in the meantime?

Python versions have changed on the new Johnny. If it was using 3.10 you probably need to update your shebang lines to use 3.12 or 3.9 #!/usr/bin/python3.12 or #!/usr/bin/python3.9

The software on your account is simply too heavy for Tommy. As soon as you start to see a lot of traffic (which could be both users or bots), your load spikes and you're getting suspended. The good news is Morty will be out soon and that server doesn't have load limits. You may want to consider that plan as soon as it's released, as it will solve this issue for you. Morty will be a paid offering with a monthly fee that varies based on your load. Instead of getting suspended, you'll just owe us more money when your site uses a lot of resources. For the time being, I've unsuspended you again. Please check for and block bots with tools like htaccess, as this will help control your load for the time being.

Oh, and to finally answer the original question about Johnny being down, it's back up. In the past, this would've taken months to recover, but we've managed to restore the server in about 2 weeks this time around, and that was because we had to finish Morty first. Rebuilding Johnny took like three days since we now have a new method of doing it.

The internals of our system is written mostly in shell scripts. I don't even really work with that part, that's Krydos. There's also some Python and php internally. The UI is just regular PHP.

I've removed Laravel from app.ppblk.space for you. If you need any of the data from that domain, a backup of the account from before the deletion can be downloaded at https://heliohost.org/backup/ I didn't need to remove the learn.ppblk.space content as the disk space went below 1000MB from removing the app.ppblk.space files. If you want to uninstall Wordpress on this yourself, you're welcome to do so. I did reissue the SSL certificate since that wasn't working. Since I had to change the document root on the app subdomain back to its default after removing laravel, it may take up to 2 hours for everything to work normally.

Both root admins are in the USA, so when you were asking for this, we were asleep. Support requests can take 24 hours or longer in many cases. As for actually removing this, I'm working on it. It's a bit more involved than just deleting the files since you look to have used laravel toolkit and git. Laravel toolkit messes with the document root for the domain (so I have to change that back), and git will break your domain if the repo folder goes missing due to manual deletion.

So you would like us to delete all content inside of the app and learn subdomains, but leave the empty domains so you can reuse them? Correct?