Account creation blocked on beta
Closed, DuplicatePublic
Actions

Assigned To

None

Authored By

	ppelberg
	Apr 15 2020, 1:49 AM

Project Tags

Referenced Files

None

Subscribers

Description

The Editing-team is inviting volunteers to try out Version 1.0 of the new Replying feature on en.wikipedia.beta.wmflabs.org and share feedback about their experience.

Trouble is, several people have reported that they are being blocked from creating accounts on https://en.wikipedia.beta.wmflabs.org [1][2][3], thus preventing them from trying out the new feature.

Expected behavior

Go to en.wikipedia.beta.wmflabs.org
Click the "Create account" link to the left of the "Log in" in link in the top right corner of the window
Enter a username, password, etc.
Click "Create your account"
✅Account created. Success!
Got to https://en.wikipedia.beta.wmflabs.org/wiki/Talk:Dogs
Experiment with the "Reply" link

Actual behavior

Go to en.wikipedia.beta.wmflabs.org
Click the "Create account" link to the left of the "Log in" in link in the top right corner of the window
Enter a username, password, etc
Click "Create your account"
❗️Autoblocked because your IP address was recently used by (a username that seems to vary day-by-day)
~~Got to https://en.wikipedia.beta.wmflabs.org/wiki/Talk:Dogs~~
~~Experiment with the "Reply" link~~

"Autoblocked because your IP address was recently used by "JonelleMaier71"

Related Objects

Mentioned In: T250366: Username change at Beta-Cluster
Mentioned Here: T250085: All users autoblocked from editing on Beta Wikis (IP address detected incorrectly as the deployment-cache-text06 internal IP)

Event Timeline

ppelberg created this task.Apr 15 2020, 1:49 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 15 2020, 1:49 AM

Sure this is still an issue? It seems to be a dupe of T250085: All users autoblocked from editing on Beta Wikis (IP address detected incorrectly as the deployment-cache-text06 internal IP) which was fixed ~12 hours ago

ppelberg moved this task from Needs Prioritization to Required after release on the OWC2020 (OWC2020 Replying 1.0) board.Apr 15 2020, 2:01 AM

I replaced the beta cache box recently and probably forgot to update the MW config that tells it to trust the XFF headers. That means likely everyone is seen as coming from the new cache box.
I see the new cache box's IP shows up in select ipb_address from ipblocks where ipb_auto;. So this is probably the source of all problems.

aaand it sounds like someone already reported this and Hashar took care of it, thanks.

I just created https://en.wikipedia.beta.wmflabs.org/wiki/Special:CentralAuth/Bug_T250245 fine

Reedy closed this task as a duplicate of T250085: All users autoblocked from editing on Beta Wikis (IP address detected incorrectly as the deployment-cache-text06 internal IP).Apr 15 2020, 2:04 AM

In T250245#6057574, @Reedy wrote:

Sure this is still an issue? It seems to be a dupe of T250085: All users autoblocked from editing on Beta Wikis (IP address detected incorrectly as the deployment-cache-text06 internal IP) which was fixed ~12 hours ago

Great spot, @Reedy...account creation seems to be working now. [1][2][3]

@hashar, @Krenair and @Reedy, thank you for getting to bottom of this as quickly as y'all did.

In T250245#6057579, @Krenair wrote:

I replaced the beta cache box recently and probably forgot to update the MW config that tells it to trust the XFF headers. That means likely everyone is seen as coming from the new cache box.

Then we do not have any automatic test to ensure that all beta cluster caches are properly configured in mediawiki-config. So I guess anyone will have missed that bit :-] At least we have a fresh new box now, thank you for that!

@ppelberg thank you for your kind words :]

Davey2010 mentioned this in T250366: Username change at Beta-Cluster .Apr 16 2020, 10:22 AM

In T250245#6061550, @hashar wrote:

In T250245#6057579, @Krenair wrote:

I replaced the beta cache box recently and probably forgot to update the MW config that tells it to trust the XFF headers. That means likely everyone is seen as coming from the new cache box.

Then we do not have any automatic test to ensure that all beta cluster caches are properly configured in mediawiki-config. So I guess anyone will have missed that bit :-] At least we have a fresh new box now, thank you for that!

Yeah. It's kinda annoying because it's only something we do, what, once every year or two? But when we forget the mediawiki-config step it breaks things in more subtle ways instead of completely taking the site down. We probably should have a test, or a documented procedure to follow to replace these boxes (and probably various other types of boxes).
The motivation for the new box btw is less about using a fresh one all the time (logstash2 and restbase02 are from like 2015...) and more about keeping puppet working (and so TLS certs getting renewed etc.) and the OS matching what prod runs.

Account creation blocked on betaClosed, DuplicatePublicActions