måndag 24 maj 2021 kl. 12:50:01 UTC+2 skrev [email protected]: > Hello everyone, I'm a novice in SVN configuration. > > Recently, I encountered a problem on the SVN server I built. When I used > the repo browser server of TortoiseSVN to access the SVN address, > TortoiseSVN hangs and it shows message like "please wait while the > repository browser is initializing" , and it could not be closed. I had to > close it in the task manager. > > The SVN server I built has two ports: 8080 and 8066. At first, I can > access both ports. One day, port 8066 can't be accessed, but port 8080 can > still be accessed, and both ports in the browser can be accessed. This > problem is also encountered by other colleagues in the company, but the > port they can access is 8066, and they cannot access 8080. > > I also checked the answers of other people on the Internet and thought > that it was related to the company's security software. However, after I > contacted my colleagues to shut down the security software, I still > couldn't access it. > > In addition, there is a strange phenomenon. When the security software has > been shut down, I shut down the network and adjust it to flight mode. The > previously accessible port 8080 reported an error running context: the > server unexpectedly closed the connection, but the port 8066 is still > suspended, which indicates that the error may occur before the request is > sent by tortoissvn.But why do different ports lead to different results? > > This problem has been bothering me for a long time. I can't find the > reason. Can someone help me find the reason? >
I would look for some kind of firewall or other network equipment eating part of the traffic (on your machine, on the server or somewhere inbetween). Can you install the command line tools (an option in the TortoiseSVN installer) and try svn ls [url of repository] My SVN server configuration: > Apache (2.2) > SVN (1.8.17), > my SVN client :1.14.1 > my win version: win10. > Are you aware that you are running a version of Subversion released 2016-11-29 (not even the latest 1.8) and a version of Apache httpd that has been EOL since 2018-01-01? Not that I would expect this to be a problem but in case it turns out to be a server problem you would get better help when running a supported version (1.10.7 or 1.14.1 being the latest Subversion releases, and ). Kind regards, Daniel Sahlberg -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/1b89a3b5-d2ae-48ef-a167-89eaacea3c41n%40googlegroups.com.
