1

it seems that there are some problems when i try to configure the Tor connectionS: the Bridges used in configuration are totally from "://bridges.torproject.org/bridges?transport=obfs4"; And before configuring, i've already try to Ping with those bridges, Ping is fine; But still i cannot finish the configuration, stuck at the step of "Establishing an encrypted directory connection", and could not move on; Below are the snapshots during the failure, please help to troubleshoot it。

stuck at this step;

ping is good; but got stuck at "Establishing an encrypted directory connection"

below are the Logs when try to configure Tor: *

2016/1/21 21:50:46.300 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
2016/1/21 21:50:46.300 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
2016/1/21 21:50:46.300 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
2016/1/21 21:50:46.300 [NOTICE] Opening Socks listener on 127.0.0.1:9150 
2016/1/21 21:50:52.700 [NOTICE] Bootstrapped 5%: Connecting to directory server 
2016/1/21 21:50:52.700 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server 
2016/1/21 21:51:13.700 [WARN] Proxy Client: unable to connect to xx.xx.xx.xx ("general SOCKS server failure") 
2016/1/21 21:51:13.700 [WARN] Proxy Client: unable to connect to xx.xx.xx.xx ("general SOCKS server failure") 
2016/1/21 22:06:13.700 [WARN] Proxy Client: unable to connect to xx.xx.xx.xx ("general SOCKS server failure") 
2016/1/21 22:06:13.700 [WARN] Proxy Client: unable to connect to xx.xx.xx.xx ("general SOCKS server failure") 
2016/1/21 22:09:47.600 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 
2016/1/21 22:09:47.600 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
2016/1/21 22:09:47.600 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
    *
Improve this question
1
  • 3
    Please don't post bridge addresses in public forums. It makes them that little bit easier for people who want to block them to find. (And defeats the point of having to request them, rather than just having them on a public wiki.)
    – Richard Horrocks
    Commented Jan 21, 2016 at 21:48

2 Answers 2

Reset to default
2

It seems that you may be a victim of TLS/HTTPS MitM-attack, try to use Meek and Obfs3/4 pluggable transports. If it won't work either - please post your Tor log here, so I'll be able to help you further. Stay tuned and never give up!

Improve this answer
8
  • @Mike anytime, m8! Have you solved your problem? Can I be of further help?
    – Alexey Vesnin ♦
    Commented Jan 22, 2016 at 18:27
  • it's great to have here as i m just a beginner using Tor browser; i tried the "Meek" connections, it worked fine; but now i have a new problem about "fte" & "flashproxy" connections; i tried the configuration according to the instructions from Tor blog; but i failed to get neither "fte" nor "flashproxy" connections; could u help to check? below are the logs of flashproxy failures:
    – Mike
    Commented Jan 24, 2016 at 3:25
  • @ Alexey Vesnin
    – Mike
    Commented Jan 24, 2016 at 3:33
  • Richard Horrocks
    – Mike
    Commented Jan 24, 2016 at 3:34
  • [NOTICE] Opening Socks listener on 127.0.0.1:9150 [NOTICE] Bootstrapped 5%: Connecting to directory server [NOTICE] Bootstrapped 10%: Finishing handshake with directory server [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server. (DONE; DONE; count 1; recommendation warn; host **********CD395A********* at 0.0.1.0:1) [WARN] 1 connections have failed: [WARN] 1 connections died in state handshaking (TLS) with SSL state SSLv2/v3 read server hello A in HANDSHAKE
    – Mike
    Commented Jan 24, 2016 at 3:37
1

I can't see any evidence of you being the victim of a MITM attack. It appears that your ISP is either blocking all traffic to known Tor entry nodes - which would imply they know that your bridges are part of the Tor network - or that they're blocking all Tor traffic by looking for Tor's traffic signature.

It might be worth requesting another set of bridges before looking at pluggable transports. If you do end needing pluggable transports, the recommendations are to try them in the order described in this official blog post. (It's a year old, but I believe the recommendation still holds true.)

You can presumably ping the bridges because your ISP isn't blocking ICMP traffic.

Improve this answer
1
  • thanks man, got a lot help from your links and caught much more information about Tor connections; yeah, what a great Idea of Tor system, full of joys!
    – Mike
    Commented Jan 22, 2016 at 4:01

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .