[Mark]

Can someone here try accessing an svn to see if its just me getting an error message-- Server sent unexpected return value (403 Forbidden) in response to PROPFIND --or if there is a bug since the server update that Yatta mentioned recently. I tried 4 different svn's and same message

EDIT. Someone else tried and could access an svn from this site that I'm having problems with. It turns out I can still commit something but the above error message shows when I try to update on any svn.

[TerminX]

I need more information to investigate this. You haven't even specified which repository it is... how am I supposed to look into it?

[NightFright]

I just checked with the Duke3D HRP SVN and had no problems at all. Maybe you should do a cleanup of your local repo, or, if nothing else helps, just do a completely new checkout.

[Daedolon]

NightFright, on 14 August 2013 - 01:53 AM, said:

or, if nothing else helps, just do a completely new checkout.

Unlucky. I just got him to do that not too long ago.

[Mark]

I'm leaving for work, back with details after. All svn's are affected. Duke HRP, SW HRP, Decay, DD, WGR2 Not just one that needs a cleanup.

[TerminX]

I found some log entries indicating your IP address was blocked by a security module due to excessive requests. You weren't trying to update all of those repositories at the same time, were you? I fiddled with the configuration of the security module in question a bit, let me know if it changes anything.

[Mark]

When it didn't work on one svn I went to the others one by one but not at the same time. Or when I update one I usually go to the others right afterward. But always one at a time. I'm still at work, I'll try again when I get home.

[TerminX]

You might also want to upgrade your SVN client... it looked like you were using a pretty old one judging by the server logs.

[Mark]

I'll look into a newer version of TortuiseSVN. Up until the other day it was "if it ain't broke...."

[TerminX]

I don't necessarily think that that's the problem, but a newer version isn't going to hurt anything.

[Mark]

I tried 2 of them, waiting about a minute in between, and its working. Thankyou very much. I'll try not to do them "rapid fire" in case that caused the red flag.

[TerminX]

Cool, good to know. Some of the settings for the security module in question were a bit conservative... I don't think I'd updated them since before we moved servers a few years ago. It's an anti-DoS module that limits stuff like concurrent connections, how fast requests can come in from a single address or on a single socket, etc. Our previous server was woefully underpowered so it used to be necessary in order to serve the HRP downloads, etc.