Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've got a Fedora server running Subversion and svnserve on port 3690. My repo is at /var/svn/project_name. I have my router forwarding port 3690 to the local server (as well as port 80, 21, 22 and a few others). When I connect locally to svn://192.168.0.2/project_name it works great. When I connect from an external server to svn://my.static.ip/project_name I get a time out connecting to the host. However, if I http://my.static.ip there is no problem, so port forwarding is working (at least for port 80).

I don't want to run WebDAV or svn via HTTP/s. I'd like it to work using svnserve, as documented in the svn book. What have I misconfigured?

EDIT Here is the last part of my iptables dump. I'm not an expert, but it looks OK to me:

ACCEPT     tcp  --  anywhere             anywhere            state NEW tcp dpt:svn
ACCEPT     udp  --  anywhere             anywhere            state NEW udp dpt:svn
ACCEPT     tcp  --  anywhere             anywhere            state NEW tcp dpts:6680:6699
ACCEPT     udp  --  anywhere             anywhere            state NEW udp dpts:6680:6699
REJECT     all  --  anywhere             anywhere            reject-with icmp-host-prohibited

EDIT 2 Results from sudo netstat -tulpn

tcp        0      0 0.0.0.0:3690                0.0.0.0:*                   LISTEN      1455/svnserve
share|improve this question
3  
Are you sure you want to use svnserve over the internet? Everything about the connection including authentication data is sent in clear text. –  Shane Madden Jul 9 '12 at 16:28
    
Yes, quite sure. –  Tom Auger Jul 9 '12 at 17:41
    
Alright. When you say access is working locally, do you mean from the server itself or another system on the local network? Any iptables rules set up on the server? What's it look like when you scan your external IP - is 22 connecting, or just 80? –  Shane Madden Jul 9 '12 at 18:01
    
How about taking a tcpdump while checking out your project outside your local network? It will narrow the problem and reduce the amount of guessing. –  vtorhonen Jul 9 '12 at 18:04
2  
Tom, see here: queens.db.toronto.edu/~nilesh/linux/subversion-howto I'm not the expert though. I just know others here setup ours and we simply use svn+ssh:// to get to ours. It looks like there are tons of serverfault questions on SVN over SSH. –  TheCleaner Jul 11 '12 at 14:23
show 8 more comments

1 Answer

up vote 0 down vote accepted

In this case, it was the server itself (service provider: Bluehost.com) that is blocking port 3690 on their end. The solution was either to pay an additional $$ to have a static IP set up and then they could open that port, or to simply use svn+ssh to access, since SSH port 22 is already open.

Hope this is at least useful to anyone else experiencing this kind of issue from a shared hosting environment.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.