Opened 8 years ago

Closed 4 years ago

#6577 closed defect (invalid)

WebSockets seem totally broken by Firefox SOCKS settings

Reported by: mikeperry Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-usability-website, tbb-bounty, tbb-firefox-patch
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description is failing on both TBB 2.2.x and 2.3.x. I also tested a Vanilla FF14 with SOCKS proxy settings, and the socket also breaks there, too.

This is thus probably an upstream Firefox bug. We should at least file a bugzilla bug and bring it to someone's attention, I guess.

Child Tickets

Change History (6)

comment:1 Changed 8 years ago by mikeperry

Keywords: tbb-usability-website added

comment:2 Changed 8 years ago by mikeperry

Keywords: tbb-bounty added

comment:3 Changed 8 years ago by mcs

I cannot get to work in vanilla Firefox 17 even without SOCKS (it does work in Chrome 16). The demo at does work in Firefox 17 both with and without SOCKS configured.

comment:4 Changed 6 years ago by erinn

Keywords: tbb-firefox-patch added

comment:5 Changed 6 years ago by erinn

Component: Firefox Patch IssuesTor Browser
Owner: changed from mikeperry to tbb-team

comment:6 Changed 4 years ago by bugzilla

Resolution: invalid
Severity: Normal
Status: newclosed

Replying to mikeperry (from ticket:5292):

Application Error (Test is dead)


This error appears in the FF error console:

Error: Firefox can't establish a connection to the server at ws://
Source File:
Line: 54

This error appears for those webpages which use swf (Adobe Flash) instead of JS for WebSocket, and it's quite confusing, yeah.
Or when JS is used by ;)

Torbutton INFO: tor SOCKS: via
Firefox can't establish a connection to the server at wss:// qui-0cc18125cbfe7c291eca.js:8132:15
The connection to wss:// was interrupted while the page was loading. qui-0cc18125cbfe7c291eca.js:8132:15
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIInterfaceRequestor.getInterface] network-monitor.js:84:0

Or by

Firefox can't establish a connection to the server at wss:// 7e8aa475d2075bbe5de6d8cac1f43c6b5ce296a1.js:53:17714

Nevertheless, is everything you need for testing.
Maybe, there are some issues with WebSocket for separate tickets, but according to the Summary and the Description this ticket can be closed.

Note: See TracTickets for help on using tickets.