[RESOLVED] WhatsApp Web doesn't work properly

[ItachiSan]

As in title.

I use a lot NoScript and my web browsing has become clean, fast and neat thanks to it.

However, I am having a weird issue on WhatsApp Web; if I refresh the page or restart the browser,
WhatsApp Web will be stuck at "Waiting for phone" message. I am then forced to logout and re-login
using my phone.
Disabling the extension completely solves the problem; I tried to see if it was the combination of
more extensions, but it seems that NoScript is the only responsible.
I've already added to the whitelisth:

• whatsapp.com
• whatsapp.net

I would like to keep the options with default values (as now I do) as I believe they are the best for my
protection (I am not sure about some of them, but considering all the others I know that this extension
gives me, I am sure they're for the best )
Waiting for suggestion/fixes!
Thanks in advance

[barbaz]

When this issue occurs, do you see anything related in the Browser Console? (Ctrl-Shift-J)
(if you don't know what's related, turn off CSS warnings and post everything else you see)

[ItachiSan]

The error messages in the debug console are the following:

Code: Select all

Content Security Policy: Il caricamento di una risorsa su self è stato bloccato dalle impostazioni della pagina (“script-src https://web.whatsapp.com 'unsafe-eval' https://ajax.googleapis.com”).  web.whatsapp.com
[Exception... "Component returned failure code: 0x804b0003 (NS_BINDING_REDIRECTED) [nsIChannelEventSink.asyncOnChannelRedirect]"  nsresult: "0x804b0003 (NS_BINDING_REDIRECTED)"  location: "JS frame :: chrome://noscript/content/ForcedRedirectionCallback.js :: CESDelegate.prototype.asyncOnChannelRedirect :: line 51"  data: no]CESDelegate.prototype.asyncOnChannelRedirect@chrome://noscript/content/ForcedRedirectionCallback.js:51:7

NS_BINDING_REDIRECTED: Component returned failure code: 0x804b0003 (NS_BINDING_REDIRECTED) [nsIChannelEventSink.asyncOnChannelRedirect]  ForcedRedirectionCallback.js:51
[Exception... "Component returned failure code: 0x804b0003 (NS_BINDING_REDIRECTED) [nsIChannelEventSink.asyncOnChannelRedirect]"  nsresult: "0x804b0003 (NS_BINDING_REDIRECTED)"  location: "JS frame :: chrome://noscript/content/ForcedRedirectionCallback.js :: CESDelegate.prototype.asyncOnChannelRedirect :: line 51"  data: no]CESDelegate.prototype.asyncOnChannelRedirect@chrome://noscript/content/ForcedRedirectionCallback.js:51:7

NS_BINDING_REDIRECTED: Component returned failure code: 0x804b0003 (NS_BINDING_REDIRECTED) [nsIChannelEventSink.asyncOnChannelRedirect]  ForcedRedirectionCallback.js:51
[Exception... "Component returned failure code: 0x804b0003 (NS_BINDING_REDIRECTED) [nsIChannelEventSink.asyncOnChannelRedirect]"  nsresult: "0x804b0003 (NS_BINDING_REDIRECTED)"  location: "JS frame :: chrome://noscript/content/ForcedRedirectionCallback.js :: CESDelegate.prototype.asyncOnChannelRedirect :: line 51"  data: no]CESDelegate.prototype.asyncOnChannelRedirect@chrome://noscript/content/ForcedRedirectionCallback.js:51:7

NS_BINDING_REDIRECTED: Component returned failure code: 0x804b0003 (NS_BINDING_REDIRECTED) [nsIChannelEventSink.asyncOnChannelRedirect]  ForcedRedirectionCallback.js:51
[Exception... "Component returned failure code: 0x804b0003 (NS_BINDING_REDIRECTED) [nsIChannelEventSink.asyncOnChannelRedirect]"  nsresult: "0x804b0003 (NS_BINDING_REDIRECTED)"  location: "JS frame :: chrome://noscript/content/ForcedRedirectionCallback.js :: CESDelegate.prototype.asyncOnChannelRedirect :: line 51"  data: no]CESDelegate.prototype.asyncOnChannelRedirect@chrome://noscript/content/ForcedRedirectionCallback.js:51:7

NS_BINDING_REDIRECTED: Component returned failure code: 0x804b0003 (NS_BINDING_REDIRECTED) [nsIChannelEventSink.asyncOnChannelRedirect]  ForcedRedirectionCallback.js:51
Content Security Policy: Il caricamento di una risorsa su https://w3.web.whatsapp.com/ws è stato bloccato dalle impostazioni della pagina (“connect-src https://web.whatsapp.com wss://*.web.whatsapp.com https://*.whatsapp.net https://dyn.web.whatsapp.com https://*.giphy.com https://*.tenor.co blob:”).  (sconosciuto)
Firefox non può stabilire una connessione con il server wss://w3.web.whatsapp.com/ws.  app_38fc5c95fd44feb095e5.js:6:25781
Content Security Policy: Il caricamento di una risorsa su https://w4.web.whatsapp.com/ws è stato bloccato dalle impostazioni della pagina (“connect-src https://web.whatsapp.com wss://*.web.whatsapp.com https://*.whatsapp.net https://dyn.web.whatsapp.com https://*.giphy.com https://*.tenor.co blob:”).  (sconosciuto)
Firefox non può stabilire una connessione con il server wss://w4.web.whatsapp.com/ws.  app_38fc5c95fd44feb095e5.js:6:25781
Content Security Policy: Il caricamento di una risorsa su https://w5.web.whatsapp.com/ws è stato bloccato dalle impostazioni della pagina (“connect-src https://web.whatsapp.com wss://*.web.whatsapp.com https://*.whatsapp.net https://dyn.web.whatsapp.com https://*.giphy.com https://*.tenor.co blob:”).  (sconosciuto)
Firefox non può stabilire una connessione con il server wss://w5.web.whatsapp.com/ws.  app_38fc5c95fd44feb095e5.js:6:25781

where

Code: Select all

Il caricamento di una risorsa su URL è stato bloccato dalle impostazioni della pagina

means Resource loading from URL has been blocked from page settings
and

Code: Select all

Firefox non può stabilire una connessione con il server URL

stands for Firefox can't establish a connection with the server URL.

[barbaz]

Does it work if you disable ABE?
(NoScript Options > Advanced > ABE, un-check "Enable ABE")

[ItachiSan]

Seems it did the trick!
Restarting Firefox and after a re-login seems fine. Further testing now.
What should I do to keep ABE on and whitelist WhatsApp Web?

[barbaz]

What, if any, non-default ABE rules do you have?

[ItachiSan]

In fact, I didn't have them.
I was checking stuff out here and I found the syntax.
I tried out to write a rule and this seems to work for me.

Code: Select all

# WhatsApp Web
Site web.whatsapp.com
Accept from SELF *.web.whatsapp.com wss://*.web.whatsapp.com
Deny

[barbaz]

Thanks for letting us know the solution and glad it's working for you again.

[barbaz]

This old thread seems to have become a spam magnet now. Locking.