FlareSolverr VS docker-pihole-unbound

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.

I'm running the chriscrowe 'one container' build for pihole for ad-blocking (https://github.com/chriscrowe/docker-pihole-unbound), and unbound for private recursive DNS which is running great on my Zima board.

I believe my problem stems from when I tried to install the pihole-unbound container (https://github.com/chriscrowe/docker-pihole-unbound)

I've got lucky enough that I could get in Nov-19 a Raspberry Pi 4 with 4GB of RAM that I use as a NAS+Pi-Hole + Unbound +Other stuff (running Void MUSL of course) and instead of an SD I use an HDD for the OS + a 5TB HDD for the data and even fully loaded all cores it barely consumes more than 22W.

I was only able to get pihole macvlan approach working with an ssh access + docker-compose approach. I used the crowe one-container approach Still had to enable Open vSwitch for the network in Synology first.

You can follow the doc to do those install steps within your own Dockerfile. Or you can use the commonly recommended chriscrowe image, which does what I’m describing.

When I started experimenting with this topic chriscrowe's was a baseline for stuff that I tryed out, so kudos to chris!

It seems you’re looking at a wrong file. Here is a docker file for one-container solution: https://github.com/chriscrowe/docker-pihole-unbound/blob/55c88afaf8d76958923adc38f4c12a80e1cb9084/one-container/pihole-unbound/Dockerfile

2) you can use something like this maintained GitHub repo. Just decide if you want to use 1 or 2 containers and modify the ip and gateways, etc accordingly.