Canary issue: anti-bot verification failed on login attempt when mainsite is fine (DDG browser)

[Hicleric]

Starting yesterday, whenever I try to access the Canary site logged in, I receive a verification failed message as it appears I'm failing whatever anti-bot measures are being tested there. I'm still able to access the regular site just fine.

Specifically, if I access Canary as a guest I can navigate and read just fine. It's only once I attempt to login that the browser verification message pops up and subsequently fails, locking me out of the site entirely. IIRC Canary will login using my mainsite info, so I'm guessing that whatever anti-bot verification is being used only applies to logged in accounts. The ordinary tricks to resolve false flags don't seem to work.

This is on mobile DDG, Android 16, no extension or anything nonstandard. I've deleted the site tab and data and I'm able to use the site up until I try to login, at which point the verification fails and all further attempts to access the site are blocked. This happens on my home network and cell, and switching networks doesn't help (although I have not yet tested on VPN but I doubt a VPN would pass either)

Given how updates have been lawndarted rolled out as of late, and there have been no announcements this is in the works, I'm understandably concerned that I will have to switch from a perfectly functional browser when this goes to prod

 

[Bartolumiu]

The bot check affects all users, regardless of login status.
If possible, please share the request ID (x-request-id response header in the request, can be found using the browser's devtools) so we can investigate on our end.

 

[Hicleric]

Thanks. I'm not certain how to find that request ID on mobile as it does not seem DDG includes devtools or remote connection as an option. I use DDG's tracker blocker, so Charles won't work either.

 

[Bartolumiu]

Thanks. I'm not certain how to find that request ID on mobile as it does not seem DDG includes devtools or remote connection as an option. I use DDG's tracker blocker, so Charles won't work either.

With FF you can debug via USB by connecting the device to a pc, but no clue about DDG, sorry...

 

[Hicleric]

Well, it looks like the problem is solved if I turn off app tracker blocking. A real shame that is, but I shouldn't be surprised since verification false negatives can come from VPN and VPN-like services (which the DDG app tracker blocker is)