Are you doing this here on Meta, or on one of our other sites (Writing or Outdoors)? I'll have to check, but it might not work on Meta because we don't have an associated SE site that we want to import posts from -- but if that's the case then we should have a better response than this error, so thanks for the report.

@Monica It seems that was the issue here. I tried linking on this Meta site, since I don't have any content on Writing and Outdoors anyway. It would seem graying out the Authenticate button on this Meta site would be appropriate with an indication of why.

@MaskedMan not your fault; we just added that "don't post here" language because the software made it too easy to end up here. Every other site we set up will have a meta, so it's baked in for now, but Meta doesn't need a meta...

@Monica I realized what might have happened. When I saw the error, I first searched here to see if the problem is already reported. I came across this post https://meta.codidact.com/questions/39514. This was similar to my issue, but not the same. This question was on "meta meta" at the time (I think, don't remember clearly), and on that page, the link still read "Ask Question", so I used that.

I know this is still early days, this is still a small community (and most of them are SE veterans anyway), so this "Don't Post Here" is ok for now. However, the "meta meta" site eventually needs to go if it isn't meant to be used. [It is probably already in the plan, I'm still feeling my way around here. :-)] Hopefully the community will grow to an extent where new users (with no knowledge of SE) will join, and this UI will be confusing even more than it is to the SE veterans.

The "meta meta" page is going to go away, yes. We just need to make sure we've removed all the pre-category code that assumed that every site has a meta -- don't want to break this site in the process of yanking that out.

Understood. I imagined it was something like that. I think that's fine for now.