[Solved] Suspended: wbsentin

[wbsentin]

username: wbsentin

server: Ricky

main domain: wbsentinel.com

Thanks.

 

 

 

[flazepe]

Your account was suspended because Wordpress is causing too much 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.

 

This is really common for Wordpress. It can cause massive amounts of load even if you're hardly getting any traffic to your site. Wordpress is also incredibly insecure and very easy to hack. We see Wordpress accounts get hacked all the time and usually the hacker sets up a phishing site on your domain. We strongly recommend using any software other than Wordpress.

 

Something that might help is this simply static Wordpress plugin. It will speed up your site, reduce the load you cause, and reduce your chance of getting hacked. If you try it let us know how it worked out for you.

 

If you insist on using Wordpress you might want to consider purchasing a VPS instead. VPS hosting gives you an entire virtual server to yourself, including no load limits, a dedicated IP address, and full root access. Wordpress sites load relatively slowly on our shared hosting, but they will be much faster on a VPS.

[wbsentin]

Thank You. I haven't used the WordPress install for a while. (Still building on local server.) Could you tell me when this was suspended for resource usage? WordPress at the moment isn't open to public. I only have a redirect index page that forwards to Facebook for the moment. So if resource usage was high, it was due to the admin side. 

Thanks. 

Edited December 18, 2020 by wbsentin

[flazepe]

This support request is being escalated to our root admins.

[wolstech]

Krydos will probably be able to answer when it was suspended, but it's worth noting that WP will cause load even if not public, simply because bots will pound on the login page. Also, if there's a backdoor due to malicious extensions or the like, those will often work with the site disabled. I would suggest fully blocking WP if you don't use it and don't want to delete it (putting a deny from all at the bottom of the .htaccess for WP will usually suffice).

[wbsentin]

Krydos will probably be able to answer when it was suspended, but it's worth noting that WP will cause load even if not public, simply because bots will pound on the login page. Also, if there's a backdoor due to malicious extensions or the like, those will often work with the site disabled. I would suggest fully blocking WP if you don't use it and don't want to delete it (putting a deny from all at the bottom of the .htaccess for WP will usually suffice).

Thanks. I'll work on that as well. Maybe changing the location of the login page will do. But the WordPress install is on a subdomain with directory privacy on. (I have to actually log in to even load the backend of WordPress.) Doubt this is what the issue is. 

[Krydos]

It looks like what happened is you installed Wordpress through Softaculous, and you have Softaculous set to take automatic backups. The automatic backup caused Wordpress to make a lot of load and that's what triggered the suspension.

[wbsentin]

It looks like what happened is you installed Wordpress through Softaculous, and you have Softaculous set to take automatic backups. The automatic backup caused Wordpress to make a lot of load and that's what triggered the suspension.

OK. Thanks. Odd that a daily Softaculous backup would trigger a load suspension though. But I guess I'll be sure to turn it off.