danieldabate
commented
3 months ago From the error it seems you are getting a timeout when Chrome is being downloaded/setup for Puppeteer. According to it, if you are not going to use Puppeteer, you can set PUPPETEER_SKIP_DOWNLOAD env variable to skip the download.
You might also want to check this thread in Puppeteer repository, where alternative solutions are offered like forcing ipv4.
Do you have access to Google servers? Can you ping 34.104.35.123? Most probably your connection is timing out because it is unreachable.
willwanggg
essington62
Am I doing something wrong?
Just did
npm install flowiseand triednpx flowise startalso tried sudo install.
npm warn ERESOLVE overriding peer dependency npm warn While resolving: chromadb@1.7.3 npm warn Found: @google/generative-ai@0.11.5 npm warn node_modules/flowise/node_modules/llamaindex/node_modules/@google/generative-ai npm warn @google/generative-ai@"^0.11.0" from llamaindex@0.3.15 npm warn node_modules/flowise/node_modules/llamaindex npm warn llamaindex@"^0.3.13" from flowise-components@1.8.2 npm warn node_modules/flowise/node_modules/flowise-components npm warn npm warn Could not resolve dependency: npm warn peerOptional @google/generative-ai@"^0.1.1" from chromadb@1.7.3 npm warn node_modules/flowise/node_modules/llamaindex/node_modules/chromadb npm warn chromadb@"~1.7.3" from llamaindex@0.3.15 npm warn node_modules/flowise/node_modules/llamaindex npm warn npm warn Conflicting peer dependency: @google/generative-ai@0.1.3 npm warn node_modules/@google/generative-ai npm warn peerOptional @google/generative-ai@"^0.1.1" from chromadb@1.7.3 npm warn node_modules/flowise/node_modules/llamaindex/node_modules/chromadb npm warn chromadb@"~1.7.3" from llamaindex@0.3.15 npm warn node_modules/flowise/node_modules/llamaindex npm warn EBADENGINE Unsupported engine { npm warn EBADENGINE package: 'flowise@1.8.1', npm warn EBADENGINE required: { node: '>=18.15.0 <19.0.0 || ^20' }, npm warn EBADENGINE current: { node: 'v22.2.0', npm: '10.7.0' } npm warn EBADENGINE } npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs npm warn deprecated set-value@0.2.0: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated set-value@0.3.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated set-value@0.3.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated set-value@0.3.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated set-value@0.3.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated set-value@0.3.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated set-value@0.3.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated set-value@0.3.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm warn deprecated @babel/plugin-proposal-class-properties@7.18.6: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead. npm warn deprecated npmlog@5.0.1: This package is no longer supported. npm warn deprecated @oclif/screen@3.0.8: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm warn deprecated rimraf@2.7.1: Rimraf versions prior to v4 are no longer supported npm warn deprecated npmlog@6.0.2: This package is no longer supported. npm warn deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported. npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported. npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported npm warn deprecated glob@5.0.15: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated @aws-sdk/signature-v4@3.374.0: This package has moved to @smithy/signature-v4 npm warn deprecated @aws-sdk/protocol-http@3.374.0: This package has moved to @smithy/protocol-http npm warn deprecated domexception@4.0.0: Use your platform's native DOMException instead npm warn deprecated cross-spawn-async@2.2.5: cross-spawn no longer requires a build toolchain, use it instead npm warn deprecated fs-promise@2.0.3: Use mz or fs-extra^3.0 with Promise Support npm warn deprecated gauge@3.0.2: This package is no longer supported. npm warn deprecated gauge@4.0.4: This package is no longer supported. npm warn deprecated vm2@3.9.19: The library contains critical security issues and should not be used for production! The maintenance of the project has been discontinued. Consider migrating your code to isolated-vm. npm warn deprecated puppeteer@19.11.1: < 22.5.0 is no longer supported npm warn deprecated puppeteer@20.9.0: < 22.5.0 is no longer supported npm warn deprecated highlight.js@9.15.10: Version no longer supported. Upgrade to @latest npm error code 1 npm error path /opt/homebrew/lib/node_modules/flowise/node_modules/flowise-components/node_modules/puppeteer npm error command failed npm error command sh -c node install.js npm error ERROR: Failed to set up Chrome r115.0.5790.98! Set "PUPPETEER_SKIP_DOWNLOAD" env variable to skip download. npm error Error: connect ETIMEDOUT 34.104.35.123:443 npm error at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1606:16) { npm error errno: -60, npm error code: 'ETIMEDOUT', npm error syscall: 'connect', npm error address: '34.104.35.123', npm error port: 443 npm error }