-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not execute the Node.js binary. You may need to set the path to a working binary manually. #1130
Comments
Hello 👋 Thank you for taking the time to open this issue with recognize. I know it's frustrating when software I look forward to working with you on this issue |
Is there anything in the nextcloud logs? |
Recognize & Node used to work correctly before. |
You need node.js v20 since recognize v7 can you check the node binary? |
You may need to install your own version of node.js |
Directly on my host, it seems the node binary installed by the Recognizez app is working (v20.9.0)
In my Nextcloud container,
Donwloaded the last prebuit binaries LTS node version 20.13.1 in my container : same issue |
Solved by installing nodejs through the docker ENV : Added nodejs,npm as additionnal apps |
Hi, in my case, the node executable was not executable... |
Which version of recognize are you using?
6.1.1
Enabled Modes
Object recognition, Face recognition
TensorFlow mode
WASM mode
Downstream App
Memories App
Which Nextcloud version do you have installed?
28.0.5
Which Operating system do you have installed?
Debian 11
Which database are you running Nextcloud on?
mysql 10.5.23
Which Docker container are you using to run Nextcloud? (if applicable)
No response
How much RAM does your server have?
4GiB
What processor Architecture does your CPU have?
aarch64
Describe the Bug
I updated from Nextcloud 27 to Nextcloud 28 and now I get this error. Node is located in
/var/www/nextcloud/apps/recognize/bin/node
so I guess it is automatically installed be Recognize.I installed manually Node executable and changed to it, but I get the same error.
Expected Behavior
Node should work?
To Reproduce
...
Debug log
No response
The text was updated successfully, but these errors were encountered: