Reputation: 8340
I'm on a network at a major bank and I'm trying to connect to a SVN repository from my Windows 7 machine. I'm using the latest version of Tortoise (as of yesterday) 64 bit client.
When I try and connect using repo-browser, I am able to log in with my credentials, but I then get the error, "No connection could be made because the target machine actively refused it."
Other people in my network are able to connect to the repository. Someone else out out of the network was able to log on to the repository using my credentials. I also tried to use superuser credentials to log on and got the same error.
I disabled my virus protection software and still got the same results.
I tried accessing from the command line and still got the same results.
I'm sure it's the way my machine or my network is configured, but I am not a network person, so I don't know how to troubleshoot this issue.
Upvotes: 5
Views: 24479
Reputation: 3339
If you are using Redmine, your URL for the repository is wrong. You will need to use the URL that can be found in the Project in Settings->Repositories. Here is the screenshot:
Upvotes: 1
Reputation: 3
this fixed with relocating to the right branch
TortiseSVN >>relocate then put ur correct URL
Upvotes: -1
Reputation: 471
In my case when you copy URL from server repository it contains localhost path.
something like http://xxxx-xxx-xx-xx:portnumber/svn/MyRepository/
if you install SVN on server and try above path then it will show the required output, i.e. folder structure of your repository.
But when you try to access it form remote computer you need to replace all the things after http://
and before port number colon by your sever IP.
It will look like http://myserverip:myport/svn/MyRepository/
Also check windows firewall port is opened or not which you are accessing.
Upvotes: 0
Reputation: 21
Check The proxy definitions in the servers file located at C:\Users\XXX\AppData\Roaming\Subversion
.
I removed the Proxy lines:
ssl-trust-default-ca = no
http-proxy-host =
http-proxy-username =
http-proxy-password =
And it works!
Upvotes: 2
Reputation: 116
I know this question is old, but something for people to consider as well; make sure that whatever webserver you are running is actually running. That may sound obvious, but I was using VisualSVN (which basically has its own Apache webserver built in) and it had stopped the service after a reboot. Check this first before messing about with proxy settings.
Upvotes: 2
Reputation: 8340
It was a proxy issue. I entered in the right proxy information and voila! I was granted access.
Upvotes: 4