3

I wanted to ask a question on Meta Unix & Linux (http://meta.unix.stackexchange.com). I'm logged in to Unix & Linux (http://unix.stackexchange.com), and it's showing just over 700 rep for me. I switched to Meta-U&L and (a) I'm not logged in and (b) pressing the 'login' button didn't seem to do anything useful.

Any idea what gives?

  • Why do you have to login to the meta when you're already logged in to the main site?
  • How does one login to a meta when the login button does nothing useful? Which weird non-Stack Exchange site has to be granted what privileges to do what possibly (but probably not) abusive things to my browser?

I'm using Firefox 41.0.1 on Mac OS X 10.11 El Capitan. I do have AdBlock Pro, Ghostery and other extensions installed.


chirlu asks:

Are you sure you are logged in on the non-https Unix.SE?

I was going to say "yes", but then I look and see that in fact I am connected to the secure https://unix.stackexchange.com/ (I have HTTPS Everywhere as one of the other extensions). So, apparently, I'm logged in on secure U&L but there isn't a secure Meta-U&L (or, at least, connecting to https://unix.meta.stackexchange.com/ ends up at http://meta.unix.stackexchange.com, losing the 's'). When I connect to SO, I'm connected to the secure version; when I switch to MSO, that is also the secure version. That seems as though it could easily be the source of the trouble. It leaves some questions:

  1. Why isn't there a secure Meta-U&L like there is a secure MSO?
  2. Do I have to disable HTTPS Everywhere for U&L so that I can see Meta-u&L as myself, or is there something else I can do?
  • Are you sure you are logged in on the non-https Unix.SE? – chirlu Oct 10 '15 at 17:16
  • @chirlu: Thanks for the question — it looks like your thinking is on the right track. I've updated the question with some extra information. Any suggestions? – Jonathan Leffler Oct 10 '15 at 18:56
  • Given the additional information from @chirlu, it looks like Can't login with Stack Exchange OpenID when HTTPS Everywhere plugin is active — which dates from January 2014 — is still a problem even when using Google rather than Stack Exchange as the OpenID source. The workaround in that question is to turn off HTTPS Everywhere for U&L (it now works via the icon in the tool-bar/search-bar rather than the Tools-->HTTPS Everywhere menu, but that has resolved my immediate problem), but why isn't there a working secure Meta-U&L? – Jonathan Leffler Oct 10 '15 at 19:11
  • 1
    For the first part, why there aren’t (working) secure per-site metas, see meta.stackexchange.com/questions/265918 (in short: would require a separate certificate for each meta.site.stackexchange.com; will be fixed by changing to site.meta.stackexchange.com). For the other part, I had some troubles myself a while ago, but it works now for me. Unfortunately I don’t know what I did to make it work (or what some other party such as SE did to make it work), so not very helpful I guess. :-/ – chirlu Oct 11 '15 at 3:47

You must log in to answer this question.

Browse other questions tagged .