wolstech

@Sagnik: That was the first thing I had him try...it didn't help. You're right though that a bad .htaccess is the common cause of this.

Your account was suspended for inactivity, because you haven't logged into your account in the last 30 days. To reactivate your account, please visit http://www.heliohost.org/home/support/scripts/renew. To prevent this from happening in the future please remember to visit http://heliohost.org/ to log into your account at least once every 30 days. If you are still seeing the Account Suspended page after renewing your account, please clear your cache.

Stevie was supposed to be upgraded to 5.4 at some point, but with the new server coming soon, I'm not sure it's still going to happen, or if so, when. Johnny already has 5.4. The new server will have at least 5.6 on it though, so once that becomes available, you'll have that as an option for getting the latest and greatest.

You should add it as a parked domain in cPanel. That will make it show the same content as your main domain. Just note that it takes 24-48 hours from when you add it to set up and stop being queued, just like the main domain. You might need to clear your cache after the time has passed to get rid of the queued page.

Thanks guys

I've reset your main domain for you...it seems like Johnny never set it up for some reason. Give it another 48 hours so the system can reconfigure the domain again...then clear your cache. If it still doesn't work, let me know and I'll escalate it for you.

Stevie experienced excessive load and downtime earlier. Not common for him at all, but it does happen on occasion, often when we get hit by DoS. You can see what happened here: http://heliohost.grd.net.pl/monitor/

It's not the account, it's what you installed on it that causes this error. The solution will be to troubleshoot whatever program you're using. If you still want to reset your account, you will need to delete it and sign up again.

Delete the wordpress install and reupload it.. By the way, I highly recommend against using WordPress...it's completely lacking in security, and its extensions and themes are prone to being attacked (or just including/being malware themselves, especially when you get them from dubious websites). That causes it to get hacked a lot. Hacked Wordpress is probably the number one cause of suspensions for spam and malware... If that still doesn't fix it, I'll escalate this for you.

Screen door hinge, more specifically the hydraulic piston used to control closing.

Login date is today. You're good

Wall mount can opener? Some form of shade or curtain? Human powered eliminates most things like appliances and fans...yet it has an adjustment for speed. Confusing when you say it's mounted 6' 6" off the floor (which would put it well over my head) but could also be practically on the ground...

500 errors are usually caused by broken software or too much load. If it does not go away on its own, you may need to fix your software.

Try renaming the index.php as well. You should be able to get a directory listing. Also, check in your account's home folder (the folder that public_html is inside of) for an htaccess and rename/delete if present. If that doesn't work, disable Cloudflare and purge the cache on their website and try again. I wouldn't be surprised if it cached the forbidden page. (Also, if I end up escalating this, the first thing Krydos will probably ask is that you change your nameservers to ours to eliminate Cloudflare completely)

If the python script is written for a web server, it can be made to accept data from POST and GET requests. You'd make a form in HTML to enter the required data, the submitted data is passed via POST to the script, script runs it and returns output. I don't know how to handle POST data in Python though (I'm a PHP programmer). You can likely eliminate the PHP component entirely if you're insistent on using Python. Do you have good reason (other than not wanting to rewrite your code) to use two languages? If it were me, I'd just rewrite the Python tasks in PHP and discard the python components...

Try renaming the .htaccess file in public_html. Chances are its set to deny you access.

You can't since we disabled exec. The closest I can think of is to write the python script as if it were for a website, then file_get_contents() the script through the web server from php. The output of your python script will end up in the return variable of the file get contents call for you to use in php.

Your account was suspended for running too many cron jobs. To help keep load low, we limit accounts to two (2) cron executions in a 24 hour period. This means that, if you only have a single job, it can run no more frequently than once every 12 hours, with two jobs, they can each only run once a day, and so on. Your account has been unsuspended.

This support request is being escalated to our root admin.

Database is likely invisible from the repairs last year. Escalating.

Seems to be working for me now as well. As tjoene said please clear your cache.

@Byron: Can you unblock me in Stevie's firewall please? I think I just managed to block myself for DoS using the Open All on the phishing scanner... :unsure: Speaking of that...can these IPs be whitelisted so this doesn't happen to me? * 204.13.205.35 * 69.242.123.95

You could try moving to Stevie, but I don't know how well his postgres works (it is newer if I remember right). I was able to create a database and user in cPanel and view/edit it in PhpPgAdmin though, so it appears to be working...

We changed it to MyISAM intentionally. InnoDB has a past history of being extremely unreliable here. It crashed a while back (on both servers no less!) and was broken for well over a year. It was actually just fixed a few months ago. It was read-only for everyone, and the mysql server would crash for everyone on the server every time someone tried to edit an InnoDB table. A ton of users had to convert their databases to MyISAM at that point, or have their databases manually restored when the server was fixed. Everyone had to recreate their database users too. In fact, because of it, I don't even have a single InnoDB table on my account anymore that I can test with! I dropped all of mine when the server was finally capable of doing it without crashing...

I'm seeing that as well. Says your active though and resuspending/unsuspending you isn't fixing it. Can you rename or delete the .htaccess file in your public_html folder?