Can't log in
"Anmeldung fehlgeschlagen! Bitte erneut versuchen."
XTools version: 3.20.3-dd4dc54f
Can't log in
"Anmeldung fehlgeschlagen! Bitte erneut versuchen."
XTools version: 3.20.3-dd4dc54f
I've heard of this happening occasionally. I'm going to need more information to do anything about it.
I just tried it and login worked fine on my end.
Yes, since yesterday. I go through the menu at German Wikipedia and use the shortcut for "User: Articels" or "Beitragszähler". Then I got a "403: Forbidden" and should login ("Aus Leistungsgründen sind die angeforderten Daten nur für eingeloggte Nutzer verfügbar. Bitte melde dich an, um fortzufahren."). Then I click on the login link and it says "Anmeldung fehlgeschlagen! Bitte erneut versuchen. " (Login failed. Please try again).
Tried it on Firefox and Chrome. The address is "https://xtools.wmcloud.org/pages/de.wikipedia.org/Gripweed" for "User:articles" and "https://xtools.wmcloud.org/ec/de.wikipedia/Gripweed?uselang=de" for the edit counter.
Do you have any software that affects cookies? (Check carefully, there's some by default at least in FF.) Most of the time OAuth cookies being blocked just makes it look like nothing happened, but perhaps this is also this type of issue.
Asking because I can't replicate (on FF). Past software you're using I don't see why you'd get something different.
Except if it's related to logging in to your account specifically.
On the technical side; this error message can come from two places: 1 and 2. Both in DefaultController.php.
1 would mean that some part of getOauthClient errors; 2 would mean that the OAuth token saved is not a token; but this token is gotten from 1, and so normally 2 never errors as 1 errors before.
So in the end we error in getOauthClient. But if we examine the whole of the code, we only use user-independent parameters! And so if the issue were there, I would also encounter it.
So @Gripweed my two cents are you've got something installed that limits OAuth.
Sorry, I don't understand your last comment. But it is not browser related. I just tried on my Ipad with Safari and got the same error.
@Gripweed can you login to https://xtools-dev.wmcloud.org/ ?
Possible duplicate: T379867: When logging into XTools through OAuth, sometimes clicking "Allow" does nothing
(As I see it it's different; here we've got an exception showing up in XTools as opposed to nothing happening.)
Other users are reporting the same issue https://de.wikipedia.org/w/index.php?title=Wikipedia:Fragen_zur_Wikipedia&oldid=255822699#Beitragsz%C3%A4hler_/_XTools
I'm also getting the „Login failed“ error message when clicking the login button.
@Xaosflux : it did use to work, we're apparently having trouble getting an OAuth client.
Not sure if it has a connection, but I can't see the Year counts and Month counts charts, with the debugger showing Uncaught RangeError: invalid language tag: "de""
Okay, I'm repro'ing now as well! This is quite bad as a lot of XTools is unusable if you can't login. Investigation underway…
We're catching the error (which we probably shouldn't be). I temporarily removed that try/catch and got our stacktrace:
{
"class": "MediaWiki\\OAuthClient\\Exception",
"message": "Server returned error: oauth_callback must be set, and must be set to \"oob\" (case-sensitive), or the configured callback must be a prefix of the supplied callback.",
"code": 0,
"file": "/var/www/vendor/mediawiki/oauthclient/src/Client.php:149",
"trace": [
"/var/www/src/Controller/DefaultController.php:70",
"/var/www/vendor/symfony/http-kernel/HttpKernel.php:163",
"/var/www/vendor/symfony/http-kernel/HttpKernel.php:75",
"/var/www/vendor/symfony/http-kernel/Kernel.php:202",
"/var/www/public/index.php:25"
]
}Sounds like an issue with our OAuth consumer. I will attempt to create a new one.
Problem identified. HTTPS forwarding is apparently broken somehow… the OAuth callback is http://xtools.wmcloud.org when it should be HTTPS.
Okay, and same problem over at https://xtools-dev.wmcloud.org/
I think something changed either upstream in OAuth (on the wiki) or with Cloud Services. I'm reaching out to folks for help.
OK, I've made a hotfix directly on the app server. Login should work now, but the core problem is still unsolved.
Resolved! We needed to allowlist the new IP ranges as trusted proxies following https://wikitech.wikimedia.org/wiki/News/2025_Cloud_VPS_VXLAN_IPv6_migration
I knew this was coming but didn't connect the dots that we needed a config change on our end. My apologies.
That sounds like a separate issue. Please file a new task, if you wouldn't mind. Thank you!