Refused to Load Stript -> PusherError: 1006

[6temes]

Atom: 1.19.4 AtomPair: 2.0.13 Os: MacOS Sierra 10.12.6

I am having the following errors:

/Users/user/.atom/packages/atom-pair/lib/pusher/pusher.js:2382 
WebSocket connection to 'wss://ws.pusherapp.com/app/51b1aeb8afea05887e26?protocol=7&client=js&version=2.2.3&flash=false' failed: Invalid frame header

/Users/user/.atom/packages/atom-pair/lib/pusher/pusher.js:117 
Pusher : Error : {"type":"WebSocketError","error":{"type":"PusherError","data":{"code":1006}}}

/Users/user/.atom/packages/atom-pair/lib/pusher/pusher.js:2382 
WebSocket connection to 'wss://ws.pusherapp.com/app/51b1aeb8afea05887e26?protocol=7&client=js&version=2.2.3&flash=false' failed: Invalid frame header

/Users/user/.atom/packages/atom-pair/lib/pusher/pusher.js:117 
Pusher : Error : {"type":"WebSocketError","error":{"type":"PusherError","data":{"code":1006}}}

/Users/user/.atom/packages/atom-pair/lib/pusher/pusher.js:1051 
Refused to load the script 'http://js.pusher.com/2.2.3/xhr.js' because it violates the following Content Security Policy directive: "script-src 'self'".

/Users/user/.atom/packages/atom-pair/lib/pusher/pusher.js:1051 
Refused to load the script 'http://js.pusher.com/2.2.3/xhr.js' because it violates the following Content Security Policy directive: "script-src 'self'".

I tried to connect from 2 different networks (to discard a network problem)

[kn100]

Hi,

Error 1006 is usually caused by a misbehaving proxy server. Could you ensure that your system is not configured to use any proxy?

[simmerz]

I'm seeing the same issue, but no proxy.

[kn100]

Have you modified any of the config files to for example use your own Pusher app instance?

[simmerz]

No, only set up my own Pusher app's key and secret in the settings pane. I have a free account.

[6temes]

None of the networks has a proxy.

[dmitrymatveev]

Atom: 1.21.0 AtomPair: 2.0.13 Win 7

I am also experiencing the same issue (with similar error log, except line numbers)

Newly created pusher app with configured "Enable client events", I also double checked my key:secret in case somehow those are causing it.

no proxies on my network