wolstech

Causing high server load. 590% more memory than #2. /home/micou/public_html/cgi-bin/videoclip.pl You're suspended for severe overuse of resources. From the looks of it, you're retrieving or processing video files, which is very resource intensive and too heavy for Tommy. We recommend a VPS for this sort of usage: https://heliohost.org/vps/ The file listed has been renamed so it won't run, please delete it. You've been unsuspended.

Causing high server load. 177% more cpu than #2. 107.1 GB bandwidth over the last week. /home1/mediaexp/public_html/api.php You're suspended for severe overuse of resources. The file indicated is the cause of the excessive usage and has been renamed so it won't run. Please delete it. Whatever that file does (retrieves/processes videos from the looks of it) is too heavy for Tommy, and uses way too much bandwidth. We recommend a VPS for this sort of use. https://heliohost.org/vps/ You've been unsuspended.

Your redirect in .htaccess is causing an infinite loop (an .htaccess file applies to requests made for subfolders too, so the redirect was catching everything including the destination and trying to redirect it). I commented that out and replaced it with an index.php that redirects everyone into the forum folder for you You could use an .htaccess for this, but it would need exception rules for /forum/ as well as things like /.well-known/ added...the index.php method is just overall easier for this application. https://greed-is-good.com/

If you've removed wordpress, you can just edit your .htaccess in your home folder to delete the deny from all (that was the only thing in it actually, so you could just delete the .htaccess entirely). That should make your website start working again.

Causing high server load. 487% more cpu than #2, 288% more memory than #2. /home1/gringoh/public_html/xmlrpc.php You're suspended for causing severe load on Tommy. The file mentioned is either broken or too heavy to run here. Considering it's part of WordPress, your most likely cause is one of your extensions is broken. We generally suggest not using WP at all because it's notorious for this sort of issue (among other things, hacking leading to malware or phishing bans are other common issues with it), but if you want to keep it, I would start by reinstalling WP and not using so many extensions. I've unsuspended you, but I've added a deny from all to the .htaccess file in your home folder so your website won't work until you fix it. This will prevent the broken script from running.

Unblocked.

Done.

Unblocked.

Johnny's load went down because we limited the number of new accounts on him per day to 1 for a while. As more and more accounts went inactive or got suspended without being restored or replaced, load went down over time. Ricky and tommy have high loads because of a combination of the number of accounts and on occasion abusive users. For a while Ricky was accepting 15+ accounts per day because Johnny had such poor uptime. Since not too many accounts expire on Ricky each day, the number and resulting load increased. The missing 0.05% on tommy is Apache restarts. During these, the server briefly goes down, usually for 30-90 seconds. They happen every time a domain is added, modified, or deleted. This is unlike Ricky and Johnny, where these restarts occur every 2 hours if a domain is waiting to be configured (this wait until the next start finishes is the reason the queued page exists). Ricky's load is high with few accounts because he's ancient. Hardware is 12 years old. That's as compared to Charlie (10 years old), and Eddie (8 years old). Whenever they stop working. Cpanel updates are incompatible with our custom code, so we have to debug and rewrite a ton of stuff every time we update. In addition, newer software is optimized for newer hardware....our hardware is only getting older since we can't afford to replace it.

We have it set to run overnight automatically. It runs sometime around 4 AM. If it hasn't done it in its own, I'll run it when I'm at a computer...

Done. You should now be able to log in and your website should start working within 2 hours.

It's archived due to inactivity. Unarchiving...

Unblocked. The "default" account for a user (which is the one in the form jamieoz@tommy.heliohost.org ) doesn't have IMAP access. Only the regular mailboxes that you create have IMAP. I suspect this is why you're having trouble with it. If you need to bulk-delete your unread messages, you can remove them from ~/mail/new (or ~/mail/cur if they've been read). A piece of Mail on our servers is just a file.

Unblocked.

That's intentional. We only accept a few registrations each day. They all reset at midnight UTC every day and usually last about an hour overall, with johnny accepting the most accounts. Tommy usually lasts for seconds. If you don't want to try at midnight for a free account, donating will get you a tommy account without the wait. You'll get an email within 24 hours of donating that lets you skip the wait.

Renamed. As for Johnny, fewer accounts. For a while, we had Johnny accounts limited to 1 per day to reduce the numbers. Numerous accounts get suspended on Johnny every day, so after a few weeks of that, the numbers dropped substantially and he's stable again.

AutoSSL already ran on its own. The DV succeeded and a certificate request was submitted but the request is in the pending queue waiting to be issued. I suspect something's just broken because there's requests in the queue from as far back as January 28. These usually fulfill within 24 hours. Lets have Krydos look at this.

It's Super Bowl Sunday here in the USA, there's been nobody around most of the day. Sent.

All processes for user sebas have been killed.

That sounds odd. Let's see if Krydos has any ideas or additional logs to look at.

It varies by server. If you go into the page where you create the mail accounts in cpanel, there should be an option for mail client setup. You can pick "manual client configuration" to see the actual settings.

Sent.

Sent. Sorry for the delay on that and thank you for the donation

Your email domain was execs.com, which is a known abuse domain (we've had numerous phishing sites with addresses from that and similar domains like consultant.com, and the domain itself has no actual content on it, which is the norm for abuse domains). Yes I would recommend a different email account, or even just an address @mail.com would be fine. As for your username, one of the phishing sites on the account was "microsoftexcelverification", which your username hints at (Microsoft excel -> micro excel -> micoexel). This sort of shortening is *extremely* common with intentional phishing accounts. Basically, whoever you sent your info to checked just about every box in the book when it comes to both automated and manual phishing detection. If you post a new email address, I'll send you an invite for a replacement Johnny account.

There's probably a redirect that's keeping it from reaching the validation file. Make sure the .well-known folder is accessible over plain http or it won't work.