Thanks for your reply and ideas Uli, much appreciated. Responses interleaved.
Dave On Tue, Sep 6, 2011 at 4:14 AM, Ulrich Eckhardt wrote: > On Monday 05 September 2011, you wrote: >> I have local TSVN and Visual SVN Server installs that have been running >> fine for multiple years, running 1.6-something for a while. Hadn't done >> anything with them for some time, went to commit some changes yesterday, >> and Tortoise said "Unable to connect to repository at URL [..] Otions of >> [...] could not connect to server at [...]". No authentication prompt, >> 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. >> Connecting to my local subversion server with firefox prompted me for >> login, as it should, then worked fine. Tried connecting to >> http://svn.apache.org/repos/asf/spamassassin/trunk/, just to hit something >> besides my own server, again fine in firefox (no login prompt), same >> failure in TSVN. > > For HTTP, there are two things that could go wrong: > 1. A mandatory proxy > If Firefox uses a company-wide, mandatory proxy but SVN doesn't, that would > explain why you can't connect to the outside world with SVN. Try to check the > Firefox network settings if it is configured to use a proxy. > > 2. A proxy > Web browsers only use some HTTP requests, SVN uses a few more. If the proxy > isn't configured to let these through, you will have problems. However, in > such cases you usually get connected but the operations fail, while in your > 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. >> Tried using localhost and 127.0.0.1 urls instead of my machine name, >> username@repository_url, and explicitly specifiying :443 in the url, >> none of which I'd ever done before, no change, as expected, since the >> anonymous remote url didn't work either. > > Hmmm, port 443 is HTTPS, if I remember correctly. Also, where and how (Apache > or svnserve) are you serving a repository locally? Lastly, if you create a > repository locally and access it using "file://" URLs, does that work? Another > 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. >> Tried upgrading to the latest versions of TSVN and VisualSVN, which are >> 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. > Good luck! > > Uli > > > -- > ML: http://tortoisesvn.tigris.org/list_etiquette.html > FAQ: http://tortoisesvn.net/faq > > ************************************************************************************** > Domino Laser GmbH, Fangdieckstra�e 75a, 22547 Hamburg, Deutschland > Gesch�ftsf�hrer: Thorsten F�cking, Amtsgericht Hamburg HR B62 932 > ************************************************************************************** > Visit our website at http://www.dominolaser.com > ************************************************************************************** > Diese E-Mail einschlie�lich s�mtlicher Anh�nge ist nur f�r den Adressaten > bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen > Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empf�nger sein > sollten. Die E-Mail ist in diesem Fall zu l�schen und darf weder gelesen, > weitergeleitet, ver�ffentlicht oder anderweitig benutzt werden. > E-Mails k�nnen durch Dritte gelesen werden und Viren sowie nichtautorisierte > �nderungen enthalten. Domino Laser GmbH ist f�r diese Folgen nicht > verantwortlich. > ************************************************************************************** > > ------------------------------------------------------ > http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2835799 > > To unsubscribe from this discussion, e-mail: > [[email protected]]. >
