Slack not working with NoScript 10.1

Ask for help about NoScript, no registration needed to post
Post Reply
mcorino

Slack not working with NoScript 10.1

Post by mcorino »

Just got the 10.1 update installed. Thanks for that.
Most things seem to work fine except for Slack.
NoScript blocks all websocket connections (wss://) and I do not seem to get that working whatever I do.
Is anybody else experiencing similar problems?
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Top
dna
Posts: 2
Joined: Tue Nov 21, 2017 8:59 am

Re: Slack not working with NoScript 10.1

Post by dna »

Same here. Websockets for some reasons can not be whitelisted.

When I browse a slack grouß, I see a message that there are «connection troubles», however, this is how the Noscript dialog looks like:

Image

The console shows some warnings firefox cannot connect to these websocket resources. Here's a complete console dump

Code: Select all

Nov-21 10:38:12.355 [SOCKET-MANAGER] (T02RRA0E6) Changing from never_connected to prov_connect
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:12.357 [SOCKET-MANAGER] (T02RRA0E6) will stay in prov_connect state for up to 10000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:12.359 [SOCKET-MANAGER] (T02RRA0E6) Changing from prov_connect to prov_connecting
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:12.360 [SOCKET-MANAGER] (T02RRA0E6) will stay in prov_connecting state for up to 20000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:13.499 [BOOT] Finalizing incremental boot
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:15.719 [FLANNEL] received a user_counts_request call while we are not connected; deferring
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: false, policyType: "fetch", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "fetch", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "fetch", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "fetch", ownFrame: true }
log.js:9:39
Diese Website verwendet anscheinend einen scroll-verknüpften Positionierungseffekt. Dies könnte mit asynchronem Verschieben (Panning) schlecht zusammenspielen; siehe https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects für weitere Details und nehmen Sie an der Diskussion über damit verbundene Werkzeuge und Funktionen teil!
C071B9S5Q
Firefox kann keine Verbindung zu dem Server unter wss://mpmulti-x71w.lb.slack-msgs.com/?flannel=2&token=xoxs-2875340482-7088105573-274958011044-2919feb188&start_args=%3Fagent%3Dwebapp_83ea537703386095c674e00deeb93178e2fd237b%26eac_cache_ts%3Dtrue%26cache_ts%3D0%26name_tagging%3Dtrue%26ms_latest%3Dtrue aufbauen.
application.e5561f8ab2b90613e899.min.js:32:501928
Nov-21 10:38:17.990 [SOCKET-MANAGER] (T02RRA0E6) Changing from prov_connecting to error
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:17.991 [SOCKET-MANAGER] (T02RRA0E6) will stay in error state for up to 10000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:17.994 SOCKET-MANAGER (T02RRA0E6) Closing socket due to unknown error
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
2017/11/21 10:38:17.996  Stacktrace: ↴
 e@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:98522
e@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:99675
l/<@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:1056
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:389086
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:390798
s@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:275281
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:391162
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:385240
Il/<@https://a.slack-edge.com/bv1-1/rollup-core_required_libs.fbc00414cfe9ae6c53ce.min.js:201:112750
O@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:500553
e/this._socket.onclose@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:502234
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:97371
Nov-21 10:38:18.700 [SOCKET-MANAGER] (T02RRA0E6) Changing from error to wait_for_connectivity
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:18.800 [SOCKET-MANAGER] (T02RRA0E6) will stay in wait_for_connectivity state for up to 300000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
[NoScript] Loading NoScript in document https://*****.slack.com/messages/C071B9S5Q, scripting=true, content type text/html
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "script", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "script", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "script", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "script", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "script", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "script", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "script", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "script", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "script", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "script", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "script", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "script", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: false, policyType: "ping", ownFrame: true }
log.js:9:39
Nov-21 10:38:09.316 [BOOT] booted! pri:0 version:1511242608 start_ms:1511257089309 (6ms ago)
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:09.318 [BOOT] Starting incremental boot (early)
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "fetch", ownFrame: true }
log.js:9:39
Nov-21 10:38:12.355 [SOCKET-MANAGER] (T02RRA0E6) Changing from never_connected to prov_connect
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:12.357 [SOCKET-MANAGER] (T02RRA0E6) will stay in prov_connect state for up to 10000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:12.359 [SOCKET-MANAGER] (T02RRA0E6) Changing from prov_connect to prov_connecting
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:12.360 [SOCKET-MANAGER] (T02RRA0E6) will stay in prov_connecting state for up to 20000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:13.499 [BOOT] Finalizing incremental boot
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:15.719 [FLANNEL] received a user_counts_request call while we are not connected; deferring
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Diese Website verwendet anscheinend einen scroll-verknüpften Positionierungseffekt. Dies könnte mit asynchronem Verschieben (Panning) schlecht zusammenspielen; siehe https://developer.mozilla.org/docs/Mozilla/Performance/ScrollLinkedEffects für weitere Details und nehmen Sie an der Diskussion über damit verbundene Werkzeuge und Funktionen teil!
C071B9S5Q
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: false, policyType: "fetch", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "fetch", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "fetch", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "fetch", ownFrame: true }
log.js:9:39
Firefox kann keine Verbindung zu dem Server unter wss://mpmulti-x71w.lb.slack-msgs.com/?flannel=2&token=xoxs-2875340482-7088105573-274958011044-2919feb188&start_args=%3Fagent%3Dwebapp_83ea537703386095c674e00deeb93178e2fd237b%26eac_cache_ts%3Dtrue%26cache_ts%3D0%26name_tagging%3Dtrue%26ms_latest%3Dtrue aufbauen.
application.e5561f8ab2b90613e899.min.js:32:501928
Nov-21 10:38:17.990 [SOCKET-MANAGER] (T02RRA0E6) Changing from prov_connecting to error
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:17.991 [SOCKET-MANAGER] (T02RRA0E6) will stay in error state for up to 10000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:17.994 SOCKET-MANAGER (T02RRA0E6) Closing socket due to unknown error
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
2017/11/21 10:38:17.996  Stacktrace: ↴
 e@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:98522
e@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:99675
l/<@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:1056
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:389086
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:390798
s@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:275281
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:391162
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:385240
Il/<@https://a.slack-edge.com/bv1-1/rollup-core_required_libs.fbc00414cfe9ae6c53ce.min.js:201:112750
O@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:500553
e/this._socket.onclose@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:502234
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:97371
Nov-21 10:38:18.700 [SOCKET-MANAGER] (T02RRA0E6) Changing from error to wait_for_connectivity
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:18.800 [SOCKET-MANAGER] (T02RRA0E6) will stay in wait_for_connectivity state for up to 300000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "fetch", ownFrame: true }
log.js:9:39
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "script", ownFrame: true }
log.js:9:39
Nov-21 10:38:23.955 [SOCKET-MANAGER] (T02RRA0E6) Changing from wait_for_connectivity to wait_for_rate_limit
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:23.956 [SOCKET-MANAGER] (T02RRA0E6) will stay in wait_for_rate_limit state for up to 120000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:23.960 [SOCKET-MANAGER] (T02RRA0E6) Changing from wait_for_rate_limit to connect
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:23.961 [SOCKET-MANAGER] (T02RRA0E6) will stay in connect state for up to 10000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:23.963 [SOCKET-MANAGER] (T02RRA0E6) Changing from connect to checking_fast_reconnect
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:23.965 [SOCKET-MANAGER] (T02RRA0E6) will stay in checking_fast_reconnect state for up to 60000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:23.969 [SOCKET-MANAGER] (T02RRA0E6) Changing from checking_fast_reconnect to prov_connect
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:23.971 [SOCKET-MANAGER] (T02RRA0E6) will stay in prov_connect state for up to 10000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:23.973 [SOCKET-MANAGER] (T02RRA0E6) Changing from prov_connect to prov_connecting
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:23.974 [SOCKET-MANAGER] (T02RRA0E6) will stay in prov_connecting state for up to 20000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: false, policyType: "fetch", ownFrame: true }
log.js:9:39
Firefox kann keine Verbindung zu dem Server unter wss://mpmulti-x71w-1.lb.slack-msgs.com/?flannel=2&token=xoxs-2875340482-7088105573-274958011044-2919feb188&start_args=%3Fagent%3Dwebapp_83ea537703386095c674e00deeb93178e2fd237b%26eac_cache_ts%3Dtrue%26cache_ts%3D0%26name_tagging%3Dtrue%26ms_latest%3Dtrue aufbauen.
application.e5561f8ab2b90613e899.min.js:32:501928
Nov-21 10:38:24.351 [SOCKET-MANAGER] (T02RRA0E6) Changing from prov_connecting to error
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:24.354 [SOCKET-MANAGER] (T02RRA0E6) will stay in error state for up to 10000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:24.358 SOCKET-MANAGER (T02RRA0E6) Closing socket due to unknown error
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
2017/11/21 10:38:24.361  Stacktrace: ↴
 e@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:98522
