Overview: Support for Docker image arch-flaresolverr in the binhex repo.

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

Docker Hub: https://hub.docker.com/r/binhex/arch-flaresolverr/

GitHub: https://github.com/binhex/arch-flaresolverr

Documentation: https://github.com/binhex/documentation

 

If you appreciate my work, then please consider buying me a beer 😁

 

 

For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here

reserved

Hey, hey,

First of all: thanks @binhex for all that work!
Insane what you are pulling off and make available.
Thank you so much for that!

I'm still new to the whole Home-Server, Docker and Unraid business.
And even though I try to read through most of the documentation I do sometimes lose track of why something might not work in the end.
Most of it all is still a new language to me.

 

So, I thought I was on a good track with Prowlarr, Sonarr and friends but now require flaresolverr in order to use them.
When I start flaresolverr however, the webUI shows the following:
 

error: "Method not allowed."
status_code: 405

 

I already installed python pack 3 but am kind of lost how to get it up and running.

Installing Ungoogled-Chromium also didn't seem to help.

 

Any idea or hint what the issue might be and how to solve it?

41 minutes ago, IMACRAB said:

When I start flaresolverr however, the webUI shows the following:

There is no webui for this image, it is purely command line and there is nothing to configure on the flaresolverr end, you simply point prowlarr/jackett at flaresolverr and you are done.

 

i am using this myself, an example setup defined in prowlarr:-

 

once defined here you then add 'tags' to each index site which then links it to flaresolverr.

For completeness here is what the Jackett configuration looks like for Flaresolverr, just go to Jackett WebUI scroll down to 'Jackett Configuration' and configure the URL for Flaresolverr, e.g.:-

8 hours ago, binhex said:

For completeness here is what the Jackett configuration looks like for Flaresolverr, just go to Jackett WebUI scroll down to 'Jackett Configuration' and configure the URL for Flaresolverr, e.g.:-

Thanks for coming back to me on this!

That's very odd, because that is exactly what I did.

I did not change anything throughout the installation of FlareSolverr either.

And I got the following error from prowlarr when clicking to 'test':

1 minute ago, IMACRAB said:

Thanks for coming back to me on this!

That's very odd, because that is exactly what I did.

I did not change anything throughout the installation of FlareSolverr either.

And I got the following error from prowlarr when clicking to 'test':

are you sharing networkkng with another container, for example vpn container? if you are and you are using one of my images then you will need to define the port in/out (depeds on setup).

What would be a good way to figure that out?
I'm currently using mostly images made by you.

That includes:

• FlareSolverr
• Prowlarr
• Sonarr
• QBitTorrent <- I should have succeeded to get my VPN up and running for this one

 

18 hours ago, IMACRAB said:

What would be a good way to figure that out?

do this:-

 

Left click the prowlarr container and select 'Edit', make any change to a value, then switch it back to what it was and click on 'Apply', then copy and paste the 'Command execution' shown to a file, ensuring to remove any reference to username and password, then attach the file here.

On 3/5/2024 at 4:17 PM, binhex said:

do this:-

 

Left click the prowlarr container and select 'Edit', make any change to a value, then switch it back to what it was and click on 'Apply', then copy and paste the 'Command execution' shown to a file, ensuring to remove any reference to username and password, then attach the file here.

Thanks for the tip.
Is it this one?
 

docker run
  -d
  --name='binhex-prowlarr'
  --net='bridge'
  -e TZ="Europe/Paris"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Gordon"
  -e HOST_CONTAINERNAME="binhex-prowlarr"
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:9696]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/prowlarr-icon.png'
  -p '9696:9696/tcp'
  -v '/mnt/user/appdata/binhex-prowlarr':'/config':'rw' 'binhex/arch-prowlarr'
e55bf9753161d07da6aeb272004338a0f3b9fea8b369d53840417411057cf307

The command finished successfully!

 

On 3/6/2024 at 9:57 PM, IMACRAB said:

Thanks for the tip.
Is it this one?
 

docker run
  -d
  --name='binhex-prowlarr'
  --net='bridge'
  -e TZ="Europe/Paris"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Gordon"
  -e HOST_CONTAINERNAME="binhex-prowlarr"
  -e 'UMASK'='000'
  -e 'PUID'='99'
  -e 'PGID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:9696]/'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/prowlarr-icon.png'
  -p '9696:9696/tcp'
  -v '/mnt/user/appdata/binhex-prowlarr':'/config':'rw' 'binhex/arch-prowlarr'
e55bf9753161d07da6aeb272004338a0f3b9fea8b369d53840417411057cf307

The command finished successfully!

 

sorry i completely forgot about this post!, the above looks fine and i can see its using 'bridge' and not sharing the network with any vpn docker containers, so i am puzzled as to why prowlarr cannot connect, the URL you are entering into prowlarr for the 'host' is that the ip address of your unraid server, right?.

 

 

On 3/15/2024 at 12:07 AM, binhex said:

sorry i completely forgot about this post!, the above looks fine and i can see its using 'bridge' and not sharing the network with any vpn docker containers, so i am puzzled as to why prowlarr cannot connect, the URL you are entering into prowlarr for the 'host' is that the ip address of your unraid server, right?.

 

 

