Jump to content

Byron

Moderators
  • Posts

    9153
  • Joined

  • Last visited

  • Days Won

    146

Everything posted by Byron

  1. You would have to know which rewrite condition it was. Is the error only coming up when you make a certain request? Or are you getting a 500 error when you go directly to your home page?
  2. The 404 didn't have anthing to do with the error. I was just wondering if your 404 error page comes up that way with only the relative path. It may very well be a rewrite that is causing the problem but I couldn't tell you which one. It doesn't seem to be causing a constant error while going to your home page.
  3. OK, make sure you uninstall Frontpage and see if that helps you any. btw, is this working for you? ErrorDocument 404 /error.php I always have to use the full path to my error documents. Are you showing a constant 500 error now?
  4. Frontpage is FrontPage Extensions and since your not using them it's best to remove them. Go to your cpanel and look for the link named FrontPage Extensions and click Uninstall. After you've removed FrontPage you can look in your htaccess file for this and remove it also if you want. <Limit GET POST> order deny,allow deny from all allow from all </Limit> <Limit PUT DELETE> order deny,allow deny from all </Limit> AuthName aghr.heliohost.org IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*
  5. Do you understand what part of the htaccess your not using? And did you uninstall FrontPage when you registered with us or are you using FrontPage?
  6. Are you using your htaccess file for anything? If not then remove it or remove what your not using.
  7. Are you doing something that is using allot of system resources?
  8. Looks like somebody was abusing server resources at the time of your error. The administrator weeds them out as he finds them.
  9. You need to point idao.tk to our nameservers: ns1.heliohost.org ns2.heliohost.org
  10. The administrator is always working on it.
  11. You can check your Error log at your cpanel but it's probably somebody abusing server resources.
  12. This support request is being escalated to our root admin.
  13. I don't know why you didn't recieve the email warning. Either it went to your spam folder or it was blocked but you knew that you needed to login to your cpanel regularly.
  14. That's normal. Give it 24 to 48 hours.
  15. I'm sorry but it looks like that account has been deleted because of inactivity. Please feel free to create another account and be sure to login to your cpanel a couple of times a month.
  16. Can you post what's inside your htaccess file?
  17. This support request is being escalated to our root admin. Domain: slimlink.co.cc Username: jesper
  18. Go ahead and park your domain again and if it recreates the htaccess file again, just delete it.
  19. If your not using your htaccess file in your root directory then try removing it.
  20. If this is not a constant error than it's because of server resources abuse and the admin. is working on it.
  21. Byron

    More then one?

    It's allowed but your friend will have to sign a release form in triplicate. Just kidding! Yes it's allowed.
  22. This support request is being escalated to our root admin.
  23. This support request is being escalated to our root admin.
  24. No, we don't keep back-ups of anybody's site.
  25. What happens when you try to recreate it without deleting it?
×
×
  • Create New...