wolstech

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.

Now it's because of copyright issues. You cannot host copyrighted material on your account unless you can show you have a license, and streaming video/IPTV is explicitly prohibited by our terms of service regardless of the content anyway. You've already been given a link to the terms above via Google Translate. You need to read and understand them, because following those rules is a requirement of using our service. So far, basically everything you've done (from creating multiple accounts to what you've hosted on the account) violates those terms. Can you explain?

Users don't have the ability to change document roots on our systems by design, because it tends to cause weird issues (especially when users later delete the folder they set the document root to). I went ahead and changed it for you. The changes can take up to 2 hours to take effect. Keep in mind that if you later remove Node from your domain (or you get suspended, which removes Node automatically), your domain may not work properly until you contact support to have the document root changed back.

Alias added. Please be sure to configure DNS. The alias can take up to 2 hours to function.

Your domain has been converted to an alias. The alias can take up to 2 hours to function.

There is nothing to enable, and no user interface for python. You just use it. See this guide for an example of how to get started. https://wiki.helionet.org/Python_Tutorial or for Flask specifically: https://wiki.helionet.org/Flask As for SSH, this is intentionally not supported on the shared hosting plans for security reasons. If you need SSH access, you'll need to buy a VPS instead.

Is your goal to make https://globalyouthsciencejournal.app/ show the same content as globalyouthsciencejournal.helioho.st? Or is the content supposed to be different on the .app site? If they're supposed to be identical, an alias is probably an easier route than duplicating the site and figuring out why the .app copy is broken.