I'm trying to setup my home server with a Subversion repo on it (after some changes).
I uninstalled-reinstalled VisualSVN Server on the Windows Server 2003 server box and the address (i.e. URL) 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.
TortoiseSVN comes with everything you need to access a repository. Only if you want to set up a server then you will need the Subversion package.
The default PORT address which SVN uses is 80 or 81 these are ports that sometimes cannot be reopened for security reasons.
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
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).
There is a note at the very bottom of the VisualSVN Server Getting Started guide and it answers the question. The note reads:
Unlike web browsers, Subversion clients are unable to access the content of the Repositories node in the VisualSVN Server Manager. In other words, you are unable to access https://svn.example.com/svn/ URL using Subversion clients such as TortoiseSVN or svn.exe.
I.e. Subversion client can access a repository but the URL https://server.network.local/svn/
points not to a repository, but to a repository root collection which you can view only with a web browser.
I also want to note that the error stated in the question can be different with newer Subversion clients. It can be:
XML parse error at line 1 no element found
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.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With