6

I know SE is going through updating their sites to secure pages, so I guess I'm just raising awareness that I encountered an Insecure Connection warning for the following domain:

discuss.area51.stackexchange.com

enter image description here

While trying to access: //discuss.area51.stackexchange.com/questions/20966/minimum-activity-requirements-for-area-51

||||||
  • 2
    While we wait for an official answer, I'll toss in that it's my understanding that Area51 is a different server, running a different (iirc older) version of the SE software. You may find the Meta Stack Overflow post HTTPS: It's time informative as well. – RandomThought Apr 14 '17 at 2:10
3

Yes, Area 51 isn't really secure yet.

This is a really high level list, there are a crazy number of nuances and edge cases to the above. This is for Q&A. Area 51, Chat, and stackexchange.com (the main site) have a separate set of concerns and code we'll address after Q&A. The list also isn't necessarily in order. While we're testing #6, Samo and I will be working on #11 at the same time.
source

And discussions was apparently causing problems:

The only such special casing in place now is https://area51.meta.stackexchange.com/, which is already a massive pain and tech debt factor. In fact, it's causing pain with the HTTPS move right now, since I can't move it the same way as everything else.
source

See also this post on Meta.SE.

||||||

You must log in to answer this question.

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