You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing open and closed issues
Is your feature request related to a problem? Please describe
The problem is that I'm in a country where indexers like 1337x.to are blocked.
While this is an easy problem to solve knowing that I have a NordVPN subscription, I can easily use my account to enable a Socks5 general proxy in prowlarr but the problem is that 1337x.to now has a cloudflare protection.
To solve the cloudflare problem, I had to use FlareSolverr as stated.
FlareSolverr is not using the general proxy defined in prowlarr which leads back to the first problem of 1337x.to is blocked in my country.
I checked the code that is related to the proxy to FlareSolverr and it's explicitly stating to ignore the proxy if there is a username and password which is the core of the problem
I would like for the prowlarr to actually send the username and password of the proxy to flaresolverr because flaresolverr explicitly supports that. @
Describe alternatives you've considered
I have considered using a docker vpn container like GluetunVPN and then changing the default gateway for flaresolverr to go through the VPN but it's not a straight forward operation and the whole problem could be easily solved.
First of all, thank you for the fast response and the quick implementation. Appreciate it.
Regarding the HTTPS_PROXY, I didn't know that docker supports that natively, I was looking into flaresolverr environment variables to find something like this.
Thank you again !
Is there an existing issue for this?
Is your feature request related to a problem? Please describe
The problem is that I'm in a country where indexers like 1337x.to are blocked.
While this is an easy problem to solve knowing that I have a NordVPN subscription, I can easily use my account to enable a Socks5 general proxy in prowlarr but the problem is that 1337x.to now has a cloudflare protection.
To solve the cloudflare problem, I had to use FlareSolverr as stated.
FlareSolverr is not using the general proxy defined in prowlarr which leads back to the first problem of 1337x.to is blocked in my country.
I checked the code that is related to the proxy to FlareSolverr and it's explicitly stating to ignore the proxy if there is a username and password which is the core of the problem
Describe the solution you'd like
I would like for the prowlarr to actually send the username and password of the proxy to flaresolverr because flaresolverr explicitly supports that. @
Describe alternatives you've considered
I have considered using a docker vpn container like GluetunVPN and then changing the default gateway for flaresolverr to go through the VPN but it's not a straight forward operation and the whole problem could be easily solved.
Anything else?
The line that needs a change
https://github.com/Prowlarr/Prowlarr/blob/develop/src/NzbDrone.Core/IndexerProxies/FlareSolverr/FlareSolverr.cs#L107
https://github.com/Prowlarr/Prowlarr/blob/develop/src/NzbDrone.Core/IndexerProxies/FlareSolverr/FlareSolverr.cs#L213
flaresolverr support for Socks5 with auth
https://github.com/FlareSolverr/FlareSolverr?tab=readme-ov-file#-sessionscreate
The text was updated successfully, but these errors were encountered: