wolstech

Oh...legacy account. Yeah old cPanel accounts used to do that (put addon docroots inside the main domain docroot). We typically recommend just resetting the account if its old enough to be set up that way because of all the weird bugs these accounts usually have, but the fact you both would lose your legacy .org domain (the new account would be keibeeit.heliohost.us since the .org ones are now limited to staff), have third party email DNS set up manually by us, and have an (also really old) Lily account attached to it that would need to be manually fixed after resetting make resetting kind of impractical if the account otherwise works. The document root for domain keibee-it.com has been moved to ~/keibee-it.com for you and will take effect within the next 2 hours. It may show a 404 error or other strange behavior until then.

Are you waiting up to 2 hours for an apache restart? Node doesn't fully disable/enable immediately. It needs an apache restart to take effect.

You got suspended for using too much memory. The limit is 200GB per day. Please fix the issue quickly. Unsuspended. It may take a few minutes before you can login again, and domains can take up to two hours to function.

You're the first person to report that the logs are slow only when node is enabled... that's an interesting observation. Morty would likely make it faster since the entire server is quite a bit faster than Tommy, but I'm actually kind of curious as to why this only happens to you when node is enabled. Maybe Krydos has some input on this?

It was suspended for high load caused by systemd, which is likely due to excessive use of cron. The scheduled jobs have been turned off on your account and you've been unsuspended, please fix the issue quickly. It may take a few minutes before you can sign in again, and domains can take up to 2 hours to function.

That domain is working properly for me. Please clear your cache. Note that this error is usually caused by running out of disk space, and you are very close to your limit (975 of 1000MB). I suspect you were over your limit earlier and have since dropped below due to something like log rotation freeing up space.

error_log for domain twoofswords.net has been discarded. The best fix for this is to enable log rotation and set a max size that's reasonable (like 10MB) with a low maximum number of logs (like 3). That way the server will rotate them out and then eventually delete them for you. I've gone ahead and set up the rotation for you on that domain so this won't happen again.

Escalating to have this enabled for you.

Account senex has been unsuspended. It may take a few minutes before you can login again, and the domains can take up to two hours to function.

Can you explain why all of the accounts have very similar usernames? (Also, on the off chance these are a result of you just needing multiple websites, you can have multiple sites on 1 account...a Johnny account can have up to 5 websites/domains on it).

Old domain has been removed. Please let us know if you need anything else.

We can't actually "rename" a domain in our system, but instead have to add the new one then remove the old one. Because of that, it's best to add the new one first, then move your site over, then remove the old domain. I've gone ahead and added app.coreconnectyoga.com domain to your account for you. It may take 2 hours before the new domain starts working. Once the domain is working, you should move your app over to the new domain and confirm it works on the new domain. Once everything is set up and working on app.coreconnectyoga.com domain, let us know and we can remove the old panchkosha.coreconnectyoga.com for you.

You can use htaccess to block IP ranges based on the logs. Setting up a robots.txt can also help but bad bots will ignore it. Note that we do not charge for bandwidth, and you did not have any overages for CPU or RAM, so your account is good as it is. The $1/month charge you were billed for is the minimum charge to have a Morty account open.

You should use the same username and password that you used for the Tommy account (klimentwork0) to log into your Morty account. If the password does not work, please try resetting it: https://heliohost.org/reset/ You may actually be able to log in now, though the domains may not work correctly just yet. It will probably take another few hours before both domains work correctly.

The specified accounts are now moving to Morty and will be merged when the moves are complete. The resulting account will be klimentwork0 on Morty containing both the Johnny and Tommy account. The $2 cost of the Tommy account will be credited as $2 on your Morty balance. Note that because this is below the normal $5 minimum purchase, no bonus credit/discount applies. It may take several hours for the move and merge to complete.

Domains that are already added as an add-on domain cannot be switched to the main domain without resetting your account. https://wiki.helionet.org/Changing_Your_Main_Domain#Account_Reset_is_Required_to_Swap_Main_and_Addon_Domain

The pending suspensions for luisgalvan and backupchiquipoli have been canceled.

So to confirm, you want klimentwork0 moved to Morty? Do you want ortfusion combined into the Morty account (so both websites are on a single Morty account), or do you want that kept on Tommy (you're allowed a single Johnny or Tommy account, but as many Morty accounts as you want)? What about the third account in this set (on Johnny)? Do you want to have that combined into the Morty account, or would you prefer it be banned instead (you can't have a Johnny account if you have a Tommy account already)?

There are actually 3 accounts associated with you this time (two of which are the luisgalvan and backupchiquipoli accounts you've been allowed to keep already). Did you or someone you know create a third account without contacting support for permission? Also, did you at any point use a VPN to access your accounts?

Yeah you had a ton of load coming from Python (note these numbers have dropped off a bit because you've been suspended for a little while). 66.38 GB 120.2 /usr/bin/python3.12 -u -O /home/dragoe.helioho.st/httpdocs/AppFiles/Moonlark/moonlark.py -n DragoE 56.11 GB 28.1 /usr/bin/python3.12 -u /home/dragoe.helioho.st/httpdocs/AppFiles/Watchman-main/Watchman.py There was also resources being used by the system due to the long-running python processes (about 14GB as of this post), which you can't really do anything about...it's just the nature of linux managing sessions. Please reduce the memory consumption quickly. Unsuspended. It may take a few minutes to work again. Domains can take up to 2 hours to function.

If you have the certificate file (and matching key file), you can likely install that instead of Lets Encrypt. Not sure how you do that on Hestia, but I'd imagine there's an option or guide for it. It should work provided the certificate is not expired and the common name and subject alternative names (SANs) are correct (the domain/subdomain you're securing needs to appear in one of those fields on the certificate unless its a wildcard certificate). A domain's certificate is sent to the browser by whatever server is serving that domain, so you'll need to install the PositiveSSL cert on your VPS if you want to use it once your (sub)domain is pointed to your VPS.

VPS150 has been turned back on and should be available again. Thank you for your payment. (Note that this process is manual...if a VPS gets powered off, we have to manually turn it back on once the payment is made).

Information sent by PM.

That account looks like it has already been moved to Morty and unsuspended.

The load mostly came from systemd, which is usually due to excessive use of scheduled tasks or FTP connections being left open. We've seen this before, and weirdly systemd-related load suspensions are always the most prevalent after a server is rebooted (Johnny was rebooted yesterday due to hardware maintenance). It usually calms down after a few weeks, and we have no idea why. Please reduce the frequency of your tasks, and if using FTP make sure you're closing your FTP connections when you're finished using them. You can watch your load here : https://heliohost.org/dashboard/load/ Unsuspended. It may take a few minutes to work again, and domains can take up to 2 hours to function.