I've encountered this same bug. Man, what is with October and software time-bombs! There was just a time-bomb with Visual Studio and SSDT that went off on Oct 6th because of some bug involving an expired certificate, making it impossible to install stuff without temporarily setting back the system clock: http://social.msdn.microsoft.com/Forums/sqlserver/en-US/51ef983f-1f07-41b4-bad4-3541e93d46 47/known-issue-ssdt-install-fails-validating-certificates?forum=ssdt&prof=required
Anyway, I just moved everything to a new server and thought I had something configured wrong, until I realized I could connect from my desktop's browser, but not the one on the server.
The error I get is "WebSocket connection to 'wss://xxx.xxx.xxx.xxx/ws.ashx' failed: Error during WebSocket handshake: Sec-WebSocket-Protocol mismatch".
*** Issue Resolved ***
I was completely stumped. Desperate. The thought of re-writing 10K lines made me sick. Then, I stumbled on pure gold. I was visiting https://groups.google.com/forum/#!topic/chicagoboss/M4fTHZN6qNE and I found an entry about the change in expected parameters in the WebSocket constructor in javascritp from old browsers to new. Adobe was adding a second parameter, "json" to the constructor and Chrome did not like it as the CF server was not returning the same item. I removed the second param and what do you know, it came alive. People are chatting and the world makes sense! Just wanted to give you an update.
Nice to hear you found your answer. To assist others, please kindly mark it as 'Correct'. Thanks.