500 Internal Error

[broccaj]

The server encountered an unexpected condition which prevented it from fulfilling the request.
The script had an error or it did not produce any output. If there was an error, you should be able to see it in the error log.

Please i don't know exactly what to do with this error, I need help urgently.
I really know, all what i have to do to resolve this, all the configuration, etc.....!

[swpowell]

You will need to enable cgi for your account.
I think you can do it form OPS or call / email support.

[broccaj]

i already do that, but, that error still exist.

[Builder]

Check that you have correct permissions (CHMOD) on your script, other files, and folders. You can do that in OPS.

Also be aware that CGI enabling takes place only twice a day (6:00 AM & PM??) so if you requested enabling earlier today you will have to wait until later this evening for it to take effect.

Good luck,
Kevin

[broccaj]

How can i have correct permissions (CHMOD)?, .......

[entrecon]

CGI enabling takes place only twice a day (6:00 AM & PM??)

Actually, I believe it is 9am and 6pm.

[Builder]

@ broccaj: In OPS you can go to File Manager to check and change permissions. Your script should have indicated what permissions were necessary to run it.

@ entrecon: I knew someone smarter than me would come along. ;)

[dmacminn]

Unfortunately, there are many, many, many, many, things that can cause this "vanilla" error message to occur ---

"The server encountered an unexpected condition which prevented it from fulfilling the request.
The script had an error or it did not produce any output. If there was an error, you should be able to see it in the error log."

1) You SHOULD check the CGI error log (under CGI and Scripted Language) to see what may be generating it.

2) You should suspect any script/file that has been recently changed.

3) You should verify that the permissions are set correctly -- use a chmod or Fileanager to force them to the required value just to be sure

4) You SHOULD create or test with a simple phpinfo(); call to ensure that CGI is operable

5) You should verify any database being called can be connected to with a simple connection script, and that the database is in good shape (run check tables/optimize).

6) You should verify that there have been no recent changes to the .htaccess, domain redirects or similar features -- we see many cases where a redirect or rewrite rule or line in .htaccess is causing the issue

7) You should retry at various times -- it could be a busy server due to someone else running a scheduled job or an account being exploited due to a bad script or application.

Try, at the least, to rule some of the above things out ... Technical Support will not review or correct scripting (they just aren't trained or paid to do that) -- if basic tests of CGI come back OK, you will need (perhaps with help from others here) to determine the locus of the error. Certain applications seem to get into "mode" where they do this -- sometimes just due to content or a version change or some other issue -- these are hard to isolate.

[insptimes]

I had the same problem I had to put name.domainname.com/