wolstech

It looks like you were a Tommy account that was lost during the cPanel->Plesk migration. The only information I have is that you were on Tommy back in 2018. An invite for a replacement account has been sent to you. Welcome back

See here: https://helionet.org/index/topic/64954-wrongful-suspension/ Please do not create multiple posts for the same issue.

Please remove all pirated content and all content that offers investments and financial services within 24 hours or you'll be suspended again. If you get resuspended, an admin will have to delete it for you before you can get a second unsuspension. Also, in the future, please don't use capslock for everything. It comes off as screaming and can result in delays receiving support from us. Unsuspended. It may take a few minutes start working again.

Why did you create another account after just being told you're not allowed to have more than 1 account (ignoring Morty accounts)? You cannot create any additional accounts unless they're on Morty. You're going to be suspended again in 24 hours unless you confirm you still want to keep emmanuelfosso206 and ban the newly created account.

This is intentionally blocked for security reasons. Minecraft servers won't run on the free hosting anyway due to the amount of resources they need. You'd be suspended for high load within hours, and custom inbound ports are not allowed either, so nobody would be able to connect. You'll need to buy a VPS to do this. https://heliohost.org/vps/ We actually just recently released 2 videos on how to host Minecraft here: https://helionet.org/index/topic/64691-minecraft-on-heliohost/ https://helionet.org/index/topic/64843-modded-minecraft-on-heliohost/

For now, just send us money through one of our donation links (https://heliohost.org/donate/ ) and let us know the transaction ID so we can credit you. We don't have an automated way to do it yet because we didn't expect users to go through their funds as fast as some have. It's on our list of things to implement...

Unsuspended. Your error just means your application ran out of memory. It's either broken or too heavy to run on Tommy. The memory limit is already set to the 128MB we usually allow on Tommy. We don't really troubleshoot code for users, so my suggestions for this would be that we can either try it on your Morty account (where we can raise the memory limit if needed), or you can find different software.

We aren't able to assist with this until you address your terms of service violation for having more than one account. I assume the account mentioned in this error is the one you want to keep?

You can cancel/delete your account here: https://heliohost.org/dashboard/delete/

No need to change it then. If you ask for additional domains for extra projects, they automatically get their own document root. Your main domain is always ~/httpdocs/ , but extra domains would use a folder named after the domain instead of httpdocs (e.g. ~/extradomain.helioho.st/ ), so they're automatically separate. Changing the docroot was a common request back in the cPanel days because cPanel used to put the addon domain roots inside the main domain's root, but Plesk doesn't do that.

This is the software in question: https://codecanyon.net/item/max-profit-online-investment-platform/26164846 Worth noting that even if he had paid for it, he can't run it here because we no longer allow investments or other financial offerings as of our June 25, 2025 TOS update. (Our data center does not meet industry data security standards for handling or storing this sort of information).

Tons of other processes are still causing load even when Apache is stopped, such as: Plesk (which runs tons of stuff in the background), MySQL, PostgreSQL, mail server, system tasks, NodeJS apps and long-running Python apps on people's accounts, cron jobs, etc. Apache itself is only a fraction of the load, and while yes, load will drop when Apache stops because there's no requests (which means things like PHP and CGI stuff will not execute), it doesn't make much difference. The real determining factor is the number of vhosts in the config. Apache takes its sweet old time loading all those. It's worth noting that Johnny is really overcrowded for a Plesk server. Typical Plesk servers are meant to handle ~400 accounts per server. We have 991 on Johnny right now, and it was over 1000 a few days ago (several accounts archived and caused it to drop). We've actually been told by the software companies (both Plesk and cPanel before it) that they were amazed at what we've done with their products. Morty is much faster than Johnny for these restarts. There's substantially fewer users, fewer vhosts, and its running on hardware that's both newer and faster than what Johnny is on. It's been a while since I checked the numbers, but I remember Johnny's Apache restarts were like 5-10 minutes while Morty took just 9 seconds... TL;DR: Server has a lot more running than Apache, and is overcrowded.

Domain added. It can take up to 2 hours to work.

Just the monitor not catching it. The monitor checks on an interval, and if happens to occur between checks, it simply never shows on the monitor. Server load also affects the speed at which it restarts, so during times of low load, the restart completes faster, resulting in shorter error duration and an increased likelihood of it being missed by the monitor. And finally, the 2 hours thing isn't a hard 2 hours. It's at least 2 hours between restarts. There's times where that restart is closer to 3 hours because the server delays maintenance tasks if it's experiencing high load. The background process we developed to handle routine server maintenance (including apache restarts) is designed to only do its work when server load is below a set threshold.

It's not crashing. We're forcing it to restart intentionally. The errors occur because nginx is used in front of Apache as a proxy, and it spits out that error when it can't reach apache.