Replies: 1 comment
-
|
Cloudflare has always allowed configuration of the expiry of their cookies, usual range is from a few hours to a few days. If you have the indexer configured in Sonarr/Radarr for RSS search, then you're already periodically refreshing the cookie. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
After the recent Cloudflare update on turktorrent.us, FlareSolverr stops working again after about 1–2 hours.
I’m using FlareSolverr with Prowlarr, Sonarr, and Radarr.
Here’s what I noticed:
cf_clearancecookie anduser-agentand add them to FlareSolverr.Example cookie (partially hidden for privacy):
cf_clearance=LYTquI**********************;
tsue_member=CV8xNT**********************%3D%3D;
shoutboxChannelID=1
It looks like Cloudflare is invalidating the
cf_clearancetoken much more frequently now — maybe every 1–2 hours.Is there any workaround or configuration to handle these shorter clearance lifetimes?
Maybe a background auto-refresh or forced re-challenge option?
Thanks for your help!
Beta Was this translation helpful? Give feedback.
All reactions