Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I was accessing in my server.

The modsec_audit.log showed the following error, but there is no related errors/warnings in modsec_debug.log. I could see the Internal Server error is logged in example-error_log.

How can I debug this Internal Server error?


[21/Mar/2012:07:01:52 +0000] T2l84H8AAAEAAGxPZ@QAAAAG x.x.x.x 33101 x.x.x.x 80


GET /RestAPI/index.php/tweets.json HTTP/1.1 Host: User-Agent: Mozilla/5.0 (X11; Linux i686; rv:11.0) Gecko/20100101 Firefox/11.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip, deflate DNT: 1 Cookie: __utma=159129855.1463065063.1331789485.1331789485.1331789485.1; __utmz=159129855.1331789485.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); 8cb6a414cf5ec1919864de0e80bea4da=0es7dcu0p10cocfpferb2lddi0; 8926e4f3c475bb6fcacb409299f1bd27=53cf8c5e6bf78ea45096945377e6d609 Connection: keep-alive Cache-Control: max-age=0


HTTP/1.0 500 Internal Server Error X-Powered-By: PHP/5.3.5 Content-Length: 0 Connection: close Content-Type: text/html; charset=UTF-8


Apache-Handler: php5-script Stopwatch: 1332313312358005 130428 (- - -) Producer: ModSecurity for Apache/2.5.12 (; core ruleset/2.0.5. Server: Apache


share|improve this question
up vote 1 down vote accepted

I guess mod_security is really just a messenger here, and not blocking anything by itself. HTTP 500 Internal Server Error is typically caused by

  • A faulty Apache configuration for that virtual host / directory
  • A faulty .htaccess file in that directory
  • Something else

Does everything else work fine at your server and only the tweets.json does not?

share|improve this answer
You are correct, Janne. I've disabled modsecurity and still gets 500 error. – max87 Mar 22 '12 at 4:38
Everything else in the server works fine. The tweets.json file's directory was recursively copied from another path ( and from that path tweets.json is working fine ) in the same virtualhost . The htaccess file is also looks good. Can there be any other reasons? – max87 Mar 22 '12 at 4:51

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.