Problem Flaresolverr in docker #1113
Labels
Comments
|
Working fine here. Follow the troubleshooting steps here - https://github.com/FlareSolverr/FlareSolverr/wiki/Troubleshooting If you still have issues, provide debug logs - https://github.com/FlareSolverr/FlareSolverr#environment-variables |
ilike2burnthing
added
the
more information needed
Hello, thank you for your response, here is the debug log to see if with this you could tell me what is happening. |
|
It's taking 30s to launch Chromium and another 45s to make the initial detection, which leaves no time to actually resolve the challenge. Is the device low powered, or have limited RAM available? Or have you limited the resources available to the container? |
|
I have the raspberry pi 3b+, with the dietpi system that adds swap memory with an extra 1gb. Is there anything I can do? Is there a lighter version of your plugin? |
|
You can try increasing the timeout, see if that makes a difference, but eventually Jackett/Prowlarr will timeout. |
Thank you for your help, it seems that something has improved because now I spend a lot of time looking for the challenge but I can't seem to find it. In both jackett and the docker installation, I increased the time by 200,000. I have thought if it does not solve something because of the language variable but I have it configured well (I think) this is my stack And the LOG |
|
Odd. Do you get the same result if you remove the |
|
I have applied the suggestions, the result is the same. I have also tried version 3.3.15 and 3.3.9 without success. new config: I am from Spain and flaresolverr works on Windows, could it be that cloudflare loads its protection in Spanish and has to load it in my language? I also sent screenshots of the portainer in case there was anything relevant. LOG PORTAINER DETAILS
|
|
The challenge detections are largely language agnostic, so it shouldn't matter what your system language is set to. The only case I've seen where it mattered was with YGGtorrent, where only English language systems could bypass the challenge, but that seemed to be Cloudflare thing rather than an issue with FlareSolverr. By all means, try |
|
Good morning. I have tried what we have talked about but it still does not work, the curious thing is that in Windows it does work, so I think it is possibly due to a limited hardware problem or that perhaps the Docker browser needs to be updated. If you have any further suggestions, I'm waiting. Anyway, thank you very much for getting so involved with my problem. |
ilike2burnthing
added
help wanted
|
Today I tested again and found this: The software seems to have issues when initializing the Chrome browser. The main error appears to be "cannot connect to chrome at 127.0.0.1:43839" and "UnboundLocalError: cannot access local variable 'driver' where it is not associated with a value". This suggests that the program is trying to access a local variable named 'driver' without it being associated with a value. The program also mentions a conversion problem with "version_main cannot be converted to an integer". This may indicate a data type error somewhere in the code where an integer is expected but another data type is being received. Additionally, in utils.py, there is an issue. It seems that there is an attempt to access a function 'convert_version' that either does not exist or is not defined correctly. |
|
By the way, I reinstalled Jackett outside of Docker. The tests from the other day were all in a Docker environment, so I'm not sure if this new error comes from there, but I wanted to run some tests. |
|
Either run both in Docker or both natively, don't mix them. The |
Thanks, I reinstalled Jackett outside of docker because at least then I can use flaresolverr from my Windows PC until there is a solution to this problem. Thanks for your help. |
|
Good morning. Today I have run again everything in docker and I get these errors I am very surprised by an error about a "driver" for example: |
|
I've been experiencing this issue as well. Set this up a while ago which it worked for a small amount of time, but then stopped working. Tried Jackett and Prowlarr with Flaresolverr, all running in docker. I'm running this on a raspberry pi 4. It never finds the captcha solver box. Running just FlareSolverr on a windows laptop resolves the captcha without issue. |
|
I just ran into this issue on a RPi 5. I changed the GPU memory from 16MB to 64MB using |
|
hi, The only difference i see: i'm on docker too but on a nuc I3 😅 |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Have you checked our README?
Have you followed our Troubleshooting?
Is there already an issue for your problem?
Have you checked the discussions?
Environment
Description
After trying all the solutions registered in this github and all the documents it seems that flaresolverr does not work correctly in docker.
I have done the tests on Windows 10 and it works well, it detects everything well.
I think the problem is that docker does not detect the challenge, I think other users have the same problem but I'm not sure.
Logged Error Messages
Screenshots
No response
The text was updated successfully, but these errors were encountered: