Ice IT Support

Your shebang line should be #!/usr/bin/python on HelioHost. Sorry I didn't notice that earlier.

Please provide a link to the script and the server you are on.

You are missing a closing curly bracket } on line 2. It should look like .shown { display: block; }

Please create a new topic in Customer Service.

MySQL is running on TCP port 3306 (the default).

Please post the following information: Your cPanel username Your main domain The server that you are on

I think he's talking about his forum accounts, not hosting accounts.

Your account is now active. Try it now.

I don't know if it is something that users could fix, since an attempt at fixing it would likely cause another crash. As for recompiling, it is safer to fix any other issues first, that way we can potentially upgrade MySQL when it comes time to recompile.

You have semicolons at the end of lines 2-4 in your dispatch.wsgi. Those shouldn't be there. That could be the source of files not routing properly.

This support request is being escalated to our root admin.

The root admin can tell us what file is triggering the malware flag.

First you need to request to enable Java for your account at http://www.helionet.org/index/forum/74-java-requests/ Once Java is enabled, the server automatically processes JSP files. You may request a .war file deployment in Customer Service.

You just created your account. Give it 24-48 hours to come out of the queue.

Your nameservers are still set to use Cloudflare: http://bybyron.net/php/tools/dns_records.php?domain=dexterous-gaming.tk&rec=NS If you want to use Cloudflare, see Krydos' post here: http://www.helionet.org/index/topic/15044-answered-cloudflare-heliohost/ Otherwise, set your nameservers to ns1.heliohost.org and ns2.heliohost.org, wait 24 hours, and you should be good to go.

Last I heard is something like this: The MySQL server is mostly stable. It doesn't have a problem until someone attempts to access a corrupted InnoDB database, and then MySQL crashes. It is supposed to restart itself after about a minute, but sometimes that doesn't happen. The corrupted databases have to be gone through and fixed manually, which is what is taking so long. That's my understanding of where we are at. Feel free to correct me if I'm mistaken.

His username is albertoc

Are you able to now? Does PM work for you if not? If neither work, let me know at iceitsup |at| heliohost |dot| org

We've had that issue come and go the past few days and are not quite sure what the cause is yet. Please be patient, we are working on the issue as fast as we can.

Believe it or not, HelioHost's main source of income is the ads. We do receive occasional donations. HelioHost owns its own hardware, meaning we don't have to pay rent for dedicated servers. The staff here are all volunteers .

<p>If you aren't sending those emails, here are some things to try:</p> <ol> <li>Change your password for cPanel and all email accounts</li> <li>Add a CAPTCHA to your contact forms (like https://www.google.com/recaptcha/intro/index.html)</li> <li>Limit or disable email notifications from forum software</li> </ol>

This support request is being escalated to our root admin.

Your account was suspended for the following reason: Malware. 1 file(s). Perl.Small 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.

This support request is being escalated to our root admin.

Contact their support staff and ask if one nameserver will suffice until we can get NS2 running again.