New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot signin : bot detected #187
Comments
My first thoughts:
Any other ideas ? |
Actually, the error occurs right away on the first code, we don't even get the chance to submit the 2FA code. |
The following works, not sure why it doesn't work with requests yet.
Translating this request exactly to |
@nmathey @MadeInPierre |
Note that even with httpx running from github actions doesn't work... clerk detects a bot. |
Moving away from requests shouldn't be a problem for me. |
Yes, the tests don't work from Github Actions server but they run fine from my home computer. You can try to signin with the main branch (and should get the bot detected error) and with this branch and you should get success. |
Got same error
Did your branch includes all headers additions you tested with curl?
|
See https://community.finary.com/t/api-finasync-extension-open-source/10104/24 for the current official status (by Finary CTO). The behavior described in this bug is "expected". For me, the HTTPX branch works. I tried several headers but of course, I made sure to use exactly the same one while testing. I had the same header in the main branch (using requests), with curl and with HTTPX (including forcing HTTP 1.1 when possible). Clerk does smart things for their bot detection for sure. For now, I would like to get more data. Does the main branch work for you ? Does the HTTPX branch work ? |
Sorry I'm bit confuse, and might be a dummy question, but can you confirm headers you successfully tested are hardcoded in your Httpx branch? |
@nmathey they aren't hardcoded but the HTTPX branch works for my laptop as it, without configuring anything. |
Hey!
I was using this repo as a reference for implementation (thanks for the awesome work btw), and I naively tried to set my user-agent to:
I haven't tried anything else since then, but my guess is that Clerk detects http clients that try to behave like browsers as they're probably bots most of the times, and allows clients that are transparent and saying that they're an API. So basically, I don't think it's an issue related to the http client, but it's probably linked to headers. Hope those information can help you! |
See https://community.finary.com/t/api-finasync-extension-open-source/10104/20
After a call to
signin
we getThe text was updated successfully, but these errors were encountered: