Opened 3 years ago

Last modified 3 years ago

#19957 new defect

Don't wait for Tor to start

Reported by: bugzilla Owned by: brade
Priority: Medium Milestone:
Component: Applications/Tor Launcher Version:
Severity: Normal Keywords: tbb-usability
Cc: mcs Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

If communication between firefox.exe and tor.exe was intercepted for some reason during start, then

The error message "Could not connect to Tor control port." is displayed after Tor Launcher (part of Tor Browser) fails to connect to the Tor control port for 30 seconds.

But it usually happens when security suite asks users for permissions for these applications. And often 30 sec are not enough to create rules. So, Tor Launcher needs an option to manually continue the startup process instead of showing "Waiting for Tor to start...".

Child Tickets

Attachments (1)

TorNetworkSettings.png (9.0 KB) - added by bugzilla 3 years ago.

Download all attachments as: .zip

Change History (6)

Changed 3 years ago by bugzilla

Attachment: TorNetworkSettings.png added

comment:1 Changed 3 years ago by bugzilla


No way to continue...

comment:2 Changed 3 years ago by bugzilla

Severity: NormalCritical

When switching from direct to obfs4proxy through Torbutton

[09-03 15:07:46] TorLauncher NOTE: Exception on control port [Exception... "Component returned failure code: 0x804b000e (NS_ERROR_NET_TIMEOUT) [nsIBinaryInputStream.readBytes]"  nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)"  location: "JS frame :: jar:file:///C:/Browser/TorBrowser/Data/Browser/profile.default/extensions/tor-launcher@torproject.org.xpi!/components/tl-protocol.js :: TorProtocolService.prototype._torReadLine :: line 716"  data: no]
[09-03 15:08:01] TorLauncher NOTE: failed to open authenticated connection: [Exception... "Component returned failure code: 0x804b000e (NS_ERROR_NET_TIMEOUT) [nsIBinaryInputStream.readBytes]"  nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)"  location: "JS frame :: jar:file:///C:/Browser/TorBrowser/Data/Browser/profile.default/extensions/tor-launcher@torproject.org.xpi!/components/tl-protocol.js :: TorProtocolService.prototype._torReadLine :: line 716"  data: no]
Tor NOTICE: Delaying directory fetches: No running bridges 
[09-03 15:08:25] TorLauncher NOTE: Tor unexpectedly exited. This might be due to a bug in Tor itself, another program on your system, or faulty hardware. Until you restart Tor, the Tor Browser will not able to reach any websites. If the problem persists, please send a copy of your Tor Log to the support team. Restarting Tor will not close your browser tabs.
[09-03 15:11:14] TorLauncher NOTE: failed to open authenticated connection: [Exception... "Component returned failure code: 0x804b000d (NS_ERROR_CONNECTION_REFUSED) [nsIBinaryOutputStream.writeBytes]"  nsresult: "0x804b000d (NS_ERROR_CONNECTION_REFUSED)"  location: "JS frame :: jar:file:///C:/Browser/TorBrowser/Data/Browser/profile.default/extensions/tor-launcher@torproject.org.xpi!/components/tl-protocol.js :: TorProtocolService.prototype._sendCommand :: line 685"  data: no]
[09-03 15:11:30] TorLauncher NOTE: failed to open authenticated connection: [Exception... "Component returned failure code: 0x804b000e (NS_ERROR_NET_TIMEOUT) [nsIBinaryInputStream.readBytes]"  nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)"  location: "JS frame :: jar:file:///C:/Browser/TorBrowser/Data/Browser/profile.default/extensions/tor-launcher@torproject.org.xpi!/components/tl-protocol.js :: TorProtocolService.prototype._torReadLine :: line 716"  data: no]
[09-03 15:11:42] TorLauncher NOTE: Could not connect to Tor control port.

Press OK, and no OK, just the above picture. Tor refuses connections, thus restart of TBB is required to get connectivity again.

comment:3 in reply to:  2 ; Changed 3 years ago by gk

Severity: CriticalNormal
Status: newneeds_information

Replying to bugzilla:

When switching from direct to obfs4proxy through Torbutton

[09-03 15:07:46] TorLauncher NOTE: Exception on control port [Exception... "Component returned failure code: 0x804b000e (NS_ERROR_NET_TIMEOUT) [nsIBinaryInputStream.readBytes]"  nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)"  location: "JS frame :: jar:file:///C:/Browser/TorBrowser/Data/Browser/profile.default/extensions/tor-launcher@torproject.org.xpi!/components/tl-protocol.js :: TorProtocolService.prototype._torReadLine :: line 716"  data: no]
[09-03 15:08:01] TorLauncher NOTE: failed to open authenticated connection: [Exception... "Component returned failure code: 0x804b000e (NS_ERROR_NET_TIMEOUT) [nsIBinaryInputStream.readBytes]"  nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)"  location: "JS frame :: jar:file:///C:/Browser/TorBrowser/Data/Browser/profile.default/extensions/tor-launcher@torproject.org.xpi!/components/tl-protocol.js :: TorProtocolService.prototype._torReadLine :: line 716"  data: no]
Tor NOTICE: Delaying directory fetches: No running bridges 
[09-03 15:08:25] TorLauncher NOTE: Tor unexpectedly exited. This might be due to a bug in Tor itself, another program on your system, or faulty hardware. Until you restart Tor, the Tor Browser will not able to reach any websites. If the problem persists, please send a copy of your Tor Log to the support team. Restarting Tor will not close your browser tabs.
[09-03 15:11:14] TorLauncher NOTE: failed to open authenticated connection: [Exception... "Component returned failure code: 0x804b000d (NS_ERROR_CONNECTION_REFUSED) [nsIBinaryOutputStream.writeBytes]"  nsresult: "0x804b000d (NS_ERROR_CONNECTION_REFUSED)"  location: "JS frame :: jar:file:///C:/Browser/TorBrowser/Data/Browser/profile.default/extensions/tor-launcher@torproject.org.xpi!/components/tl-protocol.js :: TorProtocolService.prototype._sendCommand :: line 685"  data: no]
[09-03 15:11:30] TorLauncher NOTE: failed to open authenticated connection: [Exception... "Component returned failure code: 0x804b000e (NS_ERROR_NET_TIMEOUT) [nsIBinaryInputStream.readBytes]"  nsresult: "0x804b000e (NS_ERROR_NET_TIMEOUT)"  location: "JS frame :: jar:file:///C:/Browser/TorBrowser/Data/Browser/profile.default/extensions/tor-launcher@torproject.org.xpi!/components/tl-protocol.js :: TorProtocolService.prototype._torReadLine :: line 716"  data: no]
[09-03 15:11:42] TorLauncher NOTE: Could not connect to Tor control port.

Press OK, and no OK, just the above picture. Tor refuses connections, thus restart of TBB is required to get connectivity again.

Works for me. How can I reproduce your problem?

comment:4 Changed 3 years ago by mcs

Cc: mcs added

comment:5 in reply to:  3 Changed 3 years ago by bugzilla

Status: needs_informationnew

Replying to gk:

Works for me. How can I reproduce your problem?

Win 7, extensions.torlauncher.loglevel was set to 3.

Note: See TracTickets for help on using tickets.