docker-jackett VS FlareSolverr

I can't get this container to launch, in the logs the access error in repeatedly printed:

Where did you get the docker-compose.yml from? Post the link. Also, why are you not using the one from the linuxserver if you are using their container? https://github.com/linuxserver/docker-jackett

So I'm running docker with portainer and I'm having issues getting the port number right. I set up my VPN in a container then I set up jackett and qBitTorrent. I want jackett and qBitTorrent to run through my VPN but I'm having issues with the port numbers jackett needs port 9117 and qBitTorrent needs 8080 how do I set my VPN up so they both go through it?

# https://github.com/linuxserver/docker-jackett jackett: container_name: jackett environment: PGID: $PLEX_PGID PUID: $PLEX_PUID TZ: $TZ image: lscr.io/linuxserver/jackett networks: smarthome: ipv4_address: 172.18.0.16 restart: always volumes: - $USERDIR2/jackett:/config

I always sort of assumed it was related to my set up, but it looks like some folks have had a similar problem with Jackett docker images on their own here. Gonna try the suggested alternative image and see if that helps.

https://github.com/linuxserver/docker-jackett/issues/72#issuecomment-468859532

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.