# ERR\_OSSL\_EVP\_UNSUPPORTED when running the react meeting SDK sample

**URL:** <https://devforum.zoom.us/t/err-ossl-evp-unsupported-when-running-the-react-meeting-sdk-sample/94787>\
**Category:** Meeting SDK\
**Created:** [September 11, 2023, 5:11am UTC](https://devforum.zoom.us/t/err-ossl-evp-unsupported-when-running-the-react-meeting-sdk-sample/94787 "2023-09-11T05:11:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![peterprinciple](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/peterprinciple/32/51565_2.png) [@peterprinciple](https://devforum.zoom.us/u/peterprinciple)\
**Post date:** [September 11, 2023, 5:11am UTC](https://devforum.zoom.us/t/err-ossl-evp-unsupported-when-running-the-react-meeting-sdk-sample/94787/1 "2023-09-11T05:11:07Z")

</div>

Trying to get the [react meetingsdk sample repo](https://github.com/zoom/meetingsdk-react-sample) working, but it seems to have lots of issues. Ignoring the numerous vulnerabilities after npm install, having followed the steps provided in the documentation, and making no other changes, at step 6) npm start - I get the following error message:  
opensslErrorStack: [‘error:03000086:digital envelope routines::initialization error’],  
library: ‘digital envelope routines’,  
reason: ‘unsupported’,  
code: ‘ERR\_OSSL\_EVP\_UNSUPPORTED’

This issue is consistent across multiple computers, by simply cloning the repo and following its instructions to perform the basics (install, populate fields with your unique sdk key, then running npm start).

I’ve tried changing node versions (downgrading to LTS), using node option openssl legacy provider [open ssl legacy provider](https://stackoverflow.com/questions/69665222/node-js-17-0-1-gatsby-error-digital-envelope-routinesunsupported-err-os) and other options, but have not found a work around or solution.

Any help would be greatly appreciated.

---

<div class="post-metadata">

**Author:** ![peterprinciple](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/peterprinciple/32/51565_2.png) [@peterprinciple](https://devforum.zoom.us/u/peterprinciple)\
**Post date:** [September 12, 2023, 1:06am UTC](https://devforum.zoom.us/t/err-ossl-evp-unsupported-when-running-the-react-meeting-sdk-sample/94787/2 "2023-09-12T01:06:04Z")

</div>

For anyone that stumbles on this thread:

Finally resolved this issue. It was related to openssl-legacy-provider, and the solution was a modified version from [this stack overflow thread](https://stackoverflow.com/questions/69665222/node-js-17-0-1-gatsby-error-digital-envelope-routinesunsupported-err-os)

essentially, was using windows so tried the top answer, changing package.json scripts to:

```auto
"scripts": {
    "start": "set SET NODE_OPTIONS=--openssl-legacy-provider && react-scripts start",
    "build": "set SET NODE_OPTIONS=--openssl-legacy-provider && react-scripts build"
}

```

However, “set SET NODE\_OPTIONS…” did not work, instead tweaking this to:

```auto
"scripts": {
    "start": "SET NODE_OPTIONS=--openssl-legacy-provider && react-scripts start",
    "build": "SET NODE_OPTIONS=--openssl-legacy-provider && react-scripts build"
}

```

Resolved the issues.

The meetingsdk had some further issues to overcome, such as ‘No version of chokidar available’ ( [solution here](https://stackoverflow.com/questions/66734503/react-npm-start-not-working-no-version-of-chokidar-available) )