You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 23, 2018. It is now read-only.
So I noticed some 503's, 'bad handshake', and 'websocket closed before establishing a connection' errors in chrome tonight. After researching, I have a hunch this might have started happening when the app was scaled up earlier today.
So I noticed some 503's, 'bad handshake', and 'websocket closed before establishing a connection' errors in chrome tonight. After researching, I have a hunch this might have started happening when the app was scaled up earlier today.
See links below:
https://remysharp.com/2014/11/10/muddling-my-way-through-real-time#server-side
http://stackoverflow.com/questions/26217312/socket-io-and-multiple-dynos-on-heroku-node-js-app-websocket-is-closed-before
The text was updated successfully, but these errors were encountered: