Topic: Reason for a 403 error

[taustin]

I have an intranet set up for my employer using e107, running on "Apache/2.2.22 (Win32) PHP/5.4.5" (Windows is 2003 server, 64 bit) as a CMS. It's been working fine for all 18 locations.

Yesterday, one location (and only that location) started getting 403 Forbidden errors trying to log in. The result is the same in IE9 and Firefox, and on all Windows computers at that location. Oddly, someone with an Android phone got on the wireless network, and was able to get to the log in screen OK.

Other web sites work fine, including other web sites hosted on the same server, as well as a phpinfo page within the e107 site. Only the e107 pages are affected. Attempts to log in to the sister server, running the same version of everthing (except that Windows is 32 bit on that one) work fine in all respects.

The access logs show the connections, with a status of 403. (The site is set up with basic authentication, and log in prompt for that shows up, and works OK - the logs show that, too). There is nothing in the error log related to these connections at all.

There is nothing in any <Directory> directives, nothing in the virtual host directives, or anywhere else I can think of to look that would case this connection to be refused.

I am completely stumped. I'm suspicious of a virus loose on the local network, but even that doesn't make much sense, since that should, at the least, affect any attempt to connect to this particular server.

Is there a way to get Apaache to tell me why it's issuing a 403 response?

[admin]

Indeed weird. Any configuring change at that location, like (windows) change/update at the local computers ? Or a change in user/authorization in E3107 for that users/locations.


Steffen

[taustin]

It turns out to be the auto-ban feature in e107 after someone forgot their password and failed to log in 10 times. The rejection response looks just like an normal 403 message from Apache.