-
Posts
19261 -
Joined
-
Last visited
-
Days Won
766
Everything posted by wolstech
-
Lets see what Krydos says about this, as I'm not sure if hosting what sounds like an internal system for a business will be an issue (I'd assume not as long as it is not public facing).
-
What error are you receiving? Is it just timing out? If you're not able to connect to the server at all, please post the IP address of the connection you're using (you can see that here: https://heliohost.org/ip.php)
-
Sure. Please remove the commercial website within 24 hours. Please let us know when the site has been transferred so we can remove the domain from your account. Unsuspended. The domains can take up to 2 hours to function.
-
[Solved] Request for Account Unsuspension
wolstech replied to kalairohith07's topic in Suspended and Queued Accounts
Unsuspended. Your domains may take up to two hours to function. -
You're suspended because we have reason to believe you were using Johnny to run a website that belongs to a commercial business. The Johnny and Tommy plans cannot be used to run commercial websites. Normally, we would offer a free trial of Morty for this, but you've already had a trial previously and chose not to purchase, so you were suspended instead. If you wish to keep your website hosted here, you'll need to either purchase a Morty subscription or prove that your website does not belong to a commercial business. How would you like to proceed?
-
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.
-
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.
-
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.
-
[Solved] An error occurred while using Johnny alongside MariaDB.
wolstech replied to swaloy's topic in Escalated Requests
Glad to see its working for you now. Please let us know if you need anything else. -
[Solved] An error occurred while using Johnny alongside MariaDB.
wolstech replied to swaloy's topic in Escalated Requests
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. -
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?
-
[Solved] Unable to Set Node.js Document Root
wolstech replied to amaljunior002's topic in Customer Service
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.
