Build binaries for FlareSolverr 3 #660
Comments
|
Where's the precompiled version? |
|
check 3.0.0 changelog |
|
Is there a plan to provide the windows binaries for updates at all? Had an automated update process built around downloading those from the repo.. Would love to go back to that so I figured I would ask. |
|
Don't know why it has to be like this. It's not user-friendly this way. |
|
i did build an executable with pyinstaller but when i try to open it, it closes immediately. am i doing something wrong? should i need extra steps other than "pyinstaller flaresolverr.py" or "pyinstaller --onefile flaresolverr.py" opening with command works fine. i think it has to do with required packages, i tried different commands to include packages in the exe but no luck. error message: Traceback (most recent call last): |
|
@omerf111 I had the same error as you but have now got the binary executable working in Windows 10: The error is that flaresolverr.exe can't find package.json. I know, would be more helpful if the error message stated this. FlareSolverr runs fine from source with no errors so I noted where package.json was in relation to the src folder. They are both in the FlareSolverr-3.0.2 folder downloaded from Github - ie on the same folder level. But PyInstaller creates the dist folder as a subfolder of the src folder then creates another folder in dist called FlareSolverr where it creates the flaresolverr.exe and its other related files. So you need to move the flaresolverr.exe file and all its related files back to the same folder level relative to package.json. Move all the files in the dist>FlareSolverr folder to the dist folder. Then move the dist folder to the FlareSolverr-3.0.2 folder. This is what I did to get it working. |
This should be specified in the README.md... Right now for Windows it says that you download the zip from the release that contains the binaries. |
|
@DrStrange your solution doesn't work for me. Building from the root folder will have the following structure: And then when I list and run: While the FlareSolverr-3.0.2 contains the stuff from the zip. dist contains the .exe only, nothing else as you would suggest. And src for the sake of it. So frustrating... Initially I was running it in Do you mind clearing up your steps and commands to properly build this? |
Where?
https://github.com/FlareSolverr/FlareSolverr#precompiled-binaries |
|
@Zauxst Immediately after PyInstaller finishes creating the build files and before any files are moved, the Here is the build steps using PS for output which again results in a working build for me. I also list the versions of all the relevant programs and packages (requests and selenium are updates from requirements.txt). The paths for some of the Hope this helps you. I closed PS then reopened a new PS window at this point as the next command in PS caused an error stating that the file was in use. I closed PS then reopened a new PS window at this point as the next command in PS caused an error stating that the file was in use. Tree: Versions: |
|
@ilike2burnthing |
|
Feel free to submit a PR for the README. |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
If any windows user is having an issue with the missing package.json in the latest version 3.0.4. Just copy the package.json to the directory of dist or modify the |
|
Still no plans to include the binaries with further releases? |
|
PRs are always welcome. |
This comment was marked as abuse.
This comment was marked as abuse.
|
Assuming FlareSolverr is actually running it was extremely easy to set it up. Here is how
|
|
@Rumpa112, I am running Flaresolverr v3 in Windows using Python/Chrome/PyInstaller but since I don't use Python for anything else, I decided to try Docker. I have turned on virtualization, installed WSL and the kernel update, installed Docker Desktop, created a Docker account and am running the flaresolverr container and the logs show it running. However, when I open Microsoft Edge and type Thank you. |
|
If it's on Docker then it's no longer on the localhost. Try your device's local IP with the FlareSolverr port. If you're running another Docker container (e.g. Jackett or Prowlarr) then you can use the container IP and port. |
|
That's correct. It uses some new thingy that's better than doing Hyper-V from what I understand. As to all the rest. You are on the same stand as myself. Everything seems to be running according to Docker. The “problem” is that Flaresolverr is hardly ever needed for me. Therefore only fired it up ones I got errors in my other apps. YD I got annoyed when the older v2 just started to exit everytime I tried to run it. So I decided to try v3 now rather then “having to deal with it later” Anyhow, what are you supposed to see when you try to access http://localhost:8191? It’s the API URL so you shouldn't really get anywhere trying to browse it? However, me2 would like a way to test if Flaresolverr is actually working/running. I will do some digging and get back to you, |
|
dont know what you mean by that... this is what I get everytime I start the contrainer 2023-03-14 20:53:11 INFO FlareSolverr 3.0.4 is there a command I can use to see if it actually working? could not access it using my device ip, still testing shit |
|
You asked a question, I answered it. |
I did not. But I did later "is there a command I can use to see if it actually working?" |
|
You did:
|
|
I have Prowlarr and Sonarr installed in Windows. My device IP is 192.168.1.2. When I put 192.168.1.2:8191 into Prowlarr, I get an error '"Failed to test proxy: 192.168.1.2". If I start the Flaresolverr Windows binary I have installed then 192.168.1.2:8191 works fine. Where do i find a container's IP address? If I Inspect the container it only shows the port. I can install a Prowlarr docker container but without knowing its IP address how do I access its UI? Is there another way to access a container without using the IP address? |
|
Assuming 192.168.1.2 is the local IP address of your host device, if you access http://192.168.1.2:8191 in browser, what is returned? The container IP will only be usable if Prowlarr is also running on Docker. Assuming the container's name is
|
|
So that means Jackett can't access FlareSolverr if I don't run Jackett in docker as well ? |
|
It can access it using the host's local IP, not the the container's IP. However, we've seen issues with invalid cookies when mixing local Jackett/Prowlarr and Docker FlareSolverr. |
|
|
|
I did some reading about docker since my last post (first time using it) . From: docker run -it -p 5000:5000 This will open port 5000 inside the instance to port 5000 on your local machine, and should then be accessible on 127.0.0.1:5000 or localhost:5000" Use So the port is 8191 and the imagename is I also installed a Prowlarr docker image and opened it's port. That's working also. |
|
{"msg": "FlareSolverr is ready!", "version": "3.0.4", "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36"} after running "docker run -it -p 8191:8191 flaresolverr/flaresolverr:latest" good job/find! so the problems seems to be that flaresolverr devs have failed to include the correct startup paraneters? Or rather make it clear for newcomers step-by-step as no ports are actually opend etc |
I have no idea. I am completely new to this. I only built the v3 binary last week using Python. I have used Python before though just to get applications running and only used it a little. I will test this Docker Desktop further and see how to intregrate |
|
Well all you need todo it seems is to goto images then click "run" on the right, then "optional parameters" and enter port 8191 as host port then run and your all set. Then next time you just start the container |
Nope, the Docker instructions have included this since FlareSolverr was created - https://github.com/FlareSolverr/FlareSolverr#docker It would be great if you stopped ignorantly lashing out at the people who give up their time to create and maintain something you use for free. |
|
@Rumpa112 , |
It would be even better if you take a little bit of time to explain how to use the app u so kindly offer for free... Also it's not "the people" only u I have a problem with. "If you prefer the docker cli execute the following command. docker run -d This you are referring to means absolutely NOTHING if you aren't already familiar with docker or Linux... |
|
It's expected that users would have read the README, it exists to avoid the situation like this. Your first comment here was you ignorantly lashing out, and it wasn't directed at me. I think we can move on now. |
How would you know who I was "lashing out at" perhaps I've already read a couple of comments by you .. How would the README help with any of this? 😂 It's the lack of guidance that landed us here in the first place. For you and other that already know Docker or Linux it's straightforward. But not for the rest of us as YOU CAN SEE reading the comments in this thread, GN. |
I believe you will find here what you are looking for =) https://stackoverflow.com/questions/30449313/how-do-i-make-a-docker-container-start-automatically-on-system-boot thnx again, have a good one. |
|
Thx. Unfortunately I decided to uninstall Docker Desktop for Windows + WSL. Sonarr wouldn't save a root folder anywhere in the Docker Container. Good luck. |
|
But Sonarr works great without docker, just as Jackett does 😌
Den ons 15 mars 2023 03:12DrStrange ***@***.***> skrev:
… Thx. Unfortunately I decided to uninstall Docker for Windows. Sonarr
wasn't allowing me to add a root folder anywhere in the Docker Container.
Good luck.
—
Reply to this email directly, view it on GitHub
<#660 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANQ4HDG6JTUWKRUKYBK4V7TW4EQPHANCNFSM6AAAAAATTBOJXY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Build Windows / Linux / macOS binaries for FlareSolverr 3. It was supported in FlareSolverr 2, but it was removed in the refactor.
See => https://pyinstaller.org/en/stable/
Related #650
The text was updated successfully, but these errors were encountered: