Closed Bug 1195520 Opened 9 years ago Closed 9 years ago

Error creating socket.

Categories

(Other Applications :: ChatZilla, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1214786

People

(Reporter: UberSlackr, Assigned: rginda)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.155 Safari/537.36

Steps to reproduce:

Attempted to Connect to local hosted bouncer/znc


Actual results:

Error creating socket.


Expected results:

Connection to Bouncer/ZNC opened
Chatzilla 0.9.92 > Worked as expected before recent update.
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Can you please provide the full error message?

Did it ever work on Windows 10? Have you checked that this isn't a firewall blocking chatzilla after an application update?
Flags: needinfo?(UberSlackr)
Yes, it has worked on Windows 10.
Yes, it fails both when windows firewall is on and when windows firewall is off.
The full error message appears in the ChatZilla window:

[INFO]	Attempting to connect to "irc.tmro.tv".  Use /cancel to abort.
[INFO]	Connecting to irc://irc.tmro.tv/ (irc://irc.tmro.tv/)... [Cancel]
[ERROR]	Error creating socket.

Running Firefox 42.0b9, Chatzilla 0.9.92
This is a regression from 42b8 to 42b9 according to reports on IRC; the error is this unhelpful thing:

Exception opening socket: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIProtocolProxyService.asyncResolve]"  nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame :: chrome://chatzilla/content/lib/js/connection-xpcom.js :: bc_connect :: line 277"  data: no]

I'm currently looking in to the source/changelog bug help appreciated in suggested causes.
Severity: normal → critical
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 10 → All
Hardware: x86_64 → All
Version: unspecified → Trunk
A workaround for now is to set the global or network preference "proxy.typeOverride" to "none" (or "http" surprisingly):

  /pref proxy.typeOverride none

To undo this change:

  /pref proxy.typeOverride -

If you've had the "Error creating socket" error message, a restart of ChatZilla is needed in addition to the preference change because the error puts things in to a confused state. After that it should work, though.
Flags: needinfo?(UberSlackr)
Bug 1214122 looks like the most likely cause.
Blocks: 1214122
This is weird, because it's not broken on current Nightly, which is making this hard to debug.

(In reply to James Ross from comment #6)
> Bug 1214122 looks like the most likely cause.

This might also mean that bug 1214786 has already fixed this. Checking.
(In reply to :Gijs Kruitbosch (at OSCON, limited availability) from comment #7)
> This is weird, because it's not broken on current Nightly, which is making
> this hard to debug.
> 
> (In reply to James Ross from comment #6)
> > Bug 1214122 looks like the most likely cause.
> 
> This might also mean that bug 1214786 has already fixed this. Checking.

This does indeed appear to be fixed on latest builds (which would mean that the RC and release should work as expected). James, can you doublecheck my verification on Windows? (I tested on mac)

I grabbed a build off https://treeherder.mozilla.org/#/jobs?repo=mozilla-beta -- rc builds should also be available if you update on the beta channel, or you can manually download from https://archive.mozilla.org/pub/firefox/candidates/42.0-candidates/build1/ .
Flags: needinfo?(bugzilla-mozilla-20000923)
Bug 1214122 quickly fixed a potential crash(addon could cause Firefox to crash) and bug 1214786 was a follow up to make addon work again (but bug 1214786 did not make it into ff42 :( )
(In reply to Dragana Damjanovic [:dragana] from comment #9)
> Bug 1214122 quickly fixed a potential crash(addon could cause Firefox to
> crash) and bug 1214786 was a follow up to make addon work again (but bug
> 1214786 did not make it into ff42 :( )

It did, it's just not in b9 - it made the rc, see bug 1214786 comment 24 and bug 1214786 comment 25.
I am pretty sure it's fixed by bug 1214786 but haven't tested a newer build yet. If you've got the error in b9 but had it work in b8 and rc, feel free to close/dup this bug as that resolves the issue AFAICS.
Flags: needinfo?(bugzilla-mozilla-20000923)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.