1

The day before I got a serious problem communicating with Tor.

Tor Bootstrap Result: Whonix-check gave up waiting after 60 seconds. Bootstrapping 85% done.

Tor reports: WARN BOOTSRAP PROGRESS=85 TAG= handshake_or SUMMARY="Finishing handshake with first hop “WARNING="Connection timed out" REASON=TIMEOUT COUNT=75 RECOMMENDATION=warn

enter image description here

First of all I checked the Tor on host and Tor working well, but before ruining showed me this :

    7/29/2014 7:33:11 AM.587 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
7/29/2014 7:33:11 AM.587 [NOTICE] Pluggable transport proxy (fte exec Tor\PluggableTransports\fteproxy --managed) does not provide any needed transports and will not be launched. 
7/29/2014 7:33:11 AM.587 [NOTICE] Pluggable transport proxy (flashproxy exec Tor\PluggableTransports\flashproxy-client --register :0 :9000) does not provide any needed transports and will not be launched. 
7/29/2014 7:33:11 AM.587 [NOTICE] Opening Socks listener on 127.0.0.1:9150 
7/29/2014 7:33:11 AM.587 [NOTICE] Pluggable transport proxy (fte exec Tor\PluggableTransports\fteproxy --managed) does not provide any needed transports and will not be launched. 
7/29/2014 7:33:11 AM.587 [NOTICE] Pluggable transport proxy (flashproxy exec Tor\PluggableTransports\flashproxy-client --register :0 :9000) does not provide any needed transports and will not be launched. 
7/29/2014 7:33:11 AM.615 [NOTICE] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again. 
7/29/2014 7:33:13 AM.771 [NOTICE] Bootstrapped 5%: Connecting to directory server. 
7/29/2014 7:33:13 AM.778 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server. 
7/29/2014 7:33:15 AM.375 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection. 
7/29/2014 7:33:15 AM.803 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus. 
7/29/2014 7:33:16 AM.100 [NOTICE] Bootstrapped 50%: Loading relay descriptors. 
7/29/2014 7:33:35 AM.159 [WARN] Proxy Client: unable to connect to 208.79.90.242:35658 ("TTL expired") 

But after awhile Tor is connecting and Tor browser normally opens. However, I Still have problem connecting on Whonix OS.

closed as unclear what you're asking by Jens Kubieziel Aug 25 '15 at 18:24

Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • Dear, do you use bridges or pluggable transport bridges? – Roya Jul 29 '14 at 4:49
  • I just used Whonix by default, I didn't nothing changed and about Tor on host (windows7) too nothing changed on it. – Photon Jul 29 '14 at 6:50
  • Why are you running Tor on the host? That's not necessary for running Whonix. And it may be the source of your problem. I don't have a Windows box to test on, and I don't remember how VirtualBox handles Tor running on the host. Anyway, see if Whonix works when Tor is NOT running on the host. – mirimir Jul 29 '14 at 15:58
  • Yes I know it's not required to use Tor on host (windows7) for ruining whonix on VB. I am using to make sure it works. Until a few days ago, Whonix OS worked well. My main problem with this is that the Whonix OS is not connected to Tor any more. – Photon Jul 29 '14 at 17:02
  • I just tested on Whonix OS without Tor running on host, but it still does not work... – Photon Jul 29 '14 at 17:16

Browse other questions tagged or ask your own question.