1

I'm trying to browse tor on my university wifi, but whenever I try to connect, it doesn't connect after a long time. I've used some bridges and it still can't connect.

Log: 1/31/2017 10:31:11 AM.200 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.

1/31/2017 10:31:11 AM.200 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.

1/31/2017 10:31:11 AM.200 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.

1/31/2017 10:31:11 AM.200 [NOTICE] Opening Socks listener on 127.0.0.1:9150

1/31/2017 10:31:17 AM.900 [NOTICE] Bootstrapped 5%: Connecting to directory server

1/31/2017 10:31:17 AM.900 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server

1/31/2017 10:31:38 AM.900 [WARN] Proxy Client: unable to connect to 192.73.235.50:56391 ("general SOCKS server failure")

1/31/2017 10:31:38 AM.900 [WARN] Proxy Client: unable to connect to 94.242.249.2:57860 ("general SOCKS server failure")

1/31/2017 10:31:38 AM.900 [WARN] Proxy Client: unable to connect to 194.132.208.239:28548 ("general SOCKS server failure")

  • 1
    Likely some kind of censorship. Try other bridges (obfs4 or meek), otherwise find some other method to tunnel Tor over that bypasses their censorship (iodine, ssh, vps, etc). – cacahuatl Feb 1 '17 at 1:52
  • @canonizingironize it seems that an upstream proxy uses by-ip allowed list, so pluggable transports may not help, but it's worth a try – Alexey Vesnin Feb 1 '17 at 17:20
  • You're just making stuff up again, Alexey. You have no evidence to support that claim. – cacahuatl Feb 1 '17 at 18:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.