6

Was a little surprised to see this screen when I attempted to switch to Meta:

enter image description here

I know that this was already commented on (SSL Certificate not valid here), but that was about a year ago. Has no progress been made on this issue, or is this a regression?

  • Was this via a link somewhere on the network, or did you type that in? Because all links on the network should've been converted. – SQB Aug 8 '17 at 6:14
  • @SQB - check the date of the question :P – Mithical Aug 8 '17 at 10:31
  • 1
    @Mithrandir app only shows "Edited 17 hr. ago" :( – SQB Aug 8 '17 at 12:16
4

Meta links have been switched to scifi.meta.stackexchange.com, and now have a valid HTTPS certificate. See this post on main meta. This should probably be now (but my flag requesting it was declined :/).

  • 1
    Ask and ye shall (eventually, sometimes) receive. – Pops Aug 7 '17 at 18:29
5

At least as of right now, visiting meta sites over SSL is "not supported". The most recent information I could find on meta.SE was from last year, and there doesn't appear to have been any change since then.

The technical problem is the way the domain names are formatted breaks the wildcard SSL certificates. The certificate is for *.stackexchange.com, which matches site.stackexchange.com but doesn't match meta.site.stackexchange.com.

In order to make things work they need to restructure the domain names so that, e.g.

meta.scifi.stackexchange.com ===> scifi.meta.stackexchange.com

Once that's done, a certificate for *.meta.stackexchange.com will work, but I assume that's not a trivial change so they haven't gotten around to it.

See:

Better HTTPS support for Stack Exchange sites

Untrusted connection when visiting per-site meta over SSL

This blog post

  • Interesting... Because I did not put https in the address bar. I just clicked the meta link from the navigation menu. – JDB Oct 28 '15 at 17:37
  • 1
    @JDB Which link? And do you have any addons like HTTPSEverywhere installed? – Adam Lear Oct 28 '15 at 17:53
  • 1
    @AnnaLear - Took some retracing of my steps, but I figured it out... I followed the first link from this post (which had the https protocol explicitly defined) which took me to the main site. I finished reading the content, then clicked the "Meta" link from the "Help" menu. I'm guessing it's a relative link because it adopted the https protocol, resulting in the error message in my post. If https is not supported in Meta, then the nav link should probably not be relative. – JDB Oct 28 '15 at 18:21
  • 1
    I've corrected the links in that post; that is annoying. – Shog9 Oct 28 '15 at 18:23

You must log in to answer this question.

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