SVN Unable to connect to host

We have set up the SVN repository on the remote host server. We have a completely new Dev server, which I will eventually configure our repository there, but for now I'm trying to export the project to the dev server from SVN. When I try to do this, I get svn: I can not connect to the host "website.com": connection timeout.

I can connect perfectly from any other server, so I assume that it should be something on the dev server, I'm just not sure which parameter can block this. I can ping the server, and it returns with the results, I thought that since it was a local network server, maybe something was blocking access to the external network.

I'm just looking for a few ideas as to what this might be.

+4
source share
4 answers

I just solve it using the commands below: when starting the svn service, add the "--listen-host 0.0.0.0" part to your command, for example:

svnserve -d --listen-port 9803 --listen-host 0.0.0.0 -r / somewhere / somewhere

This is because, unless explicitly stated, svnserve will listen on IPv6 connections that support IPv6, which is true for Windows Vista, 7, and Server 2008, possibly FreeBSD.

My server has FreeBSD os, I met this problem this morning and solved it now.

You can refer to this page: Additional information

+8
source

This may seem low, but double check if you are using a protocol to connect to the server for (svn: // for svn, http: // for http, ssh + svn: // for svn over ssh) and double check the firewall settings .

SVN uses port 3690 if you connect using the SVN protocol (default for new settings), (obviously) port 80 for HTTP, and (again obviously) port 22 for SSH.

+2
source

If you can telnet ip and port, make sure

  • set the host to listen on 0.0.0.0;
  • use url svn: // domain: port / to connect the server
+2
source

In my case, the problem is that I used svn 1.7.x , and this version causes this error when trying to use from the command line.

I'm just trying with svn 1.8.x and everything works fine, I can finally interact via the command line without any problems.

If someone else runs into this problem, maybe this can help.

Hi,

ps I am on Linux Centos 6.5.

+1
source

Source: https://habr.com/ru/post/1312552/


All Articles