3

I'm going mad with this issue, that came out of all a sudden! Briefly, if I try to connect my svn server, I receive the following:

$ svn list svn://host
svn: E170013: Unable to connect to a repository at URL 'svn://host'
svn: E210005: No repository found in 'svn://host'

Of course svnserve is running on the default port (3690) and 

telnet host 3690

is regularly working.

No firewalls, server nor client-side.

svn projects and repos are regularly working locally.

jasmines
  • 11,011

6 Answers6

1

another thing to check:

I setup a new svnserve and was connecting for the first time, but I got an error:

svn: E170013: Unable to connect to a repository at URL 'svn://host/path'  
svn: E210005: No repository found in 'svn://host/path'

(aside normal client nmap -Pn host -p3690 being open, the server itself gave same error with svn list -v file:///path, where it should list at least a revision zero)

SO, for me, turned out to be a leading whitespace in my /path/conf/svnserve.conf (i.e. I only removed the pound sign, and left a single space before anon-access and auth-access); and sorry, I forget which command gave me the clue, but I got an error 

svn: E200002: line 20: Option expected

which was the anon-access line in svnserve.conf.

pomsky
  • 68,507
S Hunter Simpson
  • 11
  • 2
0

if you are behind a proxy, you need to configure proxy for svn. For this, edit the ~/.subversion/servers file by using nano or your preferred text editor and go to [global] paramters section. Uncomment these lines and replace by your proxy IP adress x.x.x.x and port yyyy:

http-proxy-host = x.x.x.x
http-proxy-port = yyyy

Save before closing, that should work immediately; don't leave any space between the begining of the line and http after uncommenting.

Betty
  • 101
0

There can be multiple things to check here.

  1. Can you check on server using svn list file://... your server is giving list of files ? - (This should work I think you already mentioned.)

  2. If the above command works then your local setup is correct but there is small thing that is missing here. Please check this link steps to setup svnserve using https:// or using svn://

  3. Please check whether your server daemon has started with -r option ? Without this client needs to provide the whole path for the access. svn://host.example.com/var/www/myrepo/project1 if the server is started with -r option then it should be svn://host.example.com/project1

  4. Check svn-director/conf/svnserv.conf file and see whether repository you would like to access has proper access for the user you are connecting from. This is required as without user access it might possible that repository is not readable. For reference of svnserv.conf this.

  5. Have you setup apache and can you access the repo with https://localhost.

For debugging please run the server daemon with --foreground to get logs and easy view.

Please let me know if still this doesn't work.

Harshit
  • 415
0

Edit your "servers" configuration file to indicate which proxy to use.

The file location is in "~/.subversion"

Uncomment and set the following lines:

#http-proxy-host=my.proxy
#http-proxy-port=80
#http-proxy-username=[username]
#http-proxy-password=[password]

I don't have your software so cannot test it myself but I hope this helps.

WinEunuuchs2Unix
  • 102,282
0

have you checked your svn version has not changed ?

you might have had a package manager update it in a batch of other changes.

Run this command to show the version and other details about the subversion package

apt-cache show subversion

There can be issues connecting to a 1.7 repository with a 1.9 client, if this where the case there would be messages in the server log and on stdout when the svn client is run.

Amias
  • 5,246
0

Check you proxy settings in TortoiseSVN->Settings->Network.

Maybe they are configured differently than in your web browser.

Or else try out,

Disable/uninstall the VPN software(if you are using it) in order to use the SVN repository.

Harshal Benake
  • 204
  • 1
  • 14