This is probably not the site you are looking for. You attempted to reach meta.gaming.stackexchange.com, but instead you actually reached a server identifying itself as *.stackexchange.com.

I'm guessing *.stackexchange.com doesn't cover meta.*.stackexchange.com.

2 Answers 2


I outlines why we don't support this in a blog post here:

Stack Overflow: The road to SSL

If we do end up going full SSL, the domains will move to *.meta.stackexchange.com, which we can secure easily as we add sites. We don't have definite plans on this yet. We will be working on it in 2014 as we investigate the best way to make our sites faster all over the world.


Accessing SE sites via SSL is not supported so far, this is one of the reasons why. The structure of the meta and chat domains doesn't fit to the way certificates are handed out, SE is planning to roll out SSL to all sites at some point, though I'm not exactly sure how they want to solve this specific problem.

See also this blog post from Nick Craver with more details about the SSL transition

  • I wonder why the metas are not meta-*.stackexchange.com. Thanks for the fast answer.
    – 3ventic
    Dec 9, 2013 at 6:54
  • @3ventic That wouldn't make sense for stackoverflow and other "promoted" sites.
    – Thomas
    Dec 9, 2013 at 13:31
  • 1
    @Thomas obviously, but meta.["promoted" site].com doesn't have a problem with SSL like this.
    – 3ventic
    Dec 9, 2013 at 14:18
  • @3ventic Good point
    – Thomas
    Dec 9, 2013 at 14:56

You must log in to answer this question.

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