wolstech

It's probably a few things actually. Time of day is a big factor (the worst time for our servers is around 8PM EDT because we accept our day's worth of new account registrations during that time). I also banned a few accounts on johnny this morning that were probably contributing to load (they were running a spambot, those are notorious for causing load, ignoring the fact that sending spam is itself abuse).

675MB free as of this writing...http://heliohost.grd.net.pl/disk-space/

Unblocked.

This should be resolved for the time being. For the interested, the issue is the /var line under Tommy here: http://heliohost.grd.net.pl/disk-space/ When it hits 0, the server goes down because a lot of stuff doesn't like running out of space (PHP especially, can't save session data).

Done. Your account is now on Tommy. Thank you for the donation. If you see a queued page or 404 error, please clear your browser cache and flush your DNS resolver cache.

The username is actually naser01. Unarchiving...

Moving...

From what I can tell, your WordPress installation is either misconfigured, broken, or too bloated with extensions. The domain and server are working properly as evidenced by the phpinfo file I created: http://shgmta.ml/test.php For what it's worth, we highly recommend not using WP because it's poorly coded and laughably insecure. I'll let Krydos take a look at this and see what he thinks.

500 errors are not generally caused by these settings. The most common problem is file permissions needing to be changed. Start by verifying that all of your files are set to 644, and rename your .htaccess file to something else so it's ignored. Code errors can also cause this, but only if errors are turned off.

We don't allow users to change any of those settings to prevent abuse of resources. Krydos would have to change these for you. What PHP version needs the memory limit raised to 64M? Why? What PHP version needs the file upload limit raised to 128M? Why can't these files be uploaded via FTP instead? Also, we cap the timeouts at 30 seconds to prevent people from causing high load. It might be possible to have it raised to say, 60 seconds, but I can say for certain we would never raise it to 5 minutes. Honestly, if a script needs more than 30 seconds to produce a result, you should be rewriting or finding another script. If you really need the execution time limits, you would likely need to buy a VPS instead: https://heliohost.org/vps/ With a VPS, you have root access and can set whatever limits you please.

It's because the server is down because /var ran out of disk space. https://www.helionet.org/index/topic/34926-tommy-var-full/

Ironically, WP was actually the direct cause of at least one if not more than one of the /var issues. The downtime was basically a result of WP getting infected and sending spam (email lives on /var when it's waiting to be sent...in that case, the spam never sent because it was spam, so it sat and clogged up the space). We recommend not using WP if at all possible for this and many other reasons...

We'll move this for you as soon as we can I can't do it at the moment because we're working on getting a disk space issue fixed.

We're aware. The server is down because the disk is full. https://www.helionet.org/index/topic/34926-tommy-var-full/

Lets have Krydos look at this, but honestly, 200MB is ridiculously high...I don't think that's going to be approved. I'd suggest just uploading it via FTP instead.

Sure. We'll move you as soon as Tommy is fixed. He's currently down due to the disk being full. Please be aware also that since you have Java, you'll have to request it and wait again after the move. Moving servers unfortunately doesn't move your Java slot.

The server is currently down. See https://www.helionet.org/index/topic/34926-tommy-var-full/

That last few cases of this were caused by abuse, specifically infected Wordpress installations generating thousands of spam emails. Even though our system prevents them from sending, they still waste space... We ought to just make it larger though in my opinion. Even after cleaning it only has maybe 1GB free.

...and it's full again.

Argh.../var is full again.

Did you enable remote mysql? There's a separate page in cpanel where you have to add the IPs that will be connecting (or % to allow all).

Let's wait and see if Krydos can fix this on Johnny or not. If he can't, perhaps we can just move you because it's the only server it works on.

I'll let our other root admin Krydos take a look at this and see if he has any input on why this might be happening. In fairness, this isn't something we see used every day anymore, so you may very well be the first to use this functionality in quite some time...I know from a support standpoint you're the first person I've come across in my 8 years with HelioHost to ask for help using server-side includes. In fact, Perl in general doesn't get asked about much, let alone SSI. Python is the more common CGI language we deal with these days (usually Django apps). Perl and SSI are very old school ways of building interactive sites (though it should be supported as far as I'm aware).

It cannot be changed because it's already attached to your account as an alias. You would need to remove it first, let it finish (usually 10-15 minutes), then make it your main domain and wait.

Correct. It has to be pointed here before you can configure it. We don't allow you to add domains that aren't pointed here to help prevent abuse. By changing the name servers, you're proving you own the domain. If you're on Tommy, the downtime is only a few minutes. Domains set up usually in less than 5 minutes on Tommy anyway, so many won't even notice the move. DNS caches pointing to your old server will take longer to expire in many cases than the setup takes. If you're on Ricky or Johnny though, your downtime can be up to 2 hours. Your website will not function and your users will see a queued page during the setup progress.