7
\$\begingroup\$

When I browse to https://codereview.meta.stackexchange.com/ using Firefox, I get a message that the security certificate is bad because it's for *.stackexchange.com and *.meta.stackexchange.com (among others). I have to add an exception in order to view the meta site.

\$\endgroup\$

    1 Answer 1

    6
    \$\begingroup\$

    This is a known issue (yeah, sucky answer).

    It has been known for years, and the fix is likely not going to arrive any time soon.

    In reality, you probably have not been using https to connect to meta, so you have not noticed. The login and so on work fine, it's just the actual meta.*.stackexchange.com sites (meta.stackexchage.com works fine...).

    The issue is related to the need to create unreasonably many certificates because the wildcard * in the certified domains only goes one sub-domain deep.

    Nick Craver's blog explains this a lot better

    Useful links:

    \$\endgroup\$
    1
    • \$\begingroup\$Usually I just use http to connect to meta.*.SE but I had found a link inside help that used https. But now I can't find it any more!\$\endgroup\$
      – Snowbody
      CommentedApr 2, 2015 at 13:33

    You must log in to answer this question.

    Start asking to get answers

    Find the answer to your question by asking.

    Ask question

    Explore related questions

    See similar questions with these tags.