Furaffinity Cloudflare Block (403 Forbidden)

[soskamified]

I've been attempting to bypass the cloudflare challenge for Furaffinity but to no avail. I've looked up prior discussions regarding this, but the main solution is to simply wait for it to go away, but I feel like this can't be the solution. There was also an old guide which require an "a" and a "b" cookie, but after trying this method, I still am receiving the blocked message. Has anyone been able to get past this error message? Note that I have also tried to manually export the cf_clearance cookie to the config file, but this still did not work.

[unknowner00]

Just started having this issue as well

[FlashFried]

Same.

[featherbutt]

This started last night for me. I tried using the extractor.*.browser setting to mimic firefox's headers, ciphers, and user-agent, but this had no effect, so the Cloudflare challenge doesn't seem to be solely based on headers.

[mikf]

Let your browser solve the challenge, then pass its cookies and User-Agent to gallery-dl:

$ gallery-dl -a browser --cookies-from-browser firefox https://www.furaffinity.net/view/21835115/
[cookies][info] Extracted 3 cookies from Firefox
./furaffinity/mirlinthloth/21835115 Bude's 4 Ever.mp3

$ gallery-dl https://www.furaffinity.net/view/21835115/
[furaffinity][warning] Cloudflare challenge
[furaffinity][error] ChallengeError: Cloudflare challenge (403 Forbidden) for 'https://www.furaffinity.net/view/21835115/'

[soskamified]

I must be doing something wrong, because I've tried this and it still did not work. It stated that the a and b cookies were not set, and then the request was blocked again.

[quentinwolf]

I began experiencing the same issue, although I'm unable to use the "browser --cookies-from-browser" argument since my usage is on a headless server. Up until now I was exporting my cookies (a, b, and cf_clearance) and loading that cookie file in the .gallery-dl.conf under "furaffinity" with the option

"cookies": "/path/to/cookies.file"

However about 2 days ago, I noticed it began to only work 50% of the time, the other 50% of the time it threw the Cloudflare challenge warning, and then it seems in the last day it's now throwing the Cloudflare challenge warning 100% of the time.