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

I have found on my debian server that running the lighttpd module mod_access is causing the server to response with a 403 to all POST requests.

It's very odd as I have two servers, one is running as I'd expect and the other keeps returning these 403's. They are running identical configs for lighttpd and php.

My lighttpd.conf is:

There is also one other custom conf:

I've opened up the servers for requests until I get this fixed, the server that works is and the one that fails is

After working out that disabling mod_access resolves the problem I greped all my lighttpd configs for uses of it (docs).

Disabling each line I found didn't help, leading me to think this is perhaps some default behaviour (or bug?)...

Has anyone come across this before or know what configuration value I've got wrong?


  Debian: Debian GNU/Linux 6.0.6 (squeeze)
Lighttpd: lighttpd/1.4.28 (ssl)
     PHP: PHP 5.3.19-1~dotdeb.0 with Suhosin-Patch (cli)

Cross-Post on the Lighttpd Forum


Using lighttpd -p -f /etc/lighttpd/lighttpd.conf and finding the old values still being loaded. Turned out there was no syslinks but full files instead in conf-enabled.

share|improve this question
up vote 2 down vote accepted

Use lighttpd -p -f /etc/lighttpd/lighttpd.conf to verify the config looks like you want it to.

share|improve this answer
Indeed as pointed out on the forums, using this showed I was not using syslinks in the conf-enabled directory. :| – Sam Dec 13 '12 at 10:56

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.