Closed Bug 1468870 Opened 2 years ago Closed 11 months ago

WhatsApp Web broken in Firefox all of a sudden, with "Firefox can’t establish a connection to the server at wss://w7.web.whatsapp.com/ws" (and I can't access that domain via HTTPS in Firefox either, but can in Chrome)

Categories

(Core :: Networking, defect)

defect
Not set

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
firefox62 --- affected

People

(Reporter: dholbert, Unassigned)

Details

(Keywords: top100)

STR:
 1. Visit https://web.whatsapp.com

EXPECTED RESULTS:
QR Code should be displayed.

ACTUAL RESULTS:
WhatsApp's throbber spins forever instead of QR Code.  Additionally, I see this in Browser Console:

===============
Content Security Policy: Directive ‘child-src’ has been deprecated. Please use directive ‘worker-src’ to control workers, or directive ‘frame-src’ to control frames respectively.

Firefox can’t establish a connection to the server at wss://w7.web.whatsapp.com/ws. app.d84936ac910dd008587a.js:20:21586

Firefox can’t establish a connection to the server at wss://w8.web.whatsapp.com/ws. app.d84936ac910dd008587a.js:20:21586 
===============



I'm using Ubuntu 18.04 -- I tested current Nightly and current release (60.0.2), using a fresh profile.  Both give "Actual Results" (broken).

Chrome gives me "Expected Results" on the same machine.

NOTE: This was working as of a few days ago I think, so I suspect this regressed for us when WhatsApp changed something on their end.
I tried Firefox on Windows and Mac via browserstack.com, and I couldn't reproduce the issue there. (The QR code does load -- hooray! -- and I don't see any "Firefox can’t establish a connection to the server" errors in Browser Console).

So there might be something Linux-specific here.  (though again, I'm testing in a fresh browser profile & it does work in Chrome from the same desktop session)
I tried rebooting, and the issue persisted - still "Actual Results" (testing with a fresh browser profile).

(But on Windows on the same machine, I get Expected Results.)

(Not sure whether to blame an Ubuntu system package update, or a change on WhatsApp's end that happens to have linux-specific fallout, or what)
Additional data point: kamidphish gets "ACTUAL RESULTS" in Firefox within his Arch Linux environment.
It looks like Firefox on my linux environment is simply unable to connect to w7.web.whatsapp.com (and similarly dyn.web.whatsapp.com).  E.g. these URLs trigger "Hmm. We’re having trouble finding that site.":
 https://dyn.web.whatsapp.com/
 https://w7.web.whatsapp.com/
 https://w8.web.whatsapp.com/
...but load just fine in Chrome.

So my working theory is that the local DNS server (on the Mozilla_All_Hands network) is horked (but in a way that only affects Firefox, and only for these web.whatsapp.com subdomains).

Incidentally, if I enable DNS over HTTPS, then that fixes it for me! :D
https://blog.nightly.mozilla.org/2018/06/01/improving-dns-privacy-in-firefox/
Component: DOM: Service Workers → Networking
Summary: WhatsApp Web broken in Firefox all of a sudden, with "Firefox can’t establish a connection to the server at wss://w7.web.whatsapp.com/ws" → WhatsApp Web broken in Firefox all of a sudden, with "Firefox can’t establish a connection to the server at wss://w7.web.whatsapp.com/ws" (and I can't access that domain has HTTPS in Firefox either, but can in Chrome)
Summary: WhatsApp Web broken in Firefox all of a sudden, with "Firefox can’t establish a connection to the server at wss://w7.web.whatsapp.com/ws" (and I can't access that domain has HTTPS in Firefox either, but can in Chrome) → WhatsApp Web broken in Firefox all of a sudden, with "Firefox can’t establish a connection to the server at wss://w7.web.whatsapp.com/ws" (and I can't access that domain via HTTPS in Firefox either, but can in Chrome)
FWIW, "curl" and "ping" both fail to resolve dyn.web.whatsapp.com in the same linux environment.  So this isn't entirely linux-specific -- but Chrome somehow isn't affected by the problem.
This is WORKSFORME now (upstairs, on the Marriott_GUEST network).

Given that ping & curl were both affected (and now work fine as well), I suspect this was a misconfiguration on the DNS server that I was connected to (and/or how linux interacted with it, since it was fine when I rebooted in windows).  So, not a Firefox bug really.

I'm still curious on why it worked in Chrome... I suspect Chrome was perhaps working around it by secretly using their own DNS server under the hood or as a fallback or something like that. *shrug*
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
I'm having the same problem.

Firefox can’t establish a connection to the server at wss://w8.web.whatsapp.com/ws. app.12174fa72d7f41b3bf19.js:20:29397
Firefox can’t establish a connection to the server at wss://w1.web.whatsapp.com/ws. app.12174fa72d7f41b3bf19.js:20:29397
Firefox can’t establish a connection to the server at wss://w2.web.whatsapp.com/ws. app.12174fa72d7f41b3bf19.js:20:29397
Firefox can’t establish a connection to the server at wss://w3.web.whatsapp.com/ws. app.12174fa72d7f41b3bf19.js:20:29397
Firefox can’t establish a connection to the server at wss://w4.web.whatsapp.com/ws. app.12174fa72d7f41b3bf19.js:20:29397
Firefox can’t establish a connection to the server at wss://w5.web.whatsapp.com/ws. app.12174fa72d7f41b3bf19.js:20:29397 

Screenshot: https://i.imgur.com/qdbAzYv.png
At the same time it works just fine in Chrome and Edge
Just here to give my "me too" as well with Nightly 64.0a1 (2018-10-01) on MacOS 10.13.6.

Since this is still an ongoing issue, I'd like to re-open if there's any investigation that can be done (for the same reasons that dholbert mentioned in Comment 1).
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
For people affected by this: could you try running one of these commands from a terminal, and see if it succeeds?
 ping dyn.web.whatsapp.com
 ping w1.web.whatsapp.com

...or if you have 'curl' (e.g. perhaps on Mac):
 curl -vvv dyn.web.whatsapp.com
 curl -vvv w1.web.whatsapp.com

See comment 6 -- when I encountered this, those tools were hitting the same sort of issue (though Chrome was not).  It'd be helpful diagnostically to know if that's the case for other people, too.
QA Contact: jduell.mcbugs
QA Contact: jduell.mcbugs
(In reply to Daniel Holbert [:dholbert] from comment #11)
> For people affected by this: could you try running one of these commands
> from a terminal, and see if it succeeds?
>  ping dyn.web.whatsapp.com
>  ping w1.web.whatsapp.com
> 
> ...or if you have 'curl' (e.g. perhaps on Mac):
>  curl -vvv dyn.web.whatsapp.com
>  curl -vvv w1.web.whatsapp.com
> 
> See comment 6 -- when I encountered this, those tools were hitting the same
> sort of issue (though Chrome was not).  It'd be helpful diagnostically to
> know if that's the case for other people, too.

To make sure there's progress on this, I'll NI myself to follow up with the results.
Flags: needinfo?(jonalmeida942)
closing for lack of progress.
Status: REOPENED → RESOLVED
Closed: 2 years ago11 months ago
Resolution: --- → INCOMPLETE
Flags: needinfo?(jonalmeida942)
You need to log in before you can comment on or make changes to this bug.