Hey, hey,

 

I was off for a moment myself - thanks for looking into it again.

Yes, it's the IP address of my Unraid Server.

For reference, prowlarr uses the exact same address, but with a :9696 at the end.

 

The :8191 is also not used by any other docker.

15 hours ago, IMACRAB said:

Hey, hey,

 

I was off for a moment myself - thanks for looking into it again.

Yes, it's the IP address of my Unraid Server.

For reference, prowlarr uses the exact same address, but with a :9696 at the end.

 

The :8191 is also not used by any other docker.

ok then im out of ideas, all i can say is i use this image and it works for me *shrug*.

On 3/26/2024 at 10:28 AM, binhex said:

ok then im out of ideas, all i can say is i use this image and it works for me *shrug*.

 

Hey, hey,

 

I looked into it again and both yours and also the 'official' docker didn't work initially.

After ticking off the 'Use Proxy' options within prowlarr it worked however.

Would you know if I just misconfigured the Proxy options for prowlarr in that case or was it never meant to work with 'Use Proxy' turned on?

 

These were my options:

 

Thanks again for your help!

i am getting the error pictured.  i havent changed anything.  any ideas? thank you!

I've installed the flaresolverr container on the same container network as the delugevpn container. I added the following to the delugevpn container:  -p 8191:8191 \ to open the flaresolver port "through the vpn". It all works, but the issue is the flaresolver requests take over 200 seconds to return and the max timeout in prowlar that can be set is 180. It's almost like it takes a very long time for the requests to travel through the VPN. I want to keep this behind the VPN since flaresolver would make requests to the indexer sites directly (i think, correct me on this if im wrong).
PS: I do have kind of an unconventional set up where I run Ubuntu server (headless) on proxmox and installed docker on that with all the containers. With the exception of overseerr, everything is behind the VPN and so far has functioned without any issues. 

PPS: Sounds like there was some issues on the official flaresolverr github: https://github.com/FlareSolverr/FlareSolverr/issues/1253 not sure if this is related

6 hours ago, minihq said:

I've installed the flaresolverr container on the same container network as the delugevpn container. I added the following to the delugevpn container:  -p 8191:8191 \ to open the flaresolver port "through the vpn". It all works, but the issue is the flaresolver requests take over 200 seconds to return and the max timeout in prowlar that can be set is 180. It's almost like it takes a very long time for the requests to travel through the VPN. I want to keep this behind the VPN since flaresolver would make requests to the indexer sites directly (i think, correct me on this if im wrong).
PS: I do have kind of an unconventional set up where I run Ubuntu server (headless) on proxmox and installed docker on that with all the containers. With the exception of overseerr, everything is behind the VPN and so far has functioned without any issues. 

PPS: Sounds like there was some issues on the official flaresolverr github: https://github.com/FlareSolverr/FlareSolverr/issues/1253 not sure if this is related

Check the dns for the delugevpn container, i have seen slow response from DNS watch NS's so try removing 84.200.xxx.xxx from NAME_SERVERS, also ensure you stop all containers running through delugevpn before doing this or unraid gets it's knickers in a twist.

I will give this a shot. I'm using the NS's that you list in your instructions, are there any others that i could use? Or do I even need to? Right now i have 6 NSs and two of them are DNS watch. And yea, I've learned any time I make any change to the main vpn container I stop all of the others. I re-create all the containers directly through the ubuntu cli, but manage them via portainer. I really need to figure out compose

Removing the DNS didn't help, still timing out.

@binhex - I am also having timeout issues.

 

The issue started yesterday but has been working for well over a month

Are you running flaresolverr via VPN shared network? If so the timeout is probably due to failed VPN connection, restart the VPN container in that case.

Hi @binhex I'm using regular Flaresolverr container right now on my unraid and it can't handle two providers (torrentleech.pl and torrentleech.org) for some time because cloudflare protection. Is it possible that Your version binhex-flaresolverr will work with them?
Regards.

 

On 9/28/2024 at 4:04 AM, binhex said:

Are you running flaresolverr via VPN shared network? If so the timeout is probably due to failed VPN connection, restart the VPN container in that case.

 

@binhex Negative, I am not running via a VPN shared network.  The issue does have a solution here but I don't know how to find/access and edit the specific file 'flaresolverr_service.py'.  Can you assist with how to access/edit a file inside of a docker container within Unraid?

18 hours ago, ramjam824 said:

 

 

@binhex Negative, I am not running via a VPN shared network.  The issue does have a solution here but I don't know how to find/access and edit the specific file 'flaresolverr_service.py'.  Can you assist with how to access/edit a file inside of a docker container within Unraid?

That patch won't work for the this version of the image as i am currently including the pre-compiled binary, if it's still broken by Monday then i will consider switching to running the scripts directly and including the patched file, wonder why the dev's are reticent to include it if it fixes the issue?. 

7 hours ago, binhex said:

That patch won't work for the this version of the image as i am currently including the pre-compiled binary, if it's still broken by Monday then i will consider switching to running the scripts directly and including the patched file, wonder why the dev's are reticent to include it if it fixes the issue?. 

 

That will be greatly appreciated!  I am unsure as to why the update hasn't been merged into the main version and there hasn't been an update since June.