Jump to content

Ice IT Support

Members
  • Posts

    1,643
  • Joined

  • Last visited

  • Days Won

    38

Everything posted by Ice IT Support

  1. Have you tried deleting just .htaccess files? If this is really something you want to do, select everything in the public_html folder and click delete.
  2. Please clear your cache.
  3. Be sure you are connected to localhost, and your database user has been granted privileges to the database.
  4. Running large PHP/CGI scripts would cause this. I don't have the access to tell you what specific file or process.
  5. The domain has MX records configured correctly, why would that be the problem? Unless the user/email was not created in Google Apps.
  6. Your account is listed as 'queued' in the database, I think there may be an error with your account. I cannot access your site either.
  7. I think this may be an issue on HelioHost's end, probably caused by your DNS configuration. This isn't your fault, HelioHost's configuration tends to be picky about DNS. It's not typical for a domain to have more than one A record. @admins: Thoughts? Anything I may be missing?
  8. Is the mail for the domain with errors hosted by HelioHost or Google Apps?
  9. Look at a suspension as your warning. Unsuspending an account is as easy as clicking a button. Inactive accounts can easily be re-activated by the user. The suspension is the week-early warning, not the end of the world (or in this case the end if your time with HelioHost).
  10. 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.
  11. Please clear your cache.
  12. Dedicated IP cost is a one-time charge, sent to admin@heliohost.org via PayPal.
  13. If the directory is under your home folder, you may delete it at any time. If it is stored in /tmp, an admin will have to delete it for you. HelioHost does not tamper with user's data, so it would not be deleted automatically.
  14. Glad your problem got solved! Please spare a few minutes to take our brief survey: http://feedback.heliohost.org/ Your participation in this survey is greatly appreciated.
  15. Postme and postbox have been deleted, postfreg has been unsuspended.
  16. You have three accounts: postme, postfreg, and postbox. Users are only allowed to have one account. Choose which account you would like to keep, so I may delete the others.
  17. Did you add your domain as a parked or addon domain in cPanel? Also, I would recommend setting your nameservers to ns1.heliohost.org and ns2.heliohost.org
  18. 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.
  19. Stevie: Apache2 + OpenSSL cPanel Johnny: Tomcat cPanel
  20. Are you sure you can't abandon Yandex nameservers? I think all you would need to use their email is the MX record and mail CNAME. I know users have successfully added domains without using our nameservers in the past, I never remember how.
  21. 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.
  22. http://www.helionet.org/index/topic/13575-more-johnny-issues/ and http://www.helionet.org/index/topic/13628-johnny-news/
  23. Suspended. Your data remains intact.
  24. For a site to crash MySQL would require EXTREMELY HIGH database traffic. The first thing that comes to mind is lack of protection from, or purposely caused SQL injection/poisoning. High traffic doesn't seem to be a likely cause to me, if it was you would have a max users error, and SQL would not crash. My suggestion: protect your site from SQL injection. There are a plethora of articles on Google for simple ways to harden your site.
  25. Username, domain?
×
×
  • Create New...