Krydos

Yeah, it's pointless to mess with it right now because you're still on the old plan and any changes we make may be reverted when you change the the new plan. Keep an eye on the Account tab and when it says "HelioHost 2000 MB" instead of "HelioHost 2000 MB old" then we can take a look at it if it's not fixed already.

When we fixed the 503 error we uncovered some strange bugs in the most recent versions of Plesk which caused some permissions to disappear. We are still in the process of transferring people from the old broken plans to the new ones. You can tell if you've been moved by going to 1. Login at https://heliohost.org/login/ 2. Continue to Plesk 3. Account in left menu 4. Check Plan Name As you can see you're on an "old" plan currently. Also it looks like your mailbox size is unlimited, not 100 MB.

Remote access enabled. host=65.19.154.94 port=5432 user=moisesbaly_balyonline_db_user dbname=moisesbaly_balyonline_db password=<set in Plesk>

Remote access enabled. host=65.19.154.90 port=5432 user=marcogarthi_db dbname=marcogarthi_dbTest password=<set in Plesk>

No. That's why I suggested switching to a VPS. Another option is you can switch to Python CGI instead of Flask. The timeout on CGI can be increased if you need it.

You're not causing Nginx to restart. Nginx restarts hundreds of times per day on its own. Each time some domain gets SSL. Each time a new account is created. Each time an account goes inactive. Each time an account gets unarchived. There are tons of reasons for Nginx to restart, so if your code can't handle an Nginx restart, increasing the timeout isn't going to help and you need to get a VPS.

No problem. By the time September arrives our VPS billing system should support Stripe so we won't have to manually create payment links for the wrong amount. Haha.

Yep, that was a typo. It was supposed to be $37.80. Since it was my mistake I will go ahead and give you the 10% discount anyways, but $27.80 will only take you to September 23rd instead of the full 6 months. I went ahead and canceled the wrong amount subscription and we will email you on September 23rd to set up a new subscription for the correct amount. Sorry about that.

HelioHost has released a new YouTube video on how to install MariaDB and PHP on a VPS. Check it out and subscribe at https://youtu.be/IbUi2gcLbuA We are going to try to continue releasing new videos every 2 weeks, because some users find it much easier to follow a video guide rather than reading the text guides we have at https://wiki.helionet.org Please let us know if there is a specific topic that you think would be good for our next video. Also if you don't mind subscribing to our YouTube channel that would be a great way to get some free advertising. We are a small non-profit funded by donations so we don't have a huge budget to afford paid advertising, so the more word of mouth recommendations, the more social media likes, and the more subscribes we can get goes a long ways towards finding more users and continuing to grow. Even if you can't donate, this is a great way to help us for free. Thanks!

Of course. 2 GB memory, 2 CPUs, and 50 GB storage for 6 months with the 10% discount comes to $37.80 and you can pay with this link https://buy.stripe.com/28o9AS4tPeFc59KeUY We will upgrade the memory on your VPS once the payment is made.

Closing due to inactivity.

Here's a link to pay for Mercury VPS 1 GB memory, 2 CPUs, and 50 GB storage for 6 months with a 10% discount https://buy.stripe.com/5kAaEWf8t68GeKkdQQ

It looks like most of your memory usage is coming from your Node.js app | sum(mem) | sum(cpu) | process | +----------+----------+------------------------------------------------------------------------------+ | 0 | 0.10 | [Passenger NodeA] | | 0 | 0.20 | [php-cgi] <defunct> | | 146900 | 0.90 | /opt/plesk/php/8.3/bin/php-cgi -c /home/system/blood.hhfn.org.bd/etc/php.ini | | 1233748 | 7.70 | /opt/plesk/php/8.3/bin/php-cgi -c /home/system/panel.hhfn.org.bd/etc/php.ini | | 65339536 | 460.30 | Passenger NodeApp: /home/hhfn.helioho.st | Unless you password protect it anyone can access it, including bots. Here are the recent IPs who have visited your Node.js website. The left column is the number of page hits in the last day or so, and the right number is the IP. 21 162.158.175.54 21 167.71.81.114 21 172.68.26.254 21 172.68.27.96 21 172.70.94.122 21 172.70.94.68 21 172.71.167.128 21 172.71.167.160 21 198.41.227.68 21 198.41.227.94 22 162.158.175.46 22 165.22.34.189 22 172.69.65.41 22 172.69.67.111 22 198.41.227.122 22 206.189.19.19 23 162.158.174.47 24 162.158.174.46 25 162.158.175.31 27 172.68.26.67 113 141.101.96.28 131 154.94.51.39 690 154.94.51.136 You can see this information yourself by looking at your access logs, or AWstats. On Morty you can use as much memory and CPU as you want. If you go over the 200 GB limit you get charged $0.0005 per 1 GB memory, and if you go over the 10k CPU limit you get charged $0.005 per 1k CPU.

We emailed you the warning at 2025-05-06 01:57:23 and since you didn't respond to us or delete one of the two accounts they were both suspended at 2025-05-07 01:57:23. How would you like to be warned in the future if not by email?

The forum account has been deleted.

Not sure. I mainly provide support for server issues, not debug people's code for them. We have over 6000 accounts and if I helped each person debug their code I wouldn't have much time to do other more important things such as building new servers, adding new features, etc. You could try using AI to debug your code, or if you post your code on this forum or on Discord someone with more free time may be able to help you.

The forecast service or the rates service?

We have made some changes to the Tommy server to help reduce the number of 503 errors, and speed up the execution of PHP scripts. The feedback we've gotten so far seems to indicate that it is working. We have also noticed that the changes have sped up the time it takes for Apache to restart which should reduce downtime as well. Since the DDoS was targeting the webmail subdomain of random domains hosted on Tommy we just went through and disabled Roundcube on every account. We figure most people probably don't even use the webmail anyways so it is a waste of system resources to have it on by default. If you regularly use Roundcube webmail you can re-enable it yourself on your domain if you need to. Login > Continue to Plesk > Mail > Mail Settings > [Your Domain] > Webmail > Select Roundcube > Ok After enabling webmail again you will need to wait for up to 2 hours for an Apache restart before it will work. In the meantime if you go to webmail.yourdomain.helioho.st it will show the queued page with an estimate of when webmail should start working again. We will also be disabling webmail on Johnny to help with the 503 errors on that server too. We will likely need to disable free signups for a day or so because the server gets really slow while all the webmails are being disabled so account creations tend to time out. Let us know if you have noticed an improvement on the PHP performance of Tommy, or if you have any questions.

Installed. You can see the current list of installed modules and their versions for Tommy's Python 3.12 at https://krydos1.heliohost.org/pyinfo/info3.12.py

If you need to run a long running background process that takes more than 30-60 seconds to execute I would recommend using something like this https://wiki.helionet.org/Discord_Bot

WSGI control access has been enabled on the domain tinagoldenretreiver.helioho.st. To restart your Flask app and load new code changes in simply edit /home/tinagoldenretreiver.helioho.st/httpdocs/public/flask.wsgi. Adding a blank line, removing a blank line, adding a space, or removing a space are examples of editing the file. As long as the last modified timestamp changes it will clear the server cache. Let us know if you run into any issues.

Are you sure this is related to the scheduled tasks? I went to the URL and it timed out for me. Are you able to optimize your code so it doesn't take so long to run?

Are you able to use the scheduled tasks now?

Glad you got it working.

Like I said on the news post 6% of your memory usage came from Laravel, and 94% of your memory usage came from Node.js. Laravel had nothing to do with your suspension. You were unsuspended at 2025-05-07 13:14:31, and warned not to cause high load. Instead of reading our warning you just started a bunch of Node.js commands running again at 2025-05-07 14:39:28, and quickly went to 210 GB memory usage. You can be unsuspended this time tomorrow when your load is back to zero. Hopefully the 24 hours will give you time to read and understand that you share this server with 929 other users, and it's not fair for you to hog all the system resources, cause downtime for other users, and cause other user's websites to load slowly.