RSS-Bridge / rss-bridge

The RSS feed for websites missing it
https://rss-bridge.org/bridge01/
The Unlicense
7.19k stars 1.02k forks source link

Use of Flaresolverr #3582

Open Draky50110 opened 1 year ago

Draky50110 commented 1 year ago

Hello.

What about using a selfhosted flaresolverr install to resolve Cloudflare problems ?

I have installed it with Docker, and using another script, it uses this to resolve Cloudfare access.

Maybe could be used to solve all bridges not working like Yggtorrent one.

Flaresolverr : https://github.com/FlareSolverr/FlareSolverr

Bockiii commented 1 year ago

We've investigated flaresolverr before and judged that it would be out of scope to implement it into the base container.

You can add a proxy server to the config. Have you tried that?

enchained commented 1 year ago

What about supporting it as an optional sidecar container instead of integrating into the base one? I did not encounter Cloudflare issues with bridges yet, but FlareSolverr seems like a more universal solution to Cloudflare protection issues vs using a proxy.

Bockiii commented 1 year ago

Again.. Proxy usage is already an option in the rssbridge settings. You can just test it.

dr0id123 commented 6 months ago

Ran into FlareSolverr as well. It's definitely do-able. Here's my working example:

https://gist.github.com/dr0id123/2863a821b8bf35864f977a3eb9dface4

thomas-333 commented 5 months ago

Ran into FlareSolverr as well. It's definitely do-able. Here's my working example:

gist.github.com/dr0id123/2863a821b8bf35864f977a3eb9dface4 (too large to embed)

Thanks for posting this. Is there a particularly reason for:

//Save in cache for 7 days
$this->saveCacheValue($key, $html, 604800);

As 7 days seems like a very long time?

dr0id123 commented 5 months ago

It's not required -- you can use default caching mechanisms.

For a shorter way to call Flaresolverr see: https://gist.github.com/dr0id123/17faa66b365f37546d93bd5f033759e3

Ran into FlareSolverr as well. It's definitely do-able. Here's my working example: gist.github.com/dr0id123/2863a821b8bf35864f977a3eb9dface4 (too large to embed)

Thanks for posting this. Is there a particularly reason for:

//Save in cache for 7 days
$this->saveCacheValue($key, $html, 604800);

As 7 days seems like a very long time?

thomas-333 commented 5 months ago

Thanks for sharing.

I will experiment on some feeds myself.

thomas-333 commented 5 months ago

@dr0id123

Thanks, I have your code running. I don't suppose you have a version of the CSS Selector Feed Expander bridge using Flaresolverr as this will be easier than creating a custom bridge per site?

dr0id123 commented 5 months ago

No I haven't. Should be straight-forward for you to modify the code...

I personally would not apply flaresolverr to the entire bridge (meaning for any site), given the overhead of it. Probably good idea to make the use of flaresolverr selectable as an option.

@dr0id123

Thanks, I have your code running. I don't suppose you have a version of the CSS Selector Feed Expander bridge using Flaresolverr as this will be easier than creating a custom bridge per site?

Bockiii commented 5 months ago

the problem is that bridges have and use different types of getting the content. getSimpleHTMLDOM, getContents, some straight up use curl etc. So either you would have to option all of those or try to catch it at a different point.

I hoped that flaresolver would just work if you put it into the proxy setting, but testing it on my firefox install (and reading through their doc) it doesnt seem to work like that. If you find a solution for that, you would only have to install flaresolver and aim the proxy setting at it.

thomas-333 commented 5 months ago

Does anyone have an example of a site protected by CF that the current CSS Selector Feed Expander bridge doesn't work?

I'm struggling finding one for testing. VideoCardz works fine for me using the normal bridge.

Bockiii commented 5 months ago

NOTE: Web browsers consume a lot of memory. If you are running FlareSolverr on a machine with few RAM, do not make many requests at once. With each request a new browser is launched.

from the flaresolvrr github page. If you try to do that for a bridge, your server will likely explode. Many bridges do hundreds of requests (for content, images, deeplinking etc). Thats going to be basically impossible.

Hufschmidt commented 4 months ago

Does anyone have an example of a site protected by CF that the current CSS Selector Feed Expander bridge doesn't work?

I'm struggling finding one for testing. VideoCardz works fine for me using the normal bridge.

For me trying to access patreon is currently not possible, eg. https://www.patreon.com/deZigner/posts Getting the old "The website is protected by CloudFlare", maybe that helps your testing. :+1:

BryanWall commented 1 week ago

Does anyone have an example of a site protected by CF that the current CSS Selector Feed Expander bridge doesn't work?

I'm struggling finding one for testing. VideoCardz works fine for me using the normal bridge.

I found this thread because Cloudflare started blocking the CSS Selector Complex Bridge on happyscripe.com (it's a site with podcast transcripts). It was working previously, so I don't know if they recently added Cloudflare to the site, or something changed.

Here's an example URL from the site: https://www.happyscribe.com/public/the-daily