Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

Apache2 under Ubuntu 12.04

I get a 403 error only sometimes when a URL is passed to a PHP script in WordPress via the PressThis button. e.g.

This results in a 403 in the browser, and access.log is appended. But error.log is not appended.

Other URLs don't fail - they work properly, such as

"GET /wp-admin/press-this.php? HTTP/1.1" 200 7962 "" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52 Safari/537.17"

I have set loglevel to the most verbose setting of emerg. No error appears when the 403 is thrown.

Also, I have edited .htaccess to a minimal version that does no security and the condition still persists for some URLs.

Any ideas?

share|improve this question

By setting your LogLevel to Emerg (Emergencies - system is unusable.) you have reduced logging to it's minimum amount and only the most serious conditions are logged. You will need to increase log verbosity to at least Error to see 403's being logged.

LogLevel Error 

restart the apache service and you should be good.

share|improve this answer
thanks. unfortunately, made the change, cleared browser cache, hit the offending URL as above and no change to error.log. The last entry shows the server restarting. – Miller Jan 22 '13 at 13:05
@Miller: This works on the systems (Ubuntu and CentOS) I have to hand. Did you restart Apache after making the change ? Does the vhost you're connecting to have it's own ErrorLog directive ? – Iain Jan 22 '13 at 13:27
did restart, no change. The server directive for the vhost in question is ErrorLog ${APACHE_LOG_DIR}/error.log with an accompanying CustomLog ${APACHE_LOG_DIR}/access.log combined – Miller Jan 22 '13 at 13:55
I did notice that access.log is showing a 403 plus 407 error that I had overlooked. Here's an example of a URL that fails: – Miller Jan 22 '13 at 13:56
Note also please the error text presented in the browser reflects the 407 error, but I am logged in - to WordPress, so I don't understand what's going on. You are not authorized to access the webpage at…;. You may need to sign in. – Miller Jan 22 '13 at 14:01

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.