D
D
Dmitry Ivanov2018-12-16 20:18:51
Tor
Dmitry Ivanov, 2018-12-16 20:18:51

Can't connect to tor. What is the problem?

I make a separate exception rule for the torus in outgoing connections. (connecting current for a private network)
Tor is not connected. Here is the torus log:

12/16/18, 17:11:04.465 [WARN] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Permission denied [WSAEACCES ]; RESOURCELIMIT; count 10; recommendation warn; host 484A10BA2B8D48A5F0216674C8DD50EF27BC32F3 at 193.70.43.76:9001) 
12/16/18, 17:11:04.517 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 
12/16/18, 17:11:04.517 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
12/16/18, 17:11:04.517 [NOTICE] Closing old Socks listener on 127.0.0.1:9150

The first thing that catches your eye - the time is different from the system (client-windows). If I put the time on the system the same as in the logs ... then it changes even more. The very connection to the net is naturally worth it as home. Without this rule, everything works fine. i.e. I do everything the same as they do for vpn, when the vpn falls, so that the traffic is cut off. Here I am trying to do the same for the torus. It works on one computer (the same version of Windows) does not work on another computer. What is the reason?! When asked why this is necessary (I want to wrap Tor traffic in VPN in order to access white resources).

Answer the question

In order to leave comments, you need to log in

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question