I don't know. I'm not a firewall person.

This problem is a firewall problem though. We see it once a month or so. The firewall's DPI/IDS is blocking and/or corrupting the SVN-specific HTTP commands.

How to stop this happening is probably a question for your firewall vendor.

Followed by "wtf are you even doing this in the first place?"

Adam.

Sent from BlueMail
On 17 Oct 2017, at 19:37, Josh Bierman <jbierman@yeshivatnoam.org> wrote:
Adam,
I am already whitelisting ports and protocols and all headed to/from 37.187.79.83 (svn.observium.org)
How else (can't do complete DMZ) can I "not mangle" it?
What port/protocol am I missing?
(and thank you for the super fast reply).

Joshua Bierman
Director of Technology
Yeshivat Noam
201-261-1919 x136

On Tue, Oct 17, 2017 at 2:02 PM, Adam Armstrong <adama@memetic.org> wrote:
Your firewall is mangling SVN.

You need to make it stop doing that.

Adam.

Sent from BlueMail
On 17 Oct 2017, at 18:50, Josh Bierman <jbierman@yeshivatnoam.org> wrote:
Hi All,
I am getting an error when I go to update.
 Server sent unexpected return value (408 Request Timeout) in response to OPTIONS request for 'http://svn.observium.org/svn/observium/trunk'
I am looking for suggestions on troubleshooting this.
I have tried:
Making an outgoing rule on the firewall from my Observium server to http://svn.observium.org.
Opening outgoing (and therefore, returning) Ports: 80, 443, 21, 22, 8080, 3690
None of that has made a difference.
I can ping the svn server from my Observium machine, I can browse to the web page, my login credentials are correct..... 

ideas?

Joshua Bierman

observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium



observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium