Leaderboard

Oh! After checking, you're totally right! It seems that the default configuration makes the app use 10 connections. After overriding the default configuration to a lower number, everything started working. Thanks for your help, guys!

Over the past week or so both Johnny and Tommy have been experiencing occasional slow loading and 503 errors on PHP pages from time to time. This is definitely not normal because we've been using Plesk since 2021 and none of us can even remember the last time we saw a 503 error, and then suddenly they are happening quite frequently on these two servers. We are investigating the issue, and are hoping to resolve it soon. In the meantime, here are some ideas you can do to improve the uptime of your PHP based website. 1. Morty hasn't been affected at all by the 503 errors on PHP pages at all so far, so this is a great time to upgrade to our fastest flagship server starting at only $1 per month. You can check out the discounted Morty packages at https://heliohost.org/dashboard/move/ and move yourself over without talking to an admin by using our fully automated upgrade process with zero downtime for your website if you're interested in trying it out. 2. VPS also have not been affected by the 503 errors either. They start at $4 per month, and aren't affected by other users on the same server as you, because on a VPS you're the only user. Being able to have root SSH access is also a great perk of being a VPS customer. You can check out the plans at https://heliohost.org/vps/ 3. If you don't want to upgrade it is possible for some PHP websites to be converted to static websites. Since it is only PHP being affected by these 503 errors converting your site to use only static html, Javascript, and CSS will allow your website to load faster, have less errors, cause less server load, and greatly reduce the chance of your site getting hacked. It's not possible for all websites to be converted though so this isn't an option for everyone. 4. You could also switch to a language other than PHP. For instance, Python websites using CGI, Django, or Flask haven't been affected by the 503 errors at all. Node.js hasn't been affected by the 503 errors either, but if you decide to try Node.js we recommend keeping a close eye on your load graph at https://heliohost.org/dashboard/load/ because it's easy to go over your 200 GB memory limit. In order to diagnose these 503 errors, the first step we're going to take is implementing additional logging and performance monitoring so we can see exactly when and why the errors are occurring. Let us know if you have any questions, or have any additional information to assist in our investigation.

Your account was suspended for High Server Usage due to using 200.61 GB memory when the daily limit is 200 GB. I have unsuspended the account now, please give it a few moments to get back up and running. Please fix the issue quickly since if there are no code changes made, it's very likely the system will suspend your account again. We strongly recommend that you keep an eye your account load using the Dashboard.

Your account was suspended for High Server Usage due to using 201.06 GB memory when the daily limit is 200 GB. I have unsuspended the account now, please give it a few moments to get back up and running. Please fix the issue quickly since if there are no code changes made, it's very likely the system will suspend your account again. If you're not sure how to reduce your account load, let us know more about what apps / programming language you're using and we can offer tips to try to keep the load down. For example, WordPress and Node are among the top reasons for accounts to be suspended. We strongly recommend that you keep an eye your account load using the Dashboard.

It might be the app itself too. If the app opens all 10 connections and then DBeaver tries to open 1 more you would get that error too. By default most software assumes you have a 8 GB VPS and can have 100 database connections open at once.

If these are student accounts, do you have a school email address we can attach to your accounts so we can exempt them? We need one student email address per student account, so please find out which account belongs to which person and provide a list of whose email goes to whose account. Also, tecandsoft already has a replacement account on Tommy (tecandsoftsrv), so it cannot be unsuspended without suspending the new account. The policy is one account per human being, not one account per server.

You're on the Tommy server, and that has a limit of 10 database connections at a time. When you say you're not able to connect from the DB manager, could you give a little more info please about what is happening when you try? Do you get an error message or does it just hang? As well, please let us know what type of database (MariaDB/MySQL or PostgreSQL) you're using. You might also get more details on the issue from your error logs inside Plesk. Here's a page explaining how to check the logs: https://wiki.helionet.org/View_Error_Logs If you see any db-related errors, please post them here. It'll help us try to help you resolve the issue. ?

Users have a concurrent connection limit of 10 for mariadb, so this would be a reduction.

Just to follow up on this part: In mid-April, the multi-account detection system began emailing users who were suspected of having multiple accounts, so that users who did not read the rules had a chance to do so, and resolve the issue to avoid suspension. Since you created your 2nd account back in March, your accounts were suspended before the automated email functionality went live. Please do let us know if you think of a way to make the first line of the Terms of Service stand out more so people will read it. On one hand, we have 60% of suspensions over the past year happening because users create more than 1 account, and then on the other hand we have users getting angry with staff because they have to try for a few days to create an account -- partly because of all the users who try to create more than 1 account.

