Opened 3 years ago

Last modified 3 years ago

#20769 needs_information defect

TB on Windows: Fails to connect to socks proxy

Reported by: mrphs Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I just had a report from an Iranian user that Tor Browser on Windows has stopped working for them. After seeing the logs, I asked them to download a fresh copy to make sure none of the files have been accidentally damaged. The problem still consists.

Here's the log file:

05/09/1395 23:49:49 ب.ظ.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
05/09/1395 23:49:49 ب.ظ.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
05/09/1395 23:49:49 ب.ظ.800 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
05/09/1395 23:49:49 ب.ظ.800 [NOTICE] Opening Socks listener on 127.0.0.1:9150 
05/09/1395 23:49:49 ب.ظ.800 [NOTICE] Renaming old configuration file to "C:\Users\xxx\Desktop\Tor Browser\Browser\TorBrowser\Data\Tor\torrc.orig.1" 
05/09/1395 23:49:57 ب.ظ.300 [NOTICE] Bootstrapped 5%: Connecting to directory server 
05/09/1395 23:50:18 ب.ظ.300 [WARN] The connection to the SOCKS5 proxy server at 127.0.0.1:50481 just failed. Make sure that the proxy server is up and running. 
05/09/1395 23:50:18 ب.ظ.300 [WARN] The connection to the SOCKS5 proxy server at 127.0.0.1:50481 just failed. Make sure that the proxy server is up and running. 
05/09/1395 23:50:18 ب.ظ.300 [WARN] The connection to the SOCKS5 proxy server at 127.0.0.1:50481 just failed. Make sure that the proxy server is up and running. 
05/09/1395 23:50:18 ب.ظ.300 [WARN] The connection to the SOCKS5 proxy server at 127.0.0.1:50481 just failed. Make sure that the proxy server is up and running. 
05/09/1395 23:50:18 ب.ظ.300 [WARN] The connection to the SOCKS5 proxy server at 127.0.0.1:50481 just failed. Make sure that the proxy server is up and running. 
05/09/1395 23:50:18 ب.ظ.300 [WARN] The connection to the SOCKS5 proxy server at 127.0.0.1:50481 just failed. Make sure that the proxy server is up and running. 
05/09/1395 23:50:18 ب.ظ.300 [WARN] The connection to the SOCKS5 proxy server at 127.0.0.1:50481 just failed. Make sure that the proxy server is up and running. 
05/09/1395 23:50:18 ب.ظ.300 [WARN] The connection to the SOCKS5 proxy server at 127.0.0.1:50481 just failed. Make sure that the proxy server is up and running. 
05/09/1395 23:50:18 ب.ظ.300 [WARN] The connection to the SOCKS5 proxy server at 127.0.0.1:50481 just failed. Make sure that the proxy server is up and running. 
05/09/1395 23:50:18 ب.ظ.300 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Connection timed out [WSAETIMEDOUT ]; TIMEOUT; count 10; recommendation warn; host 752CF7825B3B9EA6A98C83AC41F7099D67007EA5 at 198.245.60.50:443) 
05/09/1395 23:50:18 ب.ظ.300 [WARN] 9 connections have failed: 
05/09/1395 23:50:18 ب.ظ.300 [WARN] 9 connections died in state connect()ing with SSL state (No SSL object) 
05/09/1395 23:50:23 ب.ظ.100 [WARN] The connection to the SOCKS5 proxy server at 127.0.0.1:50481 just failed. Make sure that the proxy server is up and running. 
05/09/1395 23:50:23 ب.ظ.100 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Connection timed out [WSAETIMEDOUT ]; TIMEOUT; count 11; recommendation warn; host FE7840FE1E21FE0A0639ED176EDA00A3ECA1E34D at 154.35.22.13:443) 
05/09/1395 23:50:23 ب.ظ.100 [WARN] 10 connections have failed:
05/09/1395 23:50:23 ب.ظ.100 [WARN] 10 connections died in state connect()ing with SSL state (No SSL object) 
05/09/1395 23:50:23 ب.ظ.100 [WARN] The connection to the SOCKS5 proxy server at 127.0.0.1:50481 just failed. Make sure that the proxy server is up and running. 
05/09/1395 23:50:23 ب.ظ.100 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 
05/09/1395 23:50:23 ب.ظ.100 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
05/09/1395 23:50:23 ب.ظ.100 [NOTICE] Closing old Socks listener on 127.0.0.1:9150

Child Tickets

Change History (9)

comment:1 Changed 3 years ago by mrphs

Apparently this has happened only after upgrading to the latest version. I'm trying to confirm the version of Tor Browser and Windows. Might take a while for user to come back online.

comment:2 Changed 3 years ago by mcs

Status: newneeds_information

Are they using a local proxy to access the Internet? Is it working? Based on their log, it looks like tor is trying (and failing) to connect to a proxy at 127.0.0.1:5048. Or am I misinterpreting the log?

comment:3 Changed 3 years ago by mrphs

I just double checked, they seem to be on Windows 10 using Tor Browser 6.0.6.
And they just shared the screen shot of the Tor Browser Network Settings, confirming no local proxy is set.

comment:4 Changed 3 years ago by mrphs

It indeed seems to be some user mistake, though I can't point it out. It might be a general proxy setting applied by some other circumvention tool or proxy. Does Tor Browser honor a generally set proxy in Windows?

As a side note, this makes me think maybe we should have better error handling when Tor doesn't connect. Tor itself writes pretty good logs, but Tor Browser doesn't necessarily communicates them with user in a tangible way that general user can understand. I can think of an error like this popping up and while saying Tor was unable to connect, asks users if they've any other application or proxy setup that is intervening.

comment:5 in reply to:  4 Changed 3 years ago by mcs

Replying to mrphs:

It indeed seems to be some user mistake, though I can't point it out. It might be a general proxy setting applied by some other circumvention tool or proxy. Does Tor Browser honor a generally set proxy in Windows?

No, Tor Browser does not look at OS proxy settings (although doing so might make initial set up easier for some people).

As a side note, this makes me think maybe we should have better error handling when Tor doesn't connect. Tor itself writes pretty good logs, but Tor Browser doesn't necessarily communicates them with user in a tangible way that general user can understand. I can think of an error like this popping up and while saying Tor was unable to connect, asks users if they've any other application or proxy setup that is intervening.

I think interpreting the Tor log messages is something that would be hard to get right. But we should at least make it easier to see the errors and warnings. Related tickets: #9516, #9675, #12733.

comment:6 Changed 3 years ago by cypherpunks

This is about tor.exe connecting to pluggable transport. log_failed_proxy_connection() called for pt too:

If the connection we are about to close was trying to connect to a proxy server and failed, the client won't be able to use that proxy. We should warn the user about this.

Some of pt failed to start, listen, accept, or blocked to communicate with tor.exe. AV/Firewall?

comment:7 Changed 3 years ago by cypherpunks

Yet, some real tor bug here leading to interpreting log confusion.
log_failed_proxy_connection() should not to call get_proxy_addrport() as proxy type doesn't depends connection (with except to sock versions for pt, and you no need to know difference anyway). get_proxy_type() should be used instead as more informative function to log about proxy failure.

comment:8 Changed 3 years ago by cypherpunks

get_proxy_type() should be used instead as more informative function to log about proxy failure.

But proxy addr need to get anyway.

comment:9 Changed 3 years ago by cypherpunks

then to replace proxy_type_to_string(proxy_type) by proxy_type_to_string(get_proxy_type())

Note: See TracTickets for help on using tickets.