[Solved] Suspended: dariogr

[dariogr]

Hi! Long time user here. I have the server for some time now (8 years I think?), running a small Telegram bot for a community. Usually very low traffic.
Yesterday and today I was testing a new version and suddendly the account got suspended. Not sure if was because of the high traffic (I was testing and developing the new code), or because a security issue, but want to know what I did wrong so I can correct it.

Thanks in advance, an sorry if I caused any trouble.

HelioHost username: dariogr

Server: the account was moved, I think I was on Morty but I'm not sure

Domain: somnio.heliohost.org

Edited 4 hours ago by dariogr

[dariogr]

Ok, I have the reason now:

Quote

Your website has been disabled because it exceeded the 24 hour limit of 200 GB memory or 10,000 CPU

If you guys can provide some logs, I can get into it to see what happened.

[dariogr]

Quote

High server load due to excessive CPU...leaving your FTP connection open will indeed cause that. Please be sure to disconnect when not using it to help keep the load down.

Oh! I was using 2 FPT connections to sync in the background, can that be the issue?

[wolstech]

It's for excessive CPU coming from systemd. Yes leaving FTP connections open continuously will cause it, as can having cron jobs set to run too frequently. This was your load chart over the past 24 hours.

Are you ready to fix the issue?

[dariogr]

Thanks @wolstech. And Yes! I'm getting ready a dev bed in my local so I can develop without pushing changes constantly via FPT. I need access again to upload a code to unhook the bot so Telegram stops sending request, and redirect that to my local.

After development I'm going to eventually deploy the new bot to the server, if that starts causing issues again, I'm ready to completely remove it, leave the old bot that was working fine all these years and rethink what to do to stop abussing the system.
 

Edited 1 hour ago by dariogr

[wolstech]

Unsuspended.  

It might take a few minutes before you can log in again, and domains can take up to 2 hours to start working.

[dariogr]

@wolstech Thanks! Sorry for the trouble at the end of the year, guys, I was really not aware of the FTP limitation. Hopping the best to you and the team on the next year!