e@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:99675
l/<@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:1056
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:389086
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:390798
s@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:275281
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:391162
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:385240
Il/<@https://a.slack-edge.com/bv1-1/rollup-core_required_libs.fbc00414cfe9ae6c53ce.min.js:201:112750
O@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:500553
e/this._socket.onclose@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:502234
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:97371
Nov-21 10:38:24.374 [SOCKET-MANAGER] (T02RRA0E6) Changing from error to wait_for_connectivity
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:24.376 [SOCKET-MANAGER] (T02RRA0E6) will stay in wait_for_connectivity state for up to 300000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "fetch", ownFrame: true }
log.js:9:39
Nov-21 10:38:24.992 [SOCKET-MANAGER] (T02RRA0E6) Changing from wait_for_connectivity to wait_for_rate_limit
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:24.993 [SOCKET-MANAGER] (T02RRA0E6) will stay in wait_for_rate_limit state for up to 120000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:24.999 [SOCKET-MANAGER] (T02RRA0E6) Changing from wait_for_rate_limit to connect
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.000 [SOCKET-MANAGER] (T02RRA0E6) will stay in connect state for up to 10000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.300 [SOCKET-MANAGER] (T02RRA0E6) Changing from connect to checking_fast_reconnect
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.400 [SOCKET-MANAGER] (T02RRA0E6) will stay in checking_fast_reconnect state for up to 60000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.700 [SOCKET-MANAGER] (T02RRA0E6) Changing from checking_fast_reconnect to prov_connect
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.800 [SOCKET-MANAGER] (T02RRA0E6) will stay in prov_connect state for up to 10000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.100 [SOCKET-MANAGER] (T02RRA0E6) Changing from prov_connect to prov_connecting
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.100 [SOCKET-MANAGER] (T02RRA0E6) will stay in prov_connecting state for up to 20000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: false, policyType: "fetch", ownFrame: true }
log.js:9:39
Firefox kann keine Verbindung zu dem Server unter wss://mpmulti-x71w-2.lb.slack-msgs.com/?flannel=2&token=xoxs-2875340482-7088105573-274958011044-2919feb188&start_args=%3Fagent%3Dwebapp_83ea537703386095c674e00deeb93178e2fd237b%26eac_cache_ts%3Dtrue%26cache_ts%3D0%26name_tagging%3Dtrue%26ms_latest%3Dtrue aufbauen.
application.e5561f8ab2b90613e899.min.js:32:501928
Nov-21 10:38:25.211 [SOCKET-MANAGER] (T02RRA0E6) Changing from prov_connecting to error
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.212 [SOCKET-MANAGER] (T02RRA0E6) will stay in error state for up to 10000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.213 SOCKET-MANAGER (T02RRA0E6) Closing socket due to unknown error
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
2017/11/21 10:38:25.216  Stacktrace: ↴
 e@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:98522
