wolstech

Wordpress...classic. WP is notorious for causing this and is the #1 cause of load suspensions. The best solution to Wordpress load is to not use Wordpress, but we know that may not always be possible. Removing extensions can also help (WooCommerce, WordFence, and Elementor are three well known problem extensions). Please take a look at this topic regarding how to manage WP load: https://wiki.helionet.org/misc/wordpress You can monitor your load here: https://heliohost.org/dashboard/load/ How do you plan to resolve this so it doesn't happen again?

I've added deny from all to your .htaccess and unsuspended you. Please ensure that your scripts are written to delete any file it creates in /tmp when it is finished using it, then remove the deny from all when ready. Your current script is just abandoning its temp files...PHP does not clean up on its own. Your script must either explicitly move them to your home folder if you wish to keep them, or you can call unlink() on them to delete them. If you don't do either, they just get left in /tmp forever and it fills up. If you fill up /tmp again, the suspension will be permanent and you'll be required to get a VPS if you wish to continue hosting your software here.

Krydos can help you with this

Enabled.

Subdomain added. it can take up to 2 hours to work. For the PHP errors, it would be best if you disable the error reporting yourself by adding this line to the top of your PHP scripts. For programs you didn't write, you can often just add it to the top of the program's config file to turn it off. error_reporting(0); Turning it off on our side doesn't make much sense as you won't be able to troubleshoot anything...you'll just get a plain white page or a 500 error instead. Doing it as above means you can turn it back on if needed.

You are suspended for crashing Johnny. Your account was running something that filled up the /tmp volume with several gigs of image files and caused email and PHP to go down for 8 hours, which caused an outage for over 2000 other websites. Can you explain what you were doing? And what will you do to prevent it from happening again if we give you a second chance?

You're suspended for high load because whatever you tried to run was so absurdly heavy on resources that it used up your entire day's allocation of CPU and RAM in the span of about an hour. In fact, it was so heavy that you managed to go almost 13% beyond your quota before the system had a chance to even finish suspending you.

That domain is not valid because it contains spaces, has no TLD, and should not contain symbols except hyphens (periods are reserved to separate out the parts of a domain, and other symbols are not supported). Also, domains are not case sensitive, so are generally written in all lowercase. Would krzysztof-lewkowicz.helioho.st work for you?

Not at the moment no. We might be able to get Payoneer working if that's an option for you as we've used them in the past, but we'd have to get that set back up if you are able to donate that way...

You're suspended for having 2 accounts. Users are only allowed to have one account. Which one do you want to keep?

There was an issue with accounts that were migrated to new Tommy early on that specifically broke SFTP. Krydos can fix it for you...

Also, since you're one of the rare cases where you're allowed to have two accounts, we would need to know which one you want to move. Or you can donate twice to move both of them..

I'd recommend $6, that way you'd get an extra 1000MB space too. Since you already have an account, you can send the money by donating through any of our normal donation channels (https://heliohost.org/donate/), then post the transaction ID here so we can verify the donation and move you. We can just directly move the account to Tommy. You shouldn't need to set it up again...

You're suspended for having more than one account. Users are only allowed to have one account. Which one would you like to keep?

Should be working again. Someone else had filled /tmp up with junk from a broken script...

Try again now. Someone else had filled /tmp up with a broken script...

Try again now. Someone else with poorly written code filled up /tmp , which causes a lot of things to stop working.

That's probably because /tmp was full due to another user's software malfunctioning. Try again now.

This should be resolved, and your site is no longer showing an error for me. Another user had filled up /tmp causing the server to stop working properly.

Should be working now. Someone filled up /tmp on the server...

You probably need to set up SPF, DKIM, and DMARC. Gmail won't accept email without them. Since you are using Cloudflare, you'll need to set these up yourself. For SPF, you can create a TXT record with a blank name (i.e. the same name as the domain) and this value: "v=spf1 a mx include:johnny.heliohost.org ~all" For DKIM, you need to enable it in Plesk under Mail Settings, apply it, then create the DNS records shown under the "How to configure DNS" link next to the option (usually two records). For DMARC, you can create a TXT record called _dmarc and use this value: "v=DMARC1; p=quarantine;"

The domain is working for me now. I see what looks to be a soccer (football) website.

Node really uses that many resources, and it's the second leading cause of suspension behind Wordpress. It is extremely inefficient. It is worth noting that if you noticed a spike specifically in the memory numbers in the past day or so for a program that has worked previously, the memory calculations were recently updated to more accurately reflect memory usage. This was the result of a user who managed to almost crash the server, and the new calculations will reflect as an increase in memory usage for users with long-running programs like Node and Python. PHP users are less likely to be affected by the changes because PHP both exits after each page is loaded, and times out after a minute or so if it doesn't finish.

More than likely that's exactly the cause. Your site is constantly using tons of resources due to all the cron traffic. Lower the frequency of those calls to like once every 5 or 10 minutes and your load will probably drop significantly.

I'm not sure honestly, but my guess is 24 hours (basically once all the red disappears), assuming you don't have any new hours during that time where the limit gets exceeded.