Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Possible Duplicate:
Better HTTPS support for Stack Exchange sites
Google Chrome warning of an SSL problem with Stack Overflow

I tried to navigate to this StackOverflow answer from a website that was not part of StackExchange. Google Chrome browser on Windows 7 returned the following:

Screen capture 21 Oct 2012 approx 3:00 Arizona Time

I am feeling some concern.

  • In my haste, I neglected to obscure all browser my bookmarks. Yes, I am an active Pinterest user.
share|improve this question

marked as duplicate by Shadow Wizard, Bo Persson, Rory, animuson, Martijn Pieters Oct 21 '12 at 13:48

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.

Stack Overflow does not use SSL. – BoltClock's a Unicorn Oct 21 '12 at 10:16
You should alert the source of the link and have him put proper link instead. (using http:// rather than https://) – Shadow Wizard Oct 21 '12 at 11:14
@ShaWizDowArd Thank you. I wanted to do that, but didn't want to be annoying, seem disrespectful to him. I appreciate your input. – Ellie Kesselman Oct 21 '12 at 12:36
Well, is simply a broken link. In my opinion it's no different than or any other wrong/broken link. – Shadow Wizard Oct 21 '12 at 12:42
up vote 2 down vote accepted

The SSL certificate is valid for, and *, while you are visiting That is the reason you are getting that error.

Firefox gives me a similar error. These are the details about the error: uses an invalid security certificate.

The certificate is only valid for the following names: * ,


share|improve this answer
Why doesn't this happen with other StackExchange sites from non SE sites e.g. Security StackExchange, when I navigate here with the https? – Ellie Kesselman Oct 21 '12 at 10:25
"The SSL certificate is valid for, and *", @Feral – Mat Oct 21 '12 at 10:28
Because they are * domains. – BoltClock's a Unicorn Oct 21 '12 at 10:28
Oh, sigh, sorry! I forgot that stackoverflow has its own domain, that the others are subdomains. And so does SuperUser (have its own domain)! Sorry! – Ellie Kesselman Oct 21 '12 at 10:29
So I'd have the same problem with both SuperUser and ServerFault, yes? – Ellie Kesselman Oct 21 '12 at 10:36
And this is why I would have the same problem, and this is why it is like that, and will remain like that for the forseeable future… Yes? – Ellie Kesselman Oct 21 '12 at 10:39
@FeralOink I get the same error for Super User. – kiamlaluno Oct 21 '12 at 10:39
Not a rhetorical question, nor sarcasm. I – Ellie Kesselman Oct 21 '12 at 10:39
@kiamlaluno And you would for ServerFault too, yes? They i.e. StackExchange site administration don't add the SSL for those other two domains because of all that other stuff in the linked question, is that the issue? Disclaimer: I'm not trying to be annoying or ask gratuitously repetitive questions. Thank you for helping me. – Ellie Kesselman Oct 21 '12 at 10:41
This is what I'm trying to say: I'm not asking about this for this sort of purpose I appreciate the sentiment and purpose and humor of that, but am not um, doing that sort of thing at the moment. – Ellie Kesselman Oct 21 '12 at 10:45
@FeralOink The question you linked explains exactly why they are not going to use secure connections on the trilogy sites. As the status is status-deferred, there is the hope they can implement it in the future, but it is not something they can do in the next months. – kiamlaluno Oct 21 '12 at 10:49
@kiamlaluno Thank you very much! – Ellie Kesselman Oct 21 '12 at 12:34

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