Cant install FlareSolverr - FlareSolverr.json was not found!

[AlexanderFeyaerts]

When trying to install FlareSolverr: /iocage/.plugins/github_com_ix-plugin-hub_iocage-plugin-index_git/FlareSolverr.json was not found!

[yeeahnick]

Same issue here.

[Night2512]

Same issue here. TrueNas is trying to install 'FlareSolverr' with capitals and is looking for a file called 'FlareSolverr.json' The json file in the directory is flaresolverr.json with lowercase letters.

Renaming the file does not work.

[Uxose]

I have the same problème

Same issue here. TrueNas is trying to install 'FlareSolverr' with capitals and is looking for a file called 'FlareSolverr.json' The json file in the directory is flaresolverr.json with lowercase letters.

Renaming the file does not work.

Hi everyone, I have copied the flaresolverr.json to FlareSolverr.json in the same directory and TrueNas have installed the plugin correctly.

[yuk7hi]

Hi everyone, I have copied the flaresolverr.json to FlareSolverr.json in the same directory and TrueNas have installed the plugin correctly.

This worked for me as well. Basically, I did the following and installing the plugin from the UI worked.

cd /mnt/<system-dataset>/iocage/.plugins/github_com_ix-plugin-hub_iocage-plugin-index_git/
cp flaresolverr.json FlareSolverr.json

[lbandi2]

Can confirm that worked for me too.

[Gujal00]

It fails towards the end at the postinstall tasks. Please advise how to solve npm: not found

Cloning into 'flaresolverr'...
Note: switching to 'c99101f74'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:
git switch -c

Or undo this operation with:
git switch -
Turn off this advice by setting config variable advice.detachedHead to false
HEAD is now at c99101f Bump version 2.2.9

/root/post_install.sh: npm: not found
cd: node_modules: No such file or directory
cd: node_modules: No such file or directory
Hmm... Looks like a unified diff to me...
The text leading up to this was:

--------------------------
|diff -Naur node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.js node_modules_fixed/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.js
|--- node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.js 2022-09-30 11:53:41.991795021 +0100
|+++ node_modules_fixed/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.js 2022-09-30 11:53:10.867991454 +0100
--------------------------
File to patch:
No file found--skip this patch? [y]
Skipping patch...
Hunk #1 ignored at 180.
Hunk #2 ignored at 507.
2 out of 2 hunks ignored--saving rejects to Oops.rej
Hmm... The next patch looks like a unified diff to me...
The text leading up to this was:

--------------------------

|diff -Naur node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.patch node_modules_fixed/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.patch
|--- node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.patch 1970-01-01 01:00:00.000000000 +0100
|+++ node_modules_fixed/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.patch 2022-09-30 11:52:26.293600027 +0100

--------------------------
(Creating file puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.patch...)
cd: node_modules: No such file or directory
Patching file puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.patch using Plan A...
Empty context always matches.
Hunk #1 succeeded at 1.
done
cd: node_modules: No such file or directory

Patching file puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.patch using Plan A...
Empty context always matches.
Hunk #1 succeeded at 1.
done

/root/post_install.sh: npm: not found
flaresolverr_enable: -> YES
/root/post_install.sh: npm: not found
Starting flaresolverr.
/root/post_install.sh: npm: not found
/root/post_install.sh: npm: not found

[yuk7hi]

@Gujal00 I don't think the plugin works anymore, even if it does it is running an older version and cannot solve the latest Cloudflare challenges.
As a workaround, I created a custom jail, cloned the FlareSolverr repo, installed the dependency packages (Chrome driver, vDisplay driver etc.) and created a rc script to run it as a service.
You can find the old steps here, but you'll have to change up some of the steps to setup the latest FlareSolverr version. (ex: instead of JS [node], it uses Python3 now)

Further, to support FreeBSD, you'll have to do a two liner change in 2 files. I've since upgraded to TrueNAS Scale from Core. I'll post the changes here (or on my forked repo) later, if anyone's it trying this way.

[Gujal00]

@yuk7hi Thanks for the prompt response. I am trying on TrueNAS core, keen to see if your method works on it. Worst case scenario i will run it on docker, it is working fine on a standalone linux machine

[AlexanderFeyaerts]

Coming back to this seeing all the replies. I was able to install it manually instead of working via the plugins.

[bringerer]

Hi everyone, I have copied the flaresolverr.json to FlareSolverr.json in the same directory and TrueNas have installed the plugin correctly.

This worked for me as well. Basically, I did the following and installing the plugin from the UI worked.

cd /mnt/<system-dataset>/iocage/.plugins/github_com_ix-plugin-hub_iocage-plugin-index_git/
cp flaresolverr.json FlareSolverr.json

this worked for me as well