search

DyonR / docker-Jackettvpn

Docker container which runs a headless Jackett Server with an optional WireGuard or OpenVPN connection
https://hub.docker.com/r/dyonr/jackettvpn/
GNU General Public License v3.0
68 stars 32 forks source link

JacketVPN + FlareSolverr #42

Closed ghost closed 3 years ago

ghost commented 3 years ago

Hello,

I'm desperately trying to add FlareSolverr to JacketVPN. I tunneled FlareSolverr to JacketVPN but I can't access to the FlareSolverr UI.

I use unraid and both docker version of JackettVPN and FlareSolverr.

image

Do you know a procedure which works ? Thank you !

DyonR commented 3 years ago

I will see if I can reproduce this and see what might be wrong
Which FlareSolverr image do you use? Just the one from DockerHub like this? Unraid > Apps > [Search] FlareSolverr > Results From DockerHub >flaresolverr

DyonR commented 3 years ago

Using the Docker Image I posted above, it works for me.
Did you add another port to jackettvpn?

image

ghost commented 3 years ago

Thanks for your answer !

Yes I use FlareSolverr from docker hub (flaresolverr/flaresolverr).

And yes I added additional port on JackettVPN. I have a timeout when I want to access to FlareSolverr API (IP:8191).

I’m not at my home, I’ll double check settings ASAP.

DyonR commented 3 years ago

Alright! Let me know 😄
Actually, it might be something else! This are the 4 things I did to get it working:

ghost commented 3 years ago

Hey,

Sorry for the delay, I forgot to add port to ADDITIONAL_PORTS. Unfortunately, I still have a timeout :( I checked logs but I don't understand why isn't working :

image image

When I check : http://192.168.1.9:8191, I have a timeout after 20-30 s.

Can it be a problem with my VPN ? I use Windscribe, but no error when I check an indexer without FlareSolverr. So I think not.

ghost commented 3 years ago

Well I can't access JackettVPN UI anymore (timeout), that's odd.

DyonR commented 3 years ago

I also use Windscribe, so I don't think that will be the problem.
However, I did test it with wireguard instead of openvpn (why are you using openvpn when Windscribe provides wireguard config files?)
I don't see anything wrong with your Jackettvpn settings, but does your FlareSolverr have a 8191 port mapping?

ghost commented 3 years ago

Because I read experimental for Wireguard in JacketVPN :o I'll try to switch to wireguard.

I need to put a port on FlareSolverr container ?

ghost commented 3 years ago

Port 443 on Windscribe ?

DyonR commented 3 years ago

I also use Windscribe, so I don't think that will be the problem. However, I did test it with wireguard instead of openvpn (why are you using openvpn when Windscribe provides wireguard config files?) I don't see anything wrong with your Jackettvpn settings, but does your FlareSolverr have a 8191 port mapping?

Wait, my bad, I don't think that is the procedure indeed. I just woke up, my bad 😓

ghost commented 3 years ago

Lol no problem 😄

Switched to Wireguard (that's easier !), but no change. FlareSolverr doesn't tell me lot of thing : 

> flaresolverr@1.2.3 start
> node ./dist/index.js

2021-01-11T12:02:25.655Z INFO REQ-0 FlareSolverr v1.2.3 listening on http://0.0.0.0:8191
DyonR commented 3 years ago

Lol no problem 😄

Switched to Wireguard (that's easier !), but no change. FlareSolverr doesn't tell me lot of thing :

> flaresolverr@1.2.3 start
> node ./dist/index.js

2021-01-11T12:02:25.655Z INFO REQ-0 FlareSolverr v1.2.3 listening on http://0.0.0.0:8191

FlareSolverr shows me the exact same output if I check the logs. Are you still unable to connect to http://192.168.1.9:8191/

This is what my logs show after connecting to the IP+port;

> flaresolverr@1.2.3 start
> node ./dist/index.js

2021-01-11T12:10:35.655Z INFO REQ-0 FlareSolverr v1.2.3 listening on http://0.0.0.0:8191
2021-01-11T12:10:45.459Z INFO REQ-1 Incoming request: GET /
2021-01-11T12:10:45.459Z INFO REQ-1 Successful response in 0 s
2021-01-11T12:10:45.459Z INFO REQ-1 FlareSolverr is ready!
2021-01-11T12:10:45.569Z INFO REQ-2 Incoming request: GET /favicon.ico
2021-01-11T12:10:45.570Z ERROR REQ-2 Body must be in JSON format
DyonR commented 3 years ago

Can you also send the log of your jackettvpn?
There should be no private info in there, but be sure to quickly check it before sharing it.

ghost commented 3 years ago

Lol no problem 😄 Switched to Wireguard (that's easier !), but no change. FlareSolverr doesn't tell me lot of thing :

> flaresolverr@1.2.3 start
> node ./dist/index.js

2021-01-11T12:02:25.655Z INFO REQ-0 FlareSolverr v1.2.3 listening on http://0.0.0.0:8191

FlareSolverr shows me the exact same output if I check the logs. Are you still unable to connect to http://192.168.1.9:8191/

Yes unable to connect, to this IP:PORT

This is what my logs show after connecting to the IP+port;

> flaresolverr@1.2.3 start
> node ./dist/index.js

2021-01-11T12:10:35.655Z INFO REQ-0 FlareSolverr v1.2.3 listening on http://0.0.0.0:8191
2021-01-11T12:10:45.459Z INFO REQ-1 Incoming request: GET /
2021-01-11T12:10:45.459Z INFO REQ-1 Successful response in 0 s
2021-01-11T12:10:45.459Z INFO REQ-1 FlareSolverr is ready!
2021-01-11T12:10:45.569Z INFO REQ-2 Incoming request: GET /favicon.ico
2021-01-11T12:10:45.570Z ERROR REQ-2 Body must be in JSON format

Nothing added on logs when I'm trying to connect to IP;PORT

ghost commented 3 years ago

Can you also send the log of your jackettvpn? There should be no private info in there, but be sure to quickly check it before sharing it. Sure : https://privatebin.net/?dc8d53a72f1bc6f8#FenFa3yxN4L8ppocVmwt9iqaV7E7e6fubnLoSUGQnyFE

DyonR commented 3 years ago

Isn't your LAN Network supposed to be 192.168.1.0/24 instead of 192.168.0.0/24?

ghost commented 3 years ago

Thank you !!! That's that !

2021-01-11T12:32:31.304Z INFO REQ-0 FlareSolverr v1.2.3 listening on http://0.0.0.0:8191
2021-01-11T12:32:37.325Z INFO REQ-1 Incoming request: GET /
2021-01-11T12:32:37.325Z INFO REQ-1 Successful response in 0 s
2021-01-11T12:32:37.325Z INFO REQ-1 FlareSolverr is ready!
DyonR commented 3 years ago

Nice! It are always the small things you get stuck on 😝 Enjoy the container, if you have any issues, feel free to open up a new issue 😄