Cloudflare challange problem #500
Labels
No labels
MediaFlow Proxy
autorelease: pending
autorelease: tagged
bug
documentation
duplicate
enhancement
help wanted
invalid
question
wontfix
🇩🇪 German
🇫🇷 French
🇮🇳 Indian
🇸🇦 Arabic
🌐 Multi
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Creepso/webstreamr-github#500
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi
How to deal with sources that use cloudflare challange and the direct fetch to search and get embeds doesn't work?
I see somewhere in the fetcher.ts you detect flaresolverr and i tried but it doesn't seem to work on a website I am trying.
There is any other way?
Flareaolver or byparr needs to be running and its url can be configured via env var. There is some rudimentary support for it here. But it does not work reliable IMO and, as I said before alread, this is completely unusable for a public instance because of how bad it performs. I currently have no interest in further looking into cloudflare captcha protected sources. They are not worth it at the moment.
But I wanted to check if the cf cookie usage works better now or can be fixed. That would be a potential working solution that might perform OK.
How to get the cf cookie without flaresolverr? Do you support this already or?I want to try...
Also does you detect also username and password for flaresolverr istance
I am trying this site `
I am using the flaresolverr and I am able to get the search I am able to get the movie link but not the embeds...When I try with curl I am able to get the embeds.
Before the cloudflare challange I was able to get the embeds with my existing code
I was getting the embeds creating a post to get the data like this
"It constructs a POST request to /wp-admin/admin-ajax.php with DooPlay parameters (action=doo_player_ajax, post, nume, type).
The response.embed_url is extracted and returned as a SourceResult."
But using flaresolverr now doesnt work
p.s the site might work well for you without the challange...it's ip based because I've tried alot with this website and now it turned the cloudflare on
Trying with curl at home with some headers works ...maybe only on vercel ip was turned on the challange I guess
I found the problem. It was the headers.
I just added some headers on fetcher.text call and also on json() calls and now is not triggering anymore the cloudflare...