yashrs

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

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

Your account was suspended for 12 cron job executions. The limit is 2 cron job executions per day. Your account has been unsuspended.

Use http://www.heliohost.org/home/support/scripts/renew to renew your account. It is inactive.

What I can suggest is a very silly and temporary solution and would only work if you have access to heliohost.org website on the registrar: 1. We can use cloudflare's nameservers temporary and point them to 64.62.211.132. 2. Instead of ns1.heliohost.org and ns2.heliohost.org on heliohost.org we can point a direct 'A' record to 64.62.211.132 in the domain registrar. I don't know if they would work out but these may be only temporary solution unless we get the problem solved of the DNS in our nameservers.

That account was inactive and has been unsuspended. I have set the last login date manually to 2015-07-30. So make sure you login before that after the http://www.heliohost.org/website works properly.

Thanks, I needed the IP Address. I am able to access epmonitoraggi.heliohost.org now.

Your account was suspended for 3 cron job executions. The limit is 2 cron job executions per day. Your account is unsuspended.

This will help :

Problem same to http://www.helionet.org/index/topic/21342-cant-access-heliohost/. There is a problem with the DNS records for heliohost.org. It seems to be removed from the nameservers. Krydos will be looking into this shortly.

InnoDB is broken on Stevie. Change all instances of InnoDB with MyISAM in the sql file and you should be ready to go !

Is that a InnoDB Table ?

Ok great ! Do let us know if you have any other issues.

Here is a Hello World Python Script to get you started. #!/usr/bin/python print "Content-Type: text/html\n\n"; print "Hello"; You can make that python file with extension ".py" in cgi-bin folder or have this in the ".htaccess" file of the folder in which you want Python scripts to be executed. AddHandler cgi-script .cgi .pl .py Options +ExecCGI

This is the reason for your suspension. Krydos will have more information on the file causing load. This support request is being escalated to our root admin.

Indeed, I was unable to access the email account after changing the password nor after creating a new mail account. The password has been mailed to the email id registered on board. This support request is being escalated to our root admin.

To reproduce the issue, I will need to change the password of your account to log in. Would you mind me doing so ?

What username are you using to signin ?

In cPanel, Cron Jobs Page under advanced section.

You have been suspended for having 4 cron job executions. The limit is 2 cron job executions per day. Your account is unsuspended now.

You can read here for instructions :- http://wiki.helionet.org/Moving_your_account

Please mention the name of the database which is missing. It will be in the format your username_database. An admin will need to fix your issue.

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.

This support request is being escalated to our root admin.

This support request is being escalated to our root admin.