7

This question already has an answer here:

Steps to reproduce:

What should happen:

  • Meta site opens

What happens instead:

  • "This Connection is Untrusted" message appears:

meta.movies.stackexchange.com uses an invalid security certificate. The certificate is only valid for the following names: *.stackexchange.com, stackexchange.com, meta.stackexchange.com, *.meta.stackexchange.com, *.stackoverflow.com, stackoverflow.com, serverfault.com, stackauth.com, sstatic.net, meta.serverfault.com, superuser.com, meta.superuser.com, stackapps.com, openid.stackauth.com (Error code: ssl_error_bad_cert_domain)

Notes:

Here is the screenshot:

Image description

|improve this question

marked as duplicate by Flyk, hims056, Aziz Shaikh, Martijn Pieters, Lance Roberts Jan 16 '14 at 15:58

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.

  • I couldn't reproduce this on standard settings on firefox 26.0. I'll have a play with security settings – Richard Tingle Jan 16 '14 at 12:12
  • 1
    Ah, I wasn't automatically redirected. By manually entering https://movies.stackexchange.com/ I was able to get this – Richard Tingle Jan 16 '14 at 12:15
  • 1
    Related: meta.stackexchange.com/questions/116782/… – rene Jan 16 '14 at 12:16
  • Do you have the HTTPS Everywhere addon installed? It seems they added some rulesets about SSL support on Stack Exchange without first consulting Stack Exchange, and thereby broke quite a lot of stuff. – TRiG is Timothy Richard Green Jan 16 '14 at 12:23
  • @TRiGisTimothyRichardGreen ah, yes, I do - so I guess it isn't a SE bug then – david.libremone Jan 16 '14 at 12:25
  • @d3vid nope, not a bug, more of a "known issue that they're steadily working on" – Flyk Jan 16 '14 at 12:26
  • @Flyk "steadily working on" isn't quite right. Over two years later, nothing has been done. I'll be really really surprised if it will be ever done. It's just too big a project for SE. – ShaWiz Jun 21 '16 at 8:46
6

As per Nick Craver's blog post about getting Stack Exchange onto SSL, it is currently impossible for them to get SSL working on the meta sites, because wildcard certs of the form 'meta.*.stackexchange.com' won't work.

Nick provided more info in this post on Arqade meta; the plan is to change the domains to make it work. Until then, metas don't support SSL. In fact, none of the sites do, officially.

|improve this answer

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