wolstech

It clearly wasn't enough based on that chart above. Your app is still too heavy. In order for the software to not get you suspended, it can't use more than about ~50MB of RAM continuously, which is admittedly extremely difficult to achieve with a long running node process. (node-based websites and such are much easier to accomplish here because they can rely on Passenger to stop them when there's no traffic, but a telegram bot can't do this since it has to listen to its channel continuously). Most users here who are running these sorts of bots here have chosen alternatives like Python because it's more resource efficient and won't lead to suspensions like this. If you want, I'll unsuspend you one more time, but it comes on the condition that you either rebuild the bot in something else so it doesn't slow the server down, or that you use the account for something that is not related to said bot. A future suspension after that for node-related load would be a permanent ban from our service. Do you want me to do that?

You didn't fix your load issue and got suspended yet again for it (previous suspensions on the 15th and 17th). It's unfair to the other 2000 users for your account to be slowing everything else down. We have a 3 strikes policy here for suspensions, and you just struck out. Your Plesk account cannot be unsuspended due to repeated failure to manage your load. You'll need to either buy a VPS (which will isolate your software on its own server so the load won't impact other users) or find a new host for this software. If you're interested in a VPS, you can purchase that here: https://heliohost.org/vps/ (it comes as an empty Linux box with root SSH access and you can install whatever you want provided it isn't illegal, including this telegram bot).

Fixed.

If I remember right, for Python and similar, the log files aren't specific to a given account and as such contain other users' information, so it isn't available in the UI. Some of the data may appear in the Plesk Logs tab, but these logs are usually limited to Apache and Nginx logs.

I never even saw this because it was marked as solved. I'll fix this shortly...

Node has been disabled on your account so the program won't start, and the account has been unsuspended. It may take a few minutes to work. Please fix the issue immediately. If this occurs again, you will not be unsuspended a second time.

You're suspended because you caused such extreme load that you almost crashed Tommy. Either your app is WAY too heavy, or more likely it's broken, and either you or the server kept restarting it despite it not exiting. Either way it cannot be run here. Do you know why this may have happened?

You can do this yourself in Plesk. Click your name in the upper right, and "edit profile".

I just checked again and realized that removing that backup didn't bring you below 1000MB, so it resuspended you. Do you want me to delete the next-oldest backup in the same folder?

Thanks for reporting this. I've passed it onto Krydos to see if it can be addressed. I had this same issue a while back, but at the time we thought it was my phone causing this so the solution was to just turn the ads off for me since I'm staff. This makes it look like a more permanent solution is needed...

Added. It may take up to 2 hours to work.

This error occurs when apache is restarting and takes longer than normal. It generally clears up on its own in a few minutes once the restart finishes.

The best solution to WordPress load, is to not use WordPress. To give an idea a WordPress site with no traffic will cause more load than a site made in other CMSes with several gigs of traffic (nodejs-based solutions notwithstanding).

Resolved on discord.

Removed and unsuspended.