Skip to content

Node v17 bad option: --openssl-legacy-provider #169

@predator4hack

Description

@predator4hack

Describe the bug
On using the command npm run start, the following error shows up:

> tensormap-client-revamp@0.1.0 start
> react-scripts --openssl-legacy-provider start

/usr/bin/node: bad option: --openssl-legacy-provider

To Reproduce
After clonging the repo,

cd tensorflow-client
npm install
npm run start

Expected behavior
Tensorflow client should start on the localhost

Screenshots
error

Desktop (please complete the following information):

  • OS: Ubuntu 20.04
  • Browser: Chrome
  • Version: 99.0,4

Additional context
It seems that this error shows up because of the Node v17, --openssl-legacy-provider was added for handling key size on OpenSSL v3. Refer this. Although the client runs smoothly if I remove --openssl-legacy-provider in the start script.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions