2

I've managed to create SVN server that works on localhost (I used this tutorial).

Checkout and all other commands work locally (when I use the adress https://localhost/svn/repository-name)

I own a domain which points at my IP adress.

ping mydomain.com

returns my IP adress.

That IP adress leads to a router, which is configured to forward ports 80 and 443 to my server machine.

Unfortunatelly checkout https://mydomain.com/svn/repository-name is not working (Connection Timed out).

Why? Please help.

My server machine is running Apache2 @ Ubuntu 10.10.

Improve this question

3 Answers 3

Reset to default
2

Are you sure that your router forwards connections made on the internal interface back into the internal network? It is very common that cheap routers only do the port forwarding on traffic that comes in on the external interface.

Try testing from outside your network and see if it works better.

Improve this answer
11
2

You either have problems with the port forwarding (that is: the packets arriving at your router are not reaching your server) or 443 is closed in the interface you're forwarding the packets to.

Try https://ip.being.forwarded.to/svn/repository-name locally (that is, in the server) with the IP you configured on your router. Does it work that way?

Also check for INPUT filtering (iptables -nvL INPUT). And post netstat -ntlp if possible.

Improve this answer
5
  • https:// 192.168.0.109/svn/testPage/ returns my repository (just like https:// localhost/svn/testPage/)
    – loostro
    May 10, 2011 at 18:43
  • netstat -ntlp returns Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 6601/apache2 tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1113/cupsd tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 6601/apache2 tcp6 0 0 ::1:631 :::* LISTEN 1113/cupsd
    – loostro
    May 10, 2011 at 18:48
  • Can you test the same from some other server in the LAN? You can access it via a browser if you haven't got a SVN client handy. If it works then you know the issue is with the router/port forwarding.
    – Eduardo Ivanec
    May 10, 2011 at 18:49
  • iptables -nvL INPUT returns Chain INPUT (policy ACCEPT 30 packets, 4974 bytes) pkts bytes target prot opt in out source destination
    – loostro
    May 10, 2011 at 18:50
  • I've tested it from another machine (plugged into the same router/in the same Local Area Network) and it works
    – loostro
    May 10, 2011 at 18:52
2

The problem was closed ports.

Port forwarding options did not work on my router. I had to reset it to factory settings and set it up again. Now it works fine.

Why did my router fail to forward ports? No idea. But resetting router fixed the problem.

I'd like to thank @Eduardo and @pehrs for help!!

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .