6/24/2016 21:20:26 PM.300 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
6/24/2016 21:56:19 PM.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150
6/24/2016 21:56:28 PM.800 [NOTICE] Bootstrapped 5%: Connecting to directory server
6/24/2016 21:56:28 PM.800 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
6/24/2016 21:56:30 PM.400 [WARN] Proxy Client: unable to connect to IP-ADRESS:PORT ("general SOCKS server failure")
6/24/2016 22:44:07 PM.200 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
6/24/2016 22:44:07 PM.200 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
6/24/2016 22:44:07 PM.200 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
Asked
Active
Viewed 138 times
1
Jens Kubieziel
- 8,630
- 5
- 35
- 116
hmn
- 11
- 1
1 Answers
0
It seems that it's a very frequent bug in Tor Browser Bundle, check the messages DisableNetwork is set. It's pretty odd, but: Tor Browser sets DisableNetwork when it's not opened, so Tor instance seems to be intended to run only when the browser itself is active. Run the browser and don't close it - give it some time and send a full log if it will not work even that way. Also a pluggable transports and bridges can be of help to you
Alexey Vesnin
- 6,385
- 3
- 15
- 36