Over the last few days, I've noticed that notifications such as "x questions with new activity" and general comment notifications don't appear particularly often.

Related screenshot showing that qa.sockets.stackexchange.com is failing:

This seems to be this issue creeping up again.

  • Are you at a workplace, or behind a proxy? It looks like you're having issues reaching us on SSL. – Nick Craver Oct 28 '13 at 14:58
  • @NickCraver Both at the workplace and from home has this issue. From home is just connecting to a router on a LAN. This was working 100% before (except when my connection is really shaky, which it isn't now). Both run Chrome 30, but tried IE 9 and it gives the same. – Dukeling Oct 28 '13 at 15:02
  • When you go to websocketstest.com what you get? – Shadow The Princess Wizard Oct 28 '13 at 15:09
  • @ShaWizDowArd It seems sufficiently happy. – Dukeling Oct 28 '13 at 15:10
  • Hmm.. so it's SSL issue as Nick mentioned above. Should have known better than to doubt him! ;) – Shadow The Princess Wizard Oct 28 '13 at 15:11
  • @Dukeling if you visit this URL, what do you get? qa.sockets.stackexchange.com/ping – Nick Craver Oct 28 '13 at 17:02
  • @NickCraver "StackExchange web-socket server on NY-WEB08" – Dukeling Oct 28 '13 at 17:08
  • hmm that means you're able to hit us fine on SSL, do you know what kind of proxy you're behind? – Nick Craver Oct 28 '13 at 18:22
  • @Dukeling we have made some changes to attempt non-SSL if SSL fails, can you give it a try now? – Nick Craver Oct 29 '13 at 10:05
  • @NickCraver It seems to be working better now. It doesn't do much for 2.5 minutes (can be reduced?), then starts working. Screenshot. I don't know much about our network setup at work, but at home I'm not behind a proxy (at least not as far as I know) - websocketstest.com and amibehindaproxy.com seems to think I'm not. – Dukeling Oct 29 '13 at 12:03
  • We made some additional timeout changes on the SSL, can you tell me if that helped or hurt? I actually think we may have broken you again...if that's the case I know just how to fix it. – Nick Craver Oct 30 '13 at 10:06
  • @NickCraver At the moment it seems to be doing better - the first connection doesn't appear to be failing anymore, or maybe the root cause was fixed, or maybe it's just temporary. – Dukeling Oct 30 '13 at 17:32
  • @Dukeling - can I close this as status-completed? – Oded Aug 1 '14 at 13:24
  • @Oded Sure. I don't remember it happening again too recently. – Dukeling Aug 5 '14 at 20:59

You must log in to answer this question.

Browse other questions tagged .