SVN Could not read status line error on checkout

Question

I used to be able to check out/in from our SVN repository at work. Then I did a clean install of OS X 10.8 due to some issues. Everything else is great but now I can't check out or update. No one else here is experiencing problems.

Here's the error I'm getting:

svn: OPTIONS of 'http://subversion.myhost.com/svn/repository/trunk': Could not read status line: connection was closed by server (http://subversion.myhost.com)

I've done a lot of googling over the last couple of days but nothing I found was helpful. The most informative page is here: SVN: Could not read status line: connection was closed by server

Stuff I've tried:

• changing http -> https -> svn (connections to https/svn are refused)
• checking for proxy/firewall blocking (couldn't find any--but perhaps there's something I missed?)
• loading the repository from the web interface (can browse it just fine, but still can't check out)
• updating subversion (was using svn from Xcode 4.5) then installed svn (1.6.18) via macports (still getting same error)
• wiped my subversion preferences in ~/.subversion
• double/triple/quad+ checked the URL (same every time)
• checking out stuff from a completely different repository off-site (got the same error)
• drinking lots of Mountain Dew and hoping for inspiration (getting jittery but nothing else has changed)

Anyone have other ideas?

Answer 1

I found a workable solution for using the SVN client with Cisco Any Connect client 3.1.x for Apple Mac OS X 10.9.x.

In summary, uninstall the Cisco Any Connect web security module.

Issue and solution summary posted at

Super User - SVN Error when connecting from MacBook

https://superuser.com/a/704711

and at

Super User - SVN Connection Not Successful

https://superuser.com/a/579485

• Tim

Answer 2

What if the repository is behind a firewall and you need the VPN client to connect?

Answer 3

I've experienced same issue but we are using Juniper VPN. Shutting down all VPN processes helped to resolve it.

Answer 4

I just got burned by this too; thanks for pointing me in the direction of the culprit (the damned VPN client). I note that it does this fuckery even with the VPN connection disabled, lest you think that you can stop it from screwing with your network stack by asking nicely!

Where did you discover it was the client? I am going to have to fight this one out with my IT team so was curious what other information was out there.