'TortoiseSVN unable to connect to VisualSVN
Until last week we were normally able to connect to our VisualSVN server using Tortoise.
Yesterday it's not working anymore. Any attempt to connect results in error with message Error running context: nenhuma conexão pôde ser feita porque a máquina de destino as recusou ativamente. Yes, this portuga message means nothing and there are very few webpages talking about it.
Connection is made using HTTPS, I tried HTTP and SVN with no luck. I also tried to connect locally on the server, and strangely Tortoise hangs for some minutes and recovers reporting Connection timed out.
I tried restarting VisualSVN service. ALAIK firewall wasn't changed.
Strangely, if I use the same HTTPS URL on FireFox, it's answered and repository is shown as webpages!
Any idea on what may be causing this?
Update: I used PortQry to connect to server using port 443, and it reported the port is listening. This means it's not a firewall issue and confirms FireFox being able to connect to VisualSVN. So, it's something related to TortoiseSVN.
Update 2: I tried command line svn update on my PC and got the same error message. Used the same command locally on the server, and it worked! This is getting strange.
Resuming: on my PC, both GUI and command line fail, but FireFox and PortQry work. Local on the server, command line works and GUI fails.
Solution 1:[1]
The error can be translated to:
no connection could be made because the target machine actively refused it
In most cases the error indicates that you attempt connecting on incorrect port number or on HTTP port using HTTPS or vice verse. However, the error could also indicate invalid proxy settings configured for the Subversion client. Check the proxy settings in TortoiseSVN.
Solution 2:[2]
The permissions and port did not work for me. I did a repair of the Visual SVN installation, by going into the control panel,
right click on Visual SVN > Repair Took 2 minutes but it got the thing to work.
it was easier since it was a single server instance.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | bahrep |
| Solution 2 |