Opened 2 years ago

Closed 2 years ago

#16281 closed defect (fixed)

Updating to 4.5.1 sets DisableNetwork

Reported by: saint Owned by: tbb-team
Priority: Low Milestone:
Component: Applications/Tor Browser Version:
Severity: Keywords: meek, tbb
Cc: brade, mcs, dcf Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by saint)

Not sure if this is intentional or not, so posting a report. I'd had meek enabled before the update, and after the update couldn't get Tor Browser to connect to the internet. The fix was to change TBB settings to no longer use a pluggable transport.

Here's the log:

06/03/2015 06:14:03.485 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
06/03/2015 06:14:03.485 [NOTICE] Opening Socks listener on 127.0.0.1:9150 
06/03/2015 06:14:16.441 [WARN] The communication stream of managed proxy './TorBrowser/Tor/PluggableTransports/meek-client-torbrowser' is 'closed'. Most probably the managed proxy stopped running. This might be a bug of the managed proxy, a bug of Tor, or a misconfiguration. Please enable logging on your managed proxy and check the logs for errors. 
06/03/2015 06:14:16.441 [NOTICE] Failed to terminate process with PID '14392' ('No child processes'). 
06/03/2015 06:14:17.242 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150 
06/03/2015 06:14:17.242 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 
06/03/2015 06:14:17.242 [NOTICE] Closing old Socks listener on 127.0.0.1:9150 

Ubuntu 14.04 x64

Child Tickets

Change History (4)

comment:1 Changed 2 years ago by saint

Description: modified (diff)

comment:2 Changed 2 years ago by mcs

Cc: brade mcs dcf added
Status: newneeds_information

If Tor Browser is configured to use one of the bundled PT options, Tor Launcher sets DisableNetwork at startup, sets the PT configuration via the control port, and then enables networking... so it is normal to see some occurrences of "DisableNetwork is set" in the Tor log.

Is it possible that this is a duplicate of #13247? Because of that bug, if meek is enabled, a second restart of the browser is required to get everything working again.

comment:3 Changed 2 years ago by dcf

Is this still happening, saint? The likely cause, #13247, has been fixed.

comment:4 Changed 2 years ago by saint

Resolution: fixed
Status: needs_informationclosed

I haven't noticed it happening with 5.01, so closing.

Note: See TracTickets for help on using tickets.