Skip to content
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

Error: Error: Error: ENOENT: no such file or directory, open '' #863

Closed
Iamtheoldman opened this issue Sep 1, 2023 · 11 comments
Closed

Comments

@Iamtheoldman
Copy link

gave all my apis but got this error even on step by step guides

@chungyau97
Copy link
Contributor

Hi @Iamtheoldman,

Could you tell me more on your setup before we proceed?

  1. NodeJS version
  2. OS
  3. Cloud or Local

@Sal-ix
Copy link

Sal-ix commented Sep 2, 2023

Hi,
Probably local. I faced a similar issue here. Missing SVGs in node_modules folder, when transitioning directly from 'yarn install' to 'yarn dev'.
Running the 'yarn build' command fixed it.

@chungyau97
Copy link
Contributor

Hey @Sal-ix, yup you have to yarn build showed on step 4

@ondrejhadrava
Copy link

I had this issue as well. I resolved it by changing node version to v18.17.1 and reinstalling Flowise.

@platothefish
Copy link

platothefish commented Sep 9, 2023

I'm getting the same:

Node JS version: v18.17.1
Mac OS 13.5.2 (Mac M1)
Local

Terminal:

elizabethoconnell@oxfordreviewpro ~ % npx flowise start
2023-09-09 13:23:38 [INFO]: Starting Flowise...
2023-09-09 13:23:38 [INFO]: ⚡️ [server]: Flowise Server is listening at 3000
2023-09-09 13:23:38 [INFO]: 📦 [server]: Data Source has been initialized!
2023-09-09 13:24:17 [INFO]: ❌ DELETE /api/v1/chatmessage/xxxx
2023-09-09 13:24:25 [INFO]: ⬆️ POST /api/v1/chatmessage/xxx
2023-09-09 13:24:25 [INFO]: ⬆️ POST /api/v1/internal-prediction/xxxx
2023-09-09 13:24:25 [ERROR]: Error: Error: ENOENT: no such file or directory, open ''
Error: Error: Error: ENOENT: no such file or directory, open ''
at getCredentialData (/Users/elizabethoconnell/.npm/_npx/xxxx/node_modules/flowise-components/dist/src/utils.js:467:15)
at async ChatOpenAI_ChatModels.init (/Users/elizabethoconnell/.npm/_npx/xxxx/node_modules/flowise-components/dist/nodes/chatmodels/ChatOpenAI/ChatOpenAI.js:138:32)
at async buildLangchain (/Users/elizabethoconnell/.npm/_npx/xxxxx/node_modules/flowise/dist/utils/index.js:221:50)
at async App.processPrediction (/Users/elizabethoconnell/.npm/_npx/xxxx/node_modules/flowise/dist/index.js:765:40)
at async /Users/elizabethoconnell/.npm/_npx/xxxx/node_modules/flowise/dist/index.js:558:13
2023-09-09 13:24:25 [ERROR]: [server]: Error: Error: Error: Error: ENOENT: no such file or directory, open ''
Error: Error: Error: Error: ENOENT: no such file or directory, open ''
at buildLangchain (/Users/elizabethoconnell/.npm/_npx/xxxxxx/node_modules/flowise/dist/utils/index.js:231:19)
at async App.processPrediction (/Users/elizabethoconnell/.npm/_npx/xxxx/node_modules/flowise/dist/index.js:765:40)
at async /Users/elizabethoconnell/.npm/_npx/8b95a19c5c9c8708/node_modules/flowise/dist/index.js:558:13
2023-09-09 13:24:25 [INFO]: ⬆️ POST /api/v1/chatmessage/xxxx

@platothefish
Copy link

Okay solved. I installed Homebrew /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" and then brew install node and then reinstalled Flowise, deleted and reinstalled the credentials and BINGO! It works.

@platothefish
Copy link

Ah so today I am back to Error: Error: Error: ENOENT: no such file or directory, open ''

Poo!

@chungyau97
Copy link
Contributor

Hey @platothefish,

could you share a screenshot of your flow?
In the mean time, try using these commands sudo npm install -g flowise and sudo npx flowise start.

@HenryHengZJ
Copy link
Contributor

HenryHengZJ commented Sep 18, 2023

Added this PR - #939

You can overwrite the encryption key using env variable instead of the old way of storing the key into a local path, this should all the errors regarding credentials

Update: here's the workaround guide - https://docs.flowiseai.com/environment-variables#credential

@platothefish
Copy link

Okay I solved this by running "sudo npx flowise start" and then closing it and re starting it with npx flowise start. Probably a permissions issue somewhere along the line.

@adolfousier
Copy link

adolfousier commented Oct 19, 2023

Unfortunately, I couldn't fix it with "sudo npx flowise start" and then npx flowise start, thanks for the heads up @platothefish.

I was able to solve this issue by setting up the node version and then increasing RAM to 2gb. It's finally working, if anyone wants to try, check here: #970 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants