Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

I'm using Chrome 25.0.1364.172 m and on every StackOverflow page I'm logging the following JavaScript console error:

WebSocket connection to 'ws://' failed:
    Unexpected response code: 502

WebSocket connection error

share|improve this question
Working fine here. What are the results of this test for you? All green? – Shadow Wizard Mar 20 '13 at 15:18
All green apart from WebSockets port 80. I guess this is an issue on my end then! – James Donnelly Mar 20 '13 at 15:21
Yeah, exactly like Geoff just said. – Shadow Wizard Mar 20 '13 at 15:21
up vote 4 down vote accepted

What this is telling you is that you're traffic is being intercepted by a proxy further up the chain. Usually this is the result of using a mobile connection of some sort. You can verify your web socket support here:

If you see that web socket support is available on port 80 it will work properly. If not sadly you're out of luck.

share|improve this answer
No way for you for a silent fallback though? – Shadow Wizard Mar 20 '13 at 15:21
Just commented on @ShaWizDowArd's comment on the original question - no, port 80 isn't green for me. Looks like this is an issue on my end, sorry for any confusion! – James Donnelly Mar 20 '13 at 15:22
@ShaWizDowArd Writing to the console is pretty "silent", that's where you want errors the user doesn't need to care about; displaying a big error banner on the page would be annoying – Michael Mrozek Mar 20 '13 at 15:34
@Michael doesn't look like console.write in action, rather unhandled client side exceptions, plus no live updates as result. On browsers not supporting web sockets I'm almost sure I saw fallback to the old mechanism using plain AJAX. – Shadow Wizard Mar 20 '13 at 15:46
@ShaWizDowArd the standard heartbeat code when editing answers etc still exists; the rest isn't a case of "fallback" - the live updates is entirely supplemental to the standard UI. Nothing was moved exclusively to there - it was all new features. – Marc Gravell Mar 20 '13 at 16:07
@Marc what about inbox new items notification? I'm almost sure it worked in IE9 which doesn't support web sockets. – Shadow Wizard Mar 20 '13 at 16:10
@ShaWizDowArd I am having the same problem for a quite while (In all browsers). It was not happening before. I think it started after installing some important softwares. How to make the proxy not to intercept the traffic? any link? – Mr_Green Aug 22 '13 at 8:59

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .