Page MenuHomePhabricator

Account creation blocked on beta
Closed, DuplicatePublic

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

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

Actual behavior

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

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


  1. https://en.wikipedia.org/wiki/User_talk:PPelberg_(WMF)#Reply_feature_at_en.wikipedia.beta.wmflabs.org/
  2. https://www.mediawiki.org/w/index.php?title=Topic:Vcwvt3bq03o5gv8h&topic_showPostId=vkh8irisui29zvrx#flow-post-vkh8irisui29zvrx
  3. https://www.mediawiki.org/w/index.php?title=Topic:Vcwvt3bq03o5gv8h&topic_showPostId=vkhjlgp64o9ihx5o#flow-post-vkhjlgp64o9ihx5o

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

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 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 :]

Krenair added a comment.EditedApr 16 2020, 12:30 PM

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.