MLister, you seem to run into sockjs deployment issue. Make sure sockjs server returns wss:// during websocket handshake over https. This is a well-known issue with some sockjs servers - servers don't always know the page is being served over https and return ws:// during handshake.
For example, sockjs-node uses faye-websocket-node code to handle this case is here: https://github.com/faye/faye-websocket-node/blob/master/lib/faye/websocket.js#L40 https://github.com/faye/faye-websocket-node/blob/master/lib/faye/websocket.js#L25-L32
Basically, you must make sure your load-balancer sets 'x-forwarded-proto' header.
Does it make sense?