Shinryuu

As the SO answer stated json didn't become a standard internal module until 2.6+. By default cPanel comes with 2.4.3, so #!/usr/bin/python will give that error. While #!/usr/local/bin/python2.7 will work fine.

Done, if you still see the account suspended page try clearing your cache.

The answer to this answers the problem thoroughly. http://stackoverflow.com/questions/14221360/why-is-import-simplejson-failing-in-python-2-7-3-code-but-not-in-the-interpre

The reason for the error was the existence of the subdomain, if you had removed it then tried adding the domain it would have worked. When you add a domain cPanel makes a new subdomain off your main domain with the name of your addon domain, so it was trying to remake the subdomain that already existed. After cPanel makes the subdomain it parks the new domain on the subdomain. Yes, setting the DocumentRoot to a folder that doesn't exist is what is recommended, cPanel generally creates a ~/public_html/domainname.tld folder, which doesn't exist beforehand, as a docroot for an addon domain.

This account has been suspended for violation of our one account per user policy which is clearly stated during the creation process of each and every account on Heliohost. A common misconception is that you need a separate account for each website that you want to host, but since Heliohost differs from most free hosts and even most paid hosting by offering unlimited addon domains, unlimited parked domains, and unlimited sub domains one can easily and conveniently host as many separate websites as they wish all from your one free hosting account. If multiple accounts were created to get around our disk space limit we strongly suggest using a free service such as dropbox to host your large images, videos, and downloads while continuing to host your website with us if you wish. If you understand that each user is only allowed to have one active account please let us know which account you would like to use and it can be unsuspended for you. Also let us know if you need backups of any of the data on the other accounts, and if there are any domains on the suspended accounts that you would like to host on your main account because we will need to remove them from the suspended account before you will be able to host them on your unsuspended account. For example: user1: unsuspend user2: backup user3: backup, idontreadrules.com user4: thoughticouldgetawaywithit.org

One quick thing I notice is you're using a bad username, a database user will also take the form <accountuser>_<dbuser>. Also if you're running the script on our servers you need to use localhost for the hostname, otherwise it should be fine.

We allow 2 cron jobs per day, if you want to install Dolphin then you have softaculous' help: For Stevie: http://stevie.heliohost.org:2082/frontend/x3/softaculous/index.live.php?act=software&soft=121 and Johnny: http://johnny.heliohost.org:2082/frontend/x3/softaculous/index.live.php?act=software&soft=121

Also consider taking a backup of your site and scanning it on your home PC with any scanners you have lying around. If you're getting a browser warning from chrome or firefox though you'll have to appeal that the message be removed by contacting https://www.stopbadware.org/ and asking them to review your site.

That account is not suspended and your domain is proxyku.heliohost.org.

Done, also watch the language please.

Your account was suspended for causing high MySQL load. I have unsuspended your account, but please try to limit the MySQL load you put on our servers as it slows down MySQL for not only your site, but MySQL for all of the other HelioHost users sharing your server. If you still see the suspended page, please clear your cache.

Note all the 1s in memory usage, your CPU usage isn't great either, so overall your site is some gobbling RAM and CPU cycles like crazy. I assume this is a scripting issue and not queries. Today some other guys decided to overload Stevie so of course your account was on the shortlist for accounts that needed to be suspended.

Your account was suspended for the following reason: Malware. 1 file(s). Suspect.Bredozip-zippwd-3 FOUND That means that there are some malware files found on your account. For your safety and to protect your website from potential further corruption the account has been suspended. To find the infected files we recommend making a backup of your site, download the backup file to your computer, and scan the backup using a reputable virus and malware scanner. If you're having trouble locating the offending files please ask and we can provide more information. If you are you certain that it is a false-positive, we strongly encourage you to file a false positive form here: http://cgi.clamav.net/sendvirus.cgi Your account should be unsuspended now, but keep in mind that this is a temporary unsuspension. You have 24 hours starting at the time of this post to clean your account of any and all malicious files or your account will be resuspended. I've done a little research on this for you, AV's tend to give this alert when they find a file within a zip archive with facebook in its name.

You were suspended for high load again. If you don't have time to fix any issues right now I can't unsuspend your account. The point of this is to bring attention to a problem with your account, when you post unsuspension requests we take it to mean you're ready to fix the problems. Let us know if you find time.

Post: username domain .war to deploy Or look at the dozens of deployment threads, that's why we use forums, so users can search for their problem and hopefully see something similar that was brought up before.

http://www.heliohost.org/home/features/domains

The account was causing abnormal load, we noticed the vBulletin install and checked it, thank you for being honest and open about this. Try to be careful about the load you cause in the future, vBulletin generally is a high load-causing software, so having it uninstalled now you should be fine. Your account has now been unsuspended, if you still see the account suspended page try clearing your cache.

Security forum is great, greater if we learn anything new. Just don't explicitly give out hacktools, clearly that is a big no-no. Ultimately you're in charge of policing anything going on within your account, if you find something and are unsure you are free to ask about it.

Do you have a ~/public_html/uploads/.htaccess file? If not what does your root .htaccess look like? By default the ~/public_html/.htaccess file has no ErrorDocument directives, you can make some custom shtml error documents through cPanel or make your own and use ErrorDocument directives to have those pages shown. cPanel handles adding the ErrorDocument directive for you.

Clear your cache.

You realize the last time this was brought I dropped a big hint about a trojan shell? Considering you didn't bother fixing it I'm not the least bit surprised.

Your account was suspended for the following reason: Malware. 1 file(s). PHP.Remoteadmin-3 FOUND That means that there are some malware files found on your account. For your safety and to protect your website from potential further corruption the account has been suspended. To find the infected files we recommend making a backup of your site, download the backup file to your computer, and scan the backup using a reputable virus and malware scanner. If you're having trouble locating the offending files please ask and we can provide more information. If you are you certain that it is a false-positive, we strongly encourage you to file a false positive form here: http://cgi.clamav.net/sendvirus.cgi Your account should be unsuspended now, but keep in mind that this is a temporary unsuspension. You have 24 hours starting at the time of this post to clean your account of any and all malicious files or your account will be resuspended.

Be patient, an admin will review your account and let you know what'll happen.

After a closer look it appears your account was in a half-suspended state. I've fixed it now so try to login with your regular credentials and let us know how it goes.

I thought I was pretty clear. You didn't attempt to fix your problem as far as I can tell, so the suspension stays.