Page 1 of 1

Admin login problem 500 internal server error ?

Posted: Wed Feb 09, 2011 4:50 am
by hostinganddesign
Hi hoping someone can help me out please im getting an error when i try to log into the admin section it just started to happen out of no where , nothing has been changed on the site or in any of the files its been working fine for 2 months now and just started to happen today this is the error im getting.


Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, webmaster@ido4u.ie and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.


If anyone has had this same problem or might know whats wrong please responds thanks everyone in advance for your help !

Re: Admin login problem 500 internal server error ?

Posted: Wed Feb 09, 2011 5:18 am
by i2Paq
What is your gzip / Output Compression Level: set to?

What is your hoster saying?

Re: Admin login problem 500 internal server error ?

Posted: Mon Apr 25, 2011 9:57 pm
by LVS
Have the same problem....anyone?

Re: Admin login problem 500 internal server error ?

Posted: Mon Apr 25, 2011 10:16 pm
by Qphoria
ISE 500 is a server issue.
Usually related to, but not limited to:
- Unsupported .htaccess commands. Some servers don't allow certain overrides in the .htaccess file. The first thing to try is rename ".htaccess" to "x.htaccess" and see if that fixes it. If so, then you can rename it back to .htaccess and edit it. Comment out using "#" in front of lines that use commands that may not be supported. Common ones are the +Options commands or any php flag commands
- Other errors on the server regarding some content or security warnings. Sometimes due to textarea boxes being saved with <script> tags

The best bet is to login to your server's cpanel and check the error log for the real error. Contact your host for further research and resolution