e@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:99675
l/<@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:1056
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:389086
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:390798
s@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:275281
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:391162
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:385240
Il/<@https://a.slack-edge.com/bv1-1/rollup-core_required_libs.fbc00414cfe9ae6c53ce.min.js:201:112750
O@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:500553
e/this._socket.onclose@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:502234
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:97371
Nov-21 10:38:25.224 [SOCKET-MANAGER] (T02RRA0E6) Changing from error to wait_for_connectivity
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.225 [SOCKET-MANAGER] (T02RRA0E6) will stay in wait_for_connectivity state for up to 300000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "fetch", ownFrame: true }
log.js:9:39
Nov-21 10:38:25.649 [SOCKET-MANAGER] (T02RRA0E6) Changing from wait_for_connectivity to wait_for_rate_limit
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.650 [SOCKET-MANAGER] (T02RRA0E6) will stay in wait_for_rate_limit state for up to 120000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.658 [SOCKET-MANAGER] (T02RRA0E6) Changing from wait_for_rate_limit to connect
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.658 [SOCKET-MANAGER] (T02RRA0E6) will stay in connect state for up to 10000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.660 [SOCKET-MANAGER] (T02RRA0E6) Changing from connect to checking_fast_reconnect
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.660 [SOCKET-MANAGER] (T02RRA0E6) will stay in checking_fast_reconnect state for up to 60000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.663 [SOCKET-MANAGER] (T02RRA0E6) Changing from checking_fast_reconnect to prov_connect
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.664 [SOCKET-MANAGER] (T02RRA0E6) will stay in prov_connect state for up to 10000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.666 [SOCKET-MANAGER] (T02RRA0E6) Changing from prov_connect to prov_connecting
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.667 [SOCKET-MANAGER] (T02RRA0E6) will stay in prov_connecting state for up to 20000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: false, policyType: "fetch", ownFrame: true }
log.js:9:39
Firefox kann keine Verbindung zu dem Server unter wss://mpmulti-x71w-3.lb.slack-msgs.com/?flannel=2&token=xoxs-2875340482-7088105573-274958011044-2919feb188&start_args=%3Fagent%3Dwebapp_83ea537703386095c674e00deeb93178e2fd237b%26eac_cache_ts%3Dtrue%26cache_ts%3D0%26name_tagging%3Dtrue%26ms_latest%3Dtrue aufbauen.
application.e5561f8ab2b90613e899.min.js:32:501928
Nov-21 10:38:25.828 [SOCKET-MANAGER] (T02RRA0E6) Changing from prov_connecting to error
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.829 [SOCKET-MANAGER] (T02RRA0E6) will stay in error state for up to 10000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.831 SOCKET-MANAGER (T02RRA0E6) Closing socket due to unknown error
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
2017/11/21 10:38:25.833  Stacktrace: ↴
 e@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:98522
e@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:99675
l/<@https://a.slack-edge.com/bv1-1/rollup-core_required_ts.dccadd362b01356101c9.min.js:1:1056
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:389086
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:390798
s@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:275281
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:391162
e@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:385240
Il/<@https://a.slack-edge.com/bv1-1/rollup-core_required_libs.fbc00414cfe9ae6c53ce.min.js:201:112750
O@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:500553
e/this._socket.onclose@https://a.slack-edge.com/bv1-1/application.e5561f8ab2b90613e899.min.js:32:502234
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:97371
Nov-21 10:38:25.841 [SOCKET-MANAGER] (T02RRA0E6) Changing from error to wait_for_connectivity
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:25.842 [SOCKET-MANAGER] (T02RRA0E6) will stay in wait_for_connectivity state for up to 300000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "fetch", ownFrame: true }
log.js:9:39
Nov-21 10:38:26.294 [SOCKET-MANAGER] (T02RRA0E6) Changing from wait_for_connectivity to wait_for_rate_limit
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:26.295 [SOCKET-MANAGER] (T02RRA0E6) will stay in wait_for_rate_limit state for up to 120000 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
Nov-21 10:38:26.296 [SOCKET-MANAGER] (T02RRA0E6) will wait for 59328 ms
rollup-core_required_ts.dccadd362b01356101c9.min.js:1:4827
[NoScript] Received message
Object { type: "seen", request: {…}, allowed: true, policyType: "fetch", ownFrame: true }
log.js:9:39
I tried the suggested trouble-shooting.
* The issue persists even if I deactivate all other plugins and extensions.
* Deleting corrupted addon files from the profile didn't help
* Resetting Noscript settings isn't possible, at least I found no way. In fact the settings page of noscript doesn't actually work, the listed URLs seems to be way to much in order to get the settings page displayed properly.

I'm using Firefox 57.0 with Noscript 10.1.1 on Ubuntu 14.04.

What did helped was to create a new firefox profile. When installing Noscript on that fresh profile, slack could be whitelisted and loaded properly. So it seem to be a conflict with some orphaned settings.

Thanks for any help in advance.
Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Top
Bluemoose

Re: Slack not working with NoScript 10.1

Post by Bluemoose »

I had the same issue. Try manually whitelisting "slack-msgs.com".
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Top
Post Reply

Return to “NoScript Support”