[Bug]: Nothing works due to Cloudflare check #10
Comments
|
Yes, it is caused by the CloudFlare challenge on FA. Alas there is nothing that can be done on this side. I have already updated the FAAPI class to take a You can also take a look at #9. The problem was the same and we solved it by manually changing the cookies in a browser to "whitelist" the IP. |
|
Duplicate of #9 |
|
Thank for the suggestion of a CloudFlare-specific exception, I will add it. |
|
Yup, FA was under cloudflare anti-bot protection for about 12 hours today (and 8 hours on a couple previous days) It should be available again now though |
|
Thanks for the update @Deer-Spangle :) I re-ran the tests and it is working again now! |
Version
3.11.3
What happened?
Hello, today I tried to use FAAPI and discovered that it stopped working.
Any request I make upon FAAPI ends with a
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: [...]1 exception. Looking into the response gotten from the server, I can see that the content of the response starts with<!DOCTYPE html><html lang="en-US"><head><title>Just a moment...</title>, which corresponds to a Cloudflare challenge.I don't know whether this is because FA changed something in their hosting to require all visitors to pass the challenge,2 or whether FA is singling my connection for these checks, but in either case, I do think that FAAPI should at least throw a better error so the user can see that a Cloudflare check is preventing FAAPI from working because, as of now, the error thrown is a simple 403, which can mean many things.
How to reproduce the bug?
Try to do anything that sends a request to FA.
Relevant log output
No response
Footnotes
[...]in excerpt signifies omisison. ↩It seems so, because testing on my two devices, I always get the challenge when trying to access FA. ↩
The text was updated successfully, but these errors were encountered: