wolstech

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.

If it's connecting using the same database name and database user that was previously approved for remote access, the software used on your side to make the connection doesn't matter. It should just work. Is it not working for some reason?

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?

I unsuspended you and deleted a single 28mb backup in the Softaculous backups folder to get you below the 1000mb limit. Please finish cleaning it up as soon as possible. if for some reason you need this backup, it can be retrieved from the archive available at https://heliohost.org/backup/

It looks like you haven't waited two hours since you restored the account. Domains take up to two hours to start working. Let's give this another hour or so and if it's still not working, we'll take a look at it.

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.

Support for these protocols has been turned back on. Please try again now.

Check the A records for your domain in your Cloudflare account. The IP address of the server has changed and you probably need to update them. The new IP address can be found in Plesk.

Your account is definitely on Johnny. If you cannot log in using https://heliohost.org/login/ , try resetting your password.

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

In the meantime, can you explain exactly why you need these?

I've asked about this in a staff channel for you. It's worth noting that Tommy still supports these protocols for the time being (and will likely continue to do so until rebuilt). The security risks associated with these protocols seem to be grossly overstated in many places, and while they are possible to break, it's still not trivial, and for the stuff being hosted on our servers, it's not likely to be an issue. Even Google still supports these legacy protocols, and they're usually one of the first to implement any form of new security...

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.

That account was lost in a recent disk failure. Please see this News link for more information. https://helionet.org/index/topic/61727-johnny-has-been-rebuilt/

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.

That account is working for me, though its SSL certificate does need to be reissued to fix a security warning. I've gone ahead and done that for you, the warning should clear up within the next 2 hours. If the site is still not working for you within the next 2 hours, can you try accessing it from a different internet connection (e.g. a cell phone on its data plan instead of home internet) and tell us if it works?

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?