Jump to content

500 Internal Server Error


Beasts

Recommended Posts

This is a 'catch-all' error generated by the Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the Web server site to locate and analyse these logs

nothing on the PHP error logs indicate anything that could cause this.

the apache error logs should have something right?

i'll ask for the host to send them to me.

in the mean time, is there a way to change the location of the apache error log via a .htaccess file?

nothing on the PHP error logs indicate anything that could cause this.

the apache error logs should have something right?

i'll ask for the host to send them to me.

in the mean time, is there a way to change the location of the apache error log via a .htaccess file?

 

You can of course use phpflag directives, Note that if php.ini has been set to not read these, there's a slight possiblity it will not work without modifying the master:

php_flag  log_errors on
php_value error_log  /home/path/public_html/domain/PHP_errors.log

 

You can of course, as well deny access to the error log:

# prevent access to PHP error log
<Files PHP_errors.log>
Order allow,deny
Deny from all
Satisfy All
</Files>

 

EDIT: More here, http://php.net/manual/en/errorfunc.configuration.php

 

Apache error logs would require you to ask for them most likely, not a method I know off hand to retrieve them, especially through php, you don't have access to them.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.