Tortoise 无法连接到 subversion 服务器
我正在尝试在我的家庭服务器上设置 Subversion 存储库（经过一些更改后）。
我在 Windows Server 2003 服务器上卸载并重新安装了 VisualSVN Server，并且存储库的地址（即 URL）为 https://server.network.local/svn/。
我可以通过 IE 浏览到该地址，并获取存储库列表（尽管我确实必须单击过去的证书错误），但是当我也将 tortoise 指向它时，我发现
OPTIONS of 'https://server.network.local/svn': Could not resolve hostname
'server.network.local': No such host is known.
(https://server.network.local)
我可以 ping 和 Tracert 到服务器，但没有问题，所以我不确定这笔交易是什么。
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.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（8）
我遇到了同样的问题，据我所知，您无法直接进入 SVN 文件夹，您需要在路径示例中包含存储库文件名：
https://server.network.local:8443/svn/MyNewRepository
希望有帮助
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
您必须清除本地 DNS 缓存（如果您的 LAN 上有 DNS，则还必须对该 DNS 缓存执行此操作）。
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).
在 VisualSVN Server 入门指南的最底部有一个注释它回答了问题。注释中写道：
即 Subversion 客户端可以访问存储库，但 URL
https://server.network.local/svn/不是指向存储库，而是指向只能使用 Web 浏览器查看的存储库根集合。我还想指出，问题中指出的错误可能与较新的 Subversion 客户端不同。它可以是：
There is a note at the very bottom of the VisualSVN Server Getting Started guide and it answers the question. The note reads:
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:
您可能希望将链接设置为“https://server.network.local:8443/svn' 看看这是否有影响。我在我使用的乌龟安装上有这个端口。
Rick Strahl 有一篇关于如何设置和运行 VisualSVN 的好文章。
希望这对你有用。
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.
唔。 “无法解析主机名”是 SSL、存储库等下面的一层。我敢打赌，这是（个人）防火墙不允许乌龟通过。
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.
TSVN 可能对错误的 SSL 证书不满意，因此您需要将其修复（我假设它是自签名的，因此您需要手动将证书添加到 Windows 中正确的证书存储中）。
在继续执行此操作之前，如果您将 TSVN 指向该站点的非安全版本（即 http://）会发生什么情况？那还幸福吗？如果是，那么肯定是 SSL 问题。
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.
设置 SVN 的代理设置。只需右键单击 Tortoise SVN 并设置并添加代理设置。它可能对你有用。
Set the proxy setting of the SVN. Just right click and Tortoise SVN and setting and add the proxy setting. It may work for you.
这个问题与 DNS 服务器有关...
看看它是否给出这样的错误 https://server.xxx.com :435/svn
如果你用适当的ip（指svn服务器计算机的ip）替换server.xxx.com，
它就可以工作..
所以只需在正向查找区域中创建AAAA记录并在反向查找区域中创建PTR并问题解决了。
This issue is regarding DNS Server...
See if it gives error like this https://server.xxx.com:435/svn
if you replace server.xxx.com with the appropriate ip (mean ip of svn server computer)
it works..
so just make a AAAA record in forward lookup zone and make PTR in reverse lookup zone and problem is resolved.