I’ve seen it consistently fail using ungoogled chromium over tor. But when I just now tried Firefox over tor, no issue. I know that U/C is fussy about timing, but the response time seems quick when I use firefox, so I don’t think it’s a problem of lagging.
What version? We do block request where the user agent indicates it using a Chrome version < 120, you’d be surprised how many malicious scrappers do this. The other possibility is that your Tor exit node is in one of the IP ranges we block for the same reason.
I just tried again on Android and it works fine, which is annoying. So I think it might be the exit node thing.
We don’t do anything to block Tor specifically.
I tested and it works on desktop Tor, but on Android it fails. I couldn’t tell you why.
I’ve seen it consistently fail using ungoogled chromium over tor. But when I just now tried Firefox over tor, no issue. I know that U/C is fussy about timing, but the response time seems quick when I use firefox, so I don’t think it’s a problem of lagging.
What version? We do block request where the user agent indicates it using a Chrome version < 120, you’d be surprised how many malicious scrappers do this. The other possibility is that your Tor exit node is in one of the IP ranges we block for the same reason.
I just tried again on Android and it works fine, which is annoying. So I think it might be the exit node thing.
My version is older than 120.
It’s very repeatable, so exit node would not be at issue. I guess the user agent string is being rejected.