views:

509

answers:

5

I'm trying to setup my home server with a subversion repo on it (after some changes).

I uninstalled-reinstalled visualsvn server on the win2k3 server box and the address to the repo is https://server.network.local/svn/.

I can browse via IE to that address, and get the repository list (I do have to click past the certificate error though), but when I point tortoise to it as well, I get

OPTIONS of 'https://server.network.local/svn': Could not resolve hostname
'server.network.local': No such host is known.
(https://server.network.local)

I can ping and tracert to the server no problem though, so I'm not sure what the deal is.

+2  A: 

I had the same problem, as far as I can tell you can’t go straight to the SVN folder you need to include a repository file name in the path example:

https://server.network.local:8443/svn/MyNewRepository

Hope that helps

Anthony
seemed too simple, so I tried everything else first... my forehead hurts and my desk is ruined... but thanks :)
SnOrfus
NP, glad I could help. Cheers
Anthony
A: 

You might want to make your link 'https://server.network.local:8443/svn' and see if that makes a difference. I have that port on a tortise installation that I use.

Rick Strahl has a pretty good article on how to setup and run VisualSVN.

Hope this works for you.

Chris
ITYM https://server.network.local:8443/svn ... port generally goes after the server, not at end of URL :-)
Chris J
The article you refer to describes setting up subversion on the local machine. I've setup subversion on the server and it works fine (I can connect via tortoise on that machine). The problem is in connecting from other machines on the network.
SnOrfus
You might want to read this one also. http://www.west-wind.com/Weblog/posts/480534.aspx - Connecting to Subversion Source Control Repository over HTTP.
Chris
A: 

It's possible TSVN isn't happy with a bad SSL certificate, so you'll need to make it good (I assume it's self-signed, so you'll need to manually add the cert into the correct certificate store in Windows).

Before you go ahead and do this, what happens if you point TSVN to a non-secure version (i.e., http://) of the site? Is it happy then? If it is then it's definately pointing to SSL problems.

Chris J
+1  A: 

You have to clear your local DNS cache (and if you have a DNS on your LAN, you'll also have to do that with that DNS cache).

Stefan
A: 

Hmm. "Could not resolve hostname" is one layer below SSL, repositories and such. My bet is it's the (personal) firewall not letting Tortoise through.

Pekka