----- Reply message ----- From: [email protected] To: "Digest Recipients" <[email protected]> Subject: Digest for [email protected] - 3 Messages in 1 Topic Date: Tue, Sep 6, 2011 10:38 pm Today's Topic Summary Group: http://groups.google.com/group/tortoisesvn/topics
Unable to connect with TSVN, locally or remotely, can connect with a web browser [3 Updates] Topic: Unable to connect with TSVN, locally or remotely, can connect with a web browser Dave Merrill <[email protected]> Sep 06 08:45AM -0400 ^ Thanks for your reply and ideas Uli, much appreciated. Responses interleaved. Dave On Tue, Sep 6, 2011 at 4:14 AM, Ulrich Eckhardt wrote: >> just that msg. > First thing to make sure is to check whether it is TSVN only or also the > vanilla SVN commandline. Could you verify that? This works fine from the cmd line: svn --version I can't verify any further than that right now, but it does seem that I can connect to it. > case you don't even seem to be able to make a connection. Note that if you are > using HTTPS, I think the proxy couldn't even snoop on your connection so that > would be another thing to try. These tests were done on my personal laptop at home, ISP is Verizon FIOS. There's no proxy anywhere on my machine. Don't think there's one at the ISP either, or at least if there is, it's transparent to me in every respect I'm aware of. This has never been an issue before, in the years I've been on FIOS. > thing to try is to just use telnet to connect to the according server and > port, if that fails to establish a connection, you have a pure networking > problem, probably caused by the [lack of] proxy settings. I'm using VisualSVN Server (http://www.visualsvn.com/server/), which installs and manages subversion servers. It uses standard subversion and apache. I am using https, standard port, which is 443 as you thought. I'm unable to browse my repository at file://c:/path/to/my/repository/ either, implying that it's something more fundamental, not an http failure. >> both up to 1.7 at this point, same results with local and remote servers. > Wait: You are aware that 1.7 has not been released yet, right? What you have > therefore is either a time machine or a pre-release version. I'm aware this TSVN version is a release candidate, but given the very confident msg on the TSVN home page, and the statement that it should be backwards compatible with earlier server releases, I thought it made sense to go ahead with it. Quote from the compatibility secion of the release notes: "Older clients and servers interoperate transparently with 1.7 servers and clients." I was incorrect about the svn version in Visual SVN, it's actually 1.6.17. Am I wrong about TSVN 1.7rc's compatibility with a 1.6 server? If so, that would explain both the local and remote failures, but the above statement seems to say that a problem in that area would be a bug. The RC version says that working copies need to be upgraded, but doesn't say that repositories do, or that un-upgraded ones can't be browsed from this version. I wonder if that's the issue. Dave Merrill <[email protected]> Sep 06 09:36AM -0400 ^ Actually, re TSVN versions, we may be losing site of the big picture. The reason I installed 1.7rc was that tortoise wasn't working in the first place. It's possible I shouldn't have gone to 1.7, and that that's causing some new issue(s), but something had stopped working before that. Dave Dave Merrill <[email protected]> Sep 06 09:39PM -0400 ^ So, I hate to whine, but I'm still stuck. - Am I correct that TSVN 1.7 *should* connect to 1.6 servers or repositories? - Is anyone aware of major problems in that area? - Where might I find logs or other info about what went wrong, other than the system event log, which doesn't show anything useful? - Any other theories of what might prevent TSVN from connecting to a *local* repository, at both html and file urls, given the things I mentioned trying in my earlier msg? Thanks very much for any assistance, Dave
