wolstech

Your account was moved to Morty because we determined during a routine compliance audit that your account is being used to host a commercial website, which is not permitted on Tommy or Johnny due to our discounted Plesk licensing on those servers. From our terms of service: You should have received an email similar to the below, however because you were one of the first accounts moved, it's possible it moved before the email notification was in place. You'll need to prove the websites on your account do not belong to commercial businesses, start paying for Morty, or remove the commercial websites before the trial expires.

Your account has been reset. You'll receive an email shortly with a link to start over with a new account. If you need anything from your old account, the data can be downloaded from https://heliohost.org/backup/ once the reset is complete.

Fixed missing DNS zone.

Domain changed. The IP addresses needed for the A and AAAA record can be seen in Plesk. For email: For mail server (MX record) should be tommy.heliohost.org For SPF, use the value "v=spf1 include:tommy.heliohost.org ~all" For DKIM, you'll need to enable it in Plesk, and once enabled, hover over the ? symbol to see the records. They are unique to your account so we cannot provide them here. The domain can take up to 2 hours to function.

How do you want this written? Is tkgagenthub.helioho.st OK? Also, keep in mind that we cannot directly rename an addon domain, but rather delete it and re-add it, which will cause the content of the domain to be deleted. Is this OK?

Krydos might be able to install that module for you. As for those other logs, odds are either your domain was still setting up, or your permissions were wrong at that time.

You need to configure DNS on the domain so it's actually hosted here before a certificate can be installed. You can do that by either using our name servers (ns1.heliohost.org and ns2.heliohost.org) or by using A and AAAA records pointed to the IPs shown in Plesk.

DNS issues corrected.

Domain added using default document root. It can take up to 2 hours to function. As for the document root being inside another, I agree with Krydos: Putting the document root of domain A inside of domain B has tons of weird issues and is not supported. Notably: Domain A would be accessible via domain B, configs applied to domain B may break domain A, and if domain B were to ever be renamed or deleted, domain A will lose all of its data and break.

The error logs do in fact show what's wrong with your program. This is what I found when I logged in as you and checked your error logs. The built in Python cgi module is no longer supported as of version 3.13. The old server had 3.12 so it could run it, but the new one is 3.14 and cannot.

We've been doing this for 20 years. It's not a security issue on the server itself, it's WordPress, though it's possible your wordpress installation is hacked or being pounded by bots, both of which will cause it to use even more load than it already does. The security of WordPress itself sucks, and WP gets hacked all the time. We usually see a couple of users per week get their Wordpress instances hacked. Even if it's not hacked, it's very inefficient, being one of the heaviest PHP based CMSes available. Also, our load measurements are a cumulative sum, not actual numbers, which is why they seem extreme. We sample your load every 60 seconds, and just add the samples together over the span of 24 hours. For example, the 200GB memory limit expressed as continuous usage would be only about 140 MB continuous usage, which is pretty easy to get suspended for (and many people do, usually because they left a node or python app running).

You managed to exceed your CPU limit for the day. Wordpress is infamous for this. Please see this article on why we do not recommend running Wordpress: https://wiki.helionet.org/WordPress It's one of the leading causes of load suspension. Please watch your load here: https://heliohost.org/dashboard/load/ unsuspended. It may take up two hours for your domain to function.

Glad to see its working for you now. Please let us know if you need anything else.

That error makes me think something is wrong with mariadb itself (looks like an incomplete upgrade). Krydos will need to take a look at this.

The account cirravosolutions has been unsuspended and the domain has been changed to cirravo.heliohost.us. The account can take up to 2 hours to function.