FlareSolverr: ygg torrent can't be add on prowlar or jackett
Have you checked our README?
- I have checked the README
Have you followed our Troubleshooting?
- I have followed your Troubleshooting
Is there already an issue for your problem?
- I have checked older issues, open and closed
Have you checked the discussions?
- I have read the Discussions
Environment
- FlareSolverr version: 3.3.10
- Last working FlareSolverr version:
- Operating system:Debian 12
- Are you using Docker: [yes/no] no
- FlareSolverr User-Agent (see log traces or / endpoint):
- Are you using a VPN: [yes/no] yes
- Are you using a Proxy: [yes/no] no
- Are you using Captcha Solver: [yes/no] no
- If using captcha solver, which one:
- URL to test this issue:
Description
Hello, for about 3 weeks I have had this error message when I try to add ygg. When I go by cookie it works but not for long. Otherwise by torrent I have this error. I tried different version of flaresolverr.
Unable to connect to indexer, indexer’s server is unavailable. Try again later. HTTP request failed: [500:InternalServerError] [POST] at [http://localhost:8191/v1]
flaresolverr.service - flaresolverr Loaded: loaded (/etc/systemd/system/flaresolverr.service; enabled; preset: enabled) Active: active (running) since Wed 2023-11-15 13:04:52 EST; 19h ago Main PID: 45604 (flaresolverr) Tasks: 6 (limit: 38207) Memory: 210.5M CPU: 4min 22.897s CGroup: /system.slice/flaresolverr.service ├─45604 /home/jonathan/flaresolverr/flaresolverr └─45629 Xvfb :151124646 -screen 0 800x680x24
nov 15 15:14:45 jonathan flaresolverr[45604]: 2023-11-15 15:14:45 INFO Response in 0.797 s nov 15 15:14:45 jonathan flaresolverr[45604]: 2023-11-15 15:14:45 INFO 127.0.0.1 POST http://localhost:8191/v1 200 OK nov 15 21:15:16 jonathan flaresolverr[45604]: 2023-11-15 21:15:16 INFO Incoming request => POST /v1 body: {‘maxTimeout’: 60000, ‘cmd’: ‘request.get’, ‘url’: ‘https://prowlarr.servarr.com/v1/ping’, ‘proxy’: > nov 15 21:15:16 jonathan flaresolverr[45604]: 2023-11-15 21:15:16 INFO Challenge not detected! nov 15 21:15:16 jonathan flaresolverr[45604]: 2023-11-15 21:15:16 INFO Response in 0.817 s nov 15 21:15:16 jonathan flaresolverr[45604]: 2023-11-15 21:15:16 INFO 127.0.0.1 POST http://localhost:8191/v1 200 OK nov 16 03:15:42 jonathan flaresolverr[45604]: 2023-11-16 03:15:42 INFO Incoming request => POST /v1 body: {‘maxTimeout’: 60000, ‘cmd’: ‘request.get’, ‘url’: ‘https://prowlarr.servarr.com/v1/ping’, ‘proxy’: > nov 16 03:15:43 jonathan flaresolverr[45604]: 2023-11-16 03:15:43 INFO Challenge not detected! nov 16 03:15:43 jonathan flaresolverr[45604]: 2023-11-16 03:15:43 INFO Response in 0.858 s nov 16 03:15:43 jonathan flaresolverr[45604]: 2023-11-16 03:15:43 INFO 127.0.0.1 POST http://localhost:8191/v1 200 OK
Logged Error Messages
2023-11-15 08:01:40.9|Warn|ProwlarrErrorPipeline|Invalid request Validation failed:
-- : Unable to connect to indexer, indexer's server is unavailable. Try again later. HTTP request failed: [500:InternalServerError] [POST] at [http://localhost:8191/v1]
2023-11-15 08:02:00.6|Info|Auth|Auth-Success ip ::1 username
Screenshots
No response
About this issue
- Original URL
- State: closed
- Created 8 months ago
- Comments: 24 (11 by maintainers)
I had already tried to mount it to 120 in prowlar, but to no effect. For now I’m going to assume that it may be because of the update I did to Debian 12. It seems to be an isolated case. I will continue with docker it does the job.