FlareSolverr VS node-red-docker

What i didnt tried: - scraping and using these (single page) tokens - headless browser - web-test-frameworks like selenium (programmable browser) - using Flaresolver (my best bet) https://github.com/FlareSolverr/FlareSolverr . A headless browser / proxy developed to bypass cloudflare. You can easily deploy it onprem with docker. I know google got its own defence machanisms, but i've got very good experience using it for scraping and crawling (at least cloudflare protected) websites. So i guess its very good at pretending being a normal browser, being a normal user.

Prowlarr & Flaresolverr to handle indexers for Radarr/Sonarr.

In terms of rate limiting and IP bans there is always that possibility on a VPN and it does happen but that's the great thing about VPNs is you can always just swap servers. On an automated server like a nas, a server restart will take care of this issue but of course until that happens some indexers may have issues. But the great thing is we have things like flaresolverr now which can mitigate these rate limit and captcha issues with various websites and I highly recommend people take a some time to set it up. How I see it if you are using a residential IP that never changes, the risk of rate limiting or IP bans becomes more of an issue because it is longer lasting or permanent. So in my opinion the security and privacy benefits of a VPN outweighs the possibility of some minor hiccups.

gtthub

FlareSolverr est un serveur proxy permettant de contourner la protection de Cloudflare. gtthub

https://github.com/FlareSolverr/FlareSolverr Had to do a fair bit of debugging to find the code level changes, but you just have to update two sections.

You could also use a Cloudflare bypass tool like FlareSolverr, which is a proxy server you can use to bypass Cloudflare and DDoS-GUARD protection.

Feb 14 16:16:31 podhost podman\3483]: 2023-02-14 16:16:31.053466474 -0300 -03 m=+0.071815344 container health_status 2177a7448029695a17a9c0c774b8f48875bda76f6bf6e100254532765c6005d7 ()image=docker.io/nodered/node-red:3.0.2-18, name=nodered, health\status=unhealthy, org.label-schema.build-date=2022-08-04T13:19:34Z, org.label-schema.docker.dockerfile=.docker/Dockerfile.alpine, org.label-schema.vcs-type=Git, org.label-schema.license=Apache-2.0, org.label-schema.name=Node-RED, authors=Dave Conway-Jones, Nick O'Leary, James Thomas, Raymond Mouthaan, org.label-schema.vcs-url=https://github.com/node-red/node-red-docker, org.label-schema.version=3.0.2, org.label-schema.arch=, org.label-schema.description=Low-code programming for event-driven applications., org.label-schema.url=https://nodered.org, org.label-schema.vcs-ref=))

I found that Nick O'Leary (founder of Node-RED and the great guy that he is..) already did some research on this, I just had to bring this all together.

I don't use node-red, but I guess they use the node-red user in shell and overriding the process owner causes some issues with that. You can add an issue to their repository if you want.

Standard practice with Node-Red lets the user add dedicated flows and dependencies via the npm install command-line. However within the Node-Red-Docker Repo Wiki, you can also add these flows/dependencies via a dedicated package.json.

# https://nodered.org/docs/getting-started/docker # https://community.home-assistant.io/t/node-red-get-homeassistant-error/53923 node-red: container_name: node-red depends_on: homeassistant: condition: service_started environment: PGID: $PGID PUID: $PUID TZ: $TZ image: nodered/node-red networks: smarthome: ipv4_address: 172.18.0.2 restart: always # https://github.com/node-red/node-red-docker/wiki/Permissions-and-Persistence # chown volume after first run volumes: - $USERDIR2/node-red:/data

Node Red - Flow programming, mainly for IOT