1

This question already has an answer here:

I'm on Windows 10 64-bit version 1511 (OS Build 10585.545).

Recently my Chrome updated to version 53.0.2785.89 m (64-bit) and since then I get this error when entering meta ELU.SE:

NET::ERR_CERT_COMMON_NAME_INVALID

I can access meta ELU.SE if I manually remove the "https" from it or click the button to "proceed ... (unsafe)". But what's happening?

EDIT: The proposed duplicate is simply a part of more linked duplicates. I see that this problem has happened to many before me, but why did I start seeing this issue just after Chrome updated to version 53? I understand that SE's HTTPS setup isn't perfected yet, but how do I solve my problem for now?

marked as duplicate by rene, Shadow Wizard support Sep 4 '16 at 10:31

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • @Glorfindel Thanks, that link takes me down a rabbit hole, a chain of "marked as duplicate", but no clear solutions. – NVZ Sep 4 '16 at 10:21
  • Bottom line: HTTPS doesn't work on most Meta sites. – Glorfindel Sep 4 '16 at 10:22
  • @Glorfindel But I had no such issues until Chrome updated to v53. Why is that? – NVZ Sep 4 '16 at 10:22
  • You probably clicked the "proceed to..." link long ago and forgot about it, while Chrome remembered it - until that last update. – Shadow Wizard Sep 4 '16 at 10:31
  • @ShadowWizard Maybe so. But now I have to click it everytime I turn on the PC. I haven't found a good workaround for this yet. Also, Chrome updates very frequently and I don't remember seeing such an error in months. – NVZ Sep 4 '16 at 10:34
  • So... just don't browse meta sites via https?? Problem solved. – Shadow Wizard Sep 4 '16 at 10:37
  • @ShadowWizard I have no other choice, apparently. Haha – NVZ Sep 4 '16 at 10:38
  • Why? If you have plugin forcing https, disable it for stackexchange.com sub domains. – Shadow Wizard Sep 4 '16 at 10:39
  • @ShadowWizard Thanks! Almost forgot that I have "HTTPS Everywhere" installed. Apparently the plugin has caused issues on many Chrome 53 users, says Google results. – NVZ Sep 4 '16 at 10:41
  • So get rid of it... I'm not using plugins on permanent basis exactly for those reasons - I can't control the bugs and problems they cause to the browser. All in all, they cause more harm than good. :/ – Shadow Wizard Sep 4 '16 at 10:50
  • 1
    @ShadowWizard YMMV. I have had the best experience with plugins ever since I started using Chrome years ago. The occasional hiccups are not gonna stop me from using plugins/extensions. :) – NVZ Sep 4 '16 at 11:02
  • As you wish... just remember to accuse them first, before accusing SE. :-) – Shadow Wizard Sep 4 '16 at 11:13

Browse other questions tagged .