Our signup page mentions "You may only have one account on Johnny or Tommy without prior written permission from an admin." And the Terms of Service, which users must read and agree to before creating an account, also mentions "Each person is allowed to have one account on Tommy or Johnny unless permitted in writing by an administrator of HelioHost." Since you created 2 accounts, you would have seen both these warnings twice, for a total of 4 times. If there is a way you think we can make the rule easier to read or more obvious so people actually read it, please let us know. You also mentioned you "have not received any specific information regarding the reason" for the suspension, which we will investigate further and advise on, since emails are generally sent to users who are suspected to be in violation of the Duplicate Account rule. In the meantime, I have unsuspended the account. It will take a few moments to reinstate so please make sure you read the Terms of Service as well as the Suspension Policy.

Please do not make multiple threads for the same question. Your account has not been incorrectly suspended, it was suspended for breaking the rules about High Server Usage Since you have created another thread here for the issue, updates will be provided there: https://helionet.org/index/topic/64331-suspended-lzban8/ HelioHost is run by volunteers who contribute their free time and creating duplicate requests for the same issue can result in unnecessary duplication of volunteer effort and delay responses to you, as well as to others who need help. Please review our 'Where do I ask for Help?' page, which explains: Wherever you prefer to ask for help, please ask your question in one place only. HelioHost is run by volunteers who contribute their free time, and some are more active on certain platforms than others. Posting the same question across multiple platforms (like Discord, the HelioNet Forum, or email) or creating duplicate requests on the same platform for the same issue can result in delays.

We looked into this further and found that the command `npm run start` was run: | sum(mem) | sum(cpu) | process | +----------+----------+-------------------------------------------------+ | 24064 | 0.00 | /usr/bin/hostnamectl --transient | | 1602836 | 2.30 | Passenger NodeApp: /home/gantelya111.helioho.st | | 36087868 | 0.90 | npm run start:bootstrap | | 45013376 | 1.60 | node --max-old-space-size=460 bootstrap-node.js | | 56514848 | 2.70 | npm run start | | 70923448 | 4.30 | node bootstrap-node.js | The `npm run start` command is not part of the Node guidance page I'd sent you after the 1st unsuspension, so it may be that you did not read the guide. The Node.js Wiki page offers steps to ensure that your Node apps run on Passenger, which is a service on Plesk that helps to reduce Node's memory usage. Running commands that never exit (like `npm run start`) use a LOT more memory. If you need to continue using this command, and so much memory, we'd recommend you upgrade your account to the Morty server. Please make sure to review the Moving Your Account page for more details on the process, and make sure to backup your account before any account move. Once you're ready to move your account, you can begin the automated process from the Dashboard page for account moves. In the meantime, your account has been unsuspended. If you decide to keep your account on the Tommy server, we would strongly recommend checking the Node guidance page linked above, and making sure your app uses Passenger. Please fix the issue quickly since without any code changes, another suspension is likely. Please also be aware of the Three-Strike Policy section of our Suspension Policy.

Account voltars has been unsuspended. It may take a few minutes to work again. As I said in my last post, please ensure that you and orca never share a computer, network connection, or content, and neither of you should ever log into the other person's account for any reason. Future suspensions for multiple accounts may result in both accounts receiving a permanent ban. Also, apologies for the delays in getting this issue resolved. We're always happy to help, but we need clear answers in order to understand the nature of an account's usage and determine a resolution to these suspensions. Please let us know if you need any additional assistance with your account.

Ok. I'm going to just change the email on the account and unsuspend it instead. It may be a little while because I have to get someone to reset your multiple account detection first...otherwise it's just going to suspend you again. I'll let you know when it's unsuspended.

Thank you for the clear answer. Ok...so your issue is that your friend isn't allowed to do that per our terms of service. Accounts must be created and maintained ONLY by the actual owner unless permission is requested in advance, so the account is in violation simply because you asked him to violate the TOS on your behalf. If you would like your own account, you are welcome to it, but you will need to sign up under your own email address, and under no circumstances are you allowed to share a PC, network connection, or content with him. He is not allowed to maintain the account for you, and you cannot store any content for his website (or vice versa). If we detect this again, both accounts will be permanently banned from our service. Would you like me to delete the voltars account so you can sign up again under your own email address? If so, let me know what email address you would like to use and I'll reinvite you for your own account.

All HelioHost staff are unpaid volunteers. We have full-time jobs and lives outside this project, and we run the organization in our free time. If we are busy, things may not get done very quickly. Help is usually provided within 24 hours, but there is no guaranteed timeframe. Due to time zone differences (most staff are based in North America) and real-life commitments like work, school, and family, response times can vary. Unlike for-profit hosting companies with full-time employees working 40 hours a week, it is rare for any of our volunteers to work more than an hour or so per day. No one is required to log hours and volunteers come and go as they please. If we are not having fun volunteering, providing support, chatting with the community, or developing new features, we take a break and focus on other things. This is why we do not offer SLAs or ETAs for new features or repairs, and why things move a little slower than with a commercial host. You can read more about why we cannot offer ETAs here: https://wiki.helionet.org/ETA I notice that you have not yet answered the question: Can you explain why the email addresses on these accounts have the same person's name in them? Bumping a thread without answering a request for more information will not speed up replies to you.

Your account was suspended for High Server Usage due to using 200.28 GB memory when the daily limit is 200 GB. I have unsuspended the account now, please give it a few moments to get back up and running. Please fix the issue quickly since if there are no code changes made, it's very likely the system will suspend your account again. If you're not sure how to reduce your account load, let us know more about what apps / programming language you're using and we can offer tips to try to keep the load down. For example, WordPress and Node are among the top reasons for accounts to be suspended.

You've got to admit this does not scream "I'm a legitimate email provider" We see criminals, phishers, spammers, etc. sign up with email addresses that when checked have messages like this all the time. Unsuspended.

It looks like you were suspended for using 201.15 GB of memory. I'm not sure what content you're hosting that caused such a massive spike in memory over a ~17 hour period, but it's also possible that a bot or malicious actor is paging your website repeatedly. I've unsuspended your account, it'll resume working shortly.

Your suspension has nothing to do with inactivity. It's because you used a disposable email address, which violates our terms of service. Please provide a real email address (PM me if you wish to keep it private, or post it and we can edit it out afterwards) and we can update your account and unsuspend you

Sure. Account reflux has been unsuspended. It may take a few minutes to work again. The other account can just be abandoned. It will delete itself in time since it's suspended. If you'd like to request it be deleted, please post from its matching forum account and we can do that.

Account aloneguardspare has been deleted and you've been unsubscribed from emails. If you want the other account removed as well, please post here from the other account's matching forum account to confirm and we can do the same for that one too.

The account igorhelio has been unsuspended, it may take a few minutes to work again.

You're suspended for having more than one account. Users are only allowed to have one account. Which one would you like to keep? (It's worth noting that while your particular case did not receive any notice of the multiple account violation, we improved this process about 2 weeks after your suspension occurred. If it happened today, you would've gotten an email 24 hours before your suspension telling you that we suspect you're violating the TOS and asking you to explain).

It was archived, not suspended. I've renewed your account for you, it may take up to 2 hours to work again. In the future, you can renew it yourself using https://heliohost.org/renew/

You were suspended for creating multiple accounts, which is against our terms of service. Are there any circumstances that could explain why you were flagged for having multiple accounts?

I have a Rails app running now on Tommy. Is it possible to run a Laravel app on my account as well without the two interfering? Or can I deactivate Ruby without losing that app and then install Laravel?

Sure. Domain added. It should start working within the next 2 hours. You'll see a new folder on your account for the domain where you can place the files for Laravel.

I believe that's supposed be megabytes but is an older version of the chart that doesn't show usage beyond 100. The version of this chart that admins work with shows the memory usage in megabytes. This is your account as seen from my side. That spike peeked around 150MB. I asked about the charts differing in a staff channel for you. For a simple reference, if the app will run 24/7, keep your app's memory below ~70MB and you should be fine. 70MB continuous for 24 hours converts to 98.4GB, which is basically right at the 100GB cumulative daily cap.

I often mention the renewed ZeroSSL. Certainly there is currently no good way to use it with HelioHost. Currently ZeroSSL (and SSL For Free) has restrictions on free issuance on the web, so you should consider a paid 1 year plan. But APIs and ACME are not. You can automatically issue a certificate and renew it for free. If you want to use this with HelioHost, it's safe to leave it to cPanel AutoSSL.

Your account was suspended for causing high server load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server. If you still see the suspended page, please clear your cache. If you need help figuring out why your site is causing such high load let us know and we can try to help. If the high load is simply because your site is getting a lot of traffic you might consider trying paid hosting from our partner starting at only a cent for the first month. https://www.heliohost.org/partners/hostgator