error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO during React install GET package

andrew.hardy 10

I am completely new to Azure.

We host an app service on Azure which comprises git version control, a node / ReactJS Frontend and a C# .NET Backend, which talks to an SQL Server Database and this deploys automatically when code is merged to the relevant branch (one app service for staging and one for development), installing the React App and building the .NET from scratch each time.

We have made like this about several deployments this year and I'd say tens of deployments last year, all successful. I'm pretty sure nothing about the configuration of the app service has changed in this time, we have only redeployed the code.

The last 2 or 3 deployments over a 2 day period failed during the React Web App installation, though the React installs successfully locally. The React install retrieves about 180 packages in this way...

npm http GET https://registry.npmjs.org/<package name>

These three recent deployments fail once each at differing points during the full 180 package retrievals with the following error passed up by the npm package:

EXEC : npm ERR! error : 1280:error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version:openssl\ssl\s23_clnt.c:602: [D:\home\site\repository\<project folder>\<project file>]
  npm ERR! 
  npm ERR!     at CleartextStream._puller (tls.js:501:24)
  npm ERR!     at CleartextStream._pull (tls.js:432:19)
  npm ERR!     at SecurePair.cycle (tls.js:727:20)
  npm ERR!     at EncryptedStream.write (tls.js:130:13)
  npm ERR!     at Socket.ondata (stream.js:38:26)
  npm ERR!     at Socket.emit (events.js:67:17)
  npm ERR!     at TCP.onread (net.js:367:14)
  npm ERR!  [Error: 1280:error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version:openssl\ssl\s23_clnt.c:602:
  npm ERR! ]
  npm ERR! You may report this log at:
  npm ERR!     <http://github.com/isaacs/npm/issues>
  npm ERR! or email it to:
  npm ERR!     <npm-@googlegroups.com>
  
  npm ERR! System Windows_NT 6.2.9200
  npm ERR! command "D:\\Program Files (x86)\\nodejs\\\\node.exe" "D:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
  npm ERR! cwd D:\home\site\repository\CTM.Approval.Web\ClientApp
  npm ERR! node -v v0.6.20
  npm ERR! npm -v 1.1.37
npm ERR! message 1280 : error : 1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version:openssl\ssl\s23_clnt.c:602: [D:\home\site\repository\CTM.Approval.Web\CTM.Approval.Web.csproj]
  npm ERR! message

This causes the overall build to fail. At first glance this seems to me likely some kind of intermitent / dynamic / dependant comms issue, rather than a React install issue, given each failure is not at the same package GET and the install is successful locally.

Is anyone able to confirm this likelihood and suggest any further investigations or is aware of any recent issues on Azure which may possibly lead to these symptoms and when these recent issue may be resolved? Or alternatively how this might actually be an issue with the deployed code and why it might only fail on deployment?

It is odd that the error message includes these versions:

  npm ERR! node -v v0.6.20
  npm ERR! npm -v 1.1.37

The Azure App Service CLI includes:
User's image

Also odd. Though I am not sure if this is just a sandbox in some contexts.
Node v16.13.0 is as expected. Not sure why npm would be at ver 1 for this node installation.
However, the installations have always been successful (as described) and nothing has been explicitly changed on Azure at all or in the deploying application iro this.

Many thanks indeed.

VenkateshDodda-MSFT 18,176 Reputation points Microsoft Employee

2023-01-30T13:07:12.53+00:00
@andrew.hardy Thank you for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.

Based on the shared information, we have understood that your web app is enabled with source controls github and recently you have started seeing the deployment failure stating the above shared npm errors.

Do you see those above npm errors in the GitHub actions workflows? If yes, could you help us with the github action logs to check and assist you further.

You have mentioned the below.
"However, the installations have always been successful (as described) and nothing has been explicitly changed on Azure at all or in the deploying application iro this." --> Just to confirm, is your deployment now successful? and trying to understand the case of the error with prior deployment attempts (with no change from your end)?)

Is your web app running on windows app service or Linux app service plan?
andrew.hardy 10 Reputation points

2023-01-31T08:01:43.36+00:00
@VenkateshDodda-MSFT Thank you so much. I do appreciate this.
1)

I am here. Unfortunately I have literally only just started with Azure so I am struggling to navigate to the GitHub Actions Workflows. I'd really appreciate it if you could guide me with the steps.

Apologies, I should have made this clearer. I meant nothing has been explicitly changed and deployments have always been successful until now. Now they consistently fail, as described. Though npm install in our local dev environment does not have this issue. While so far this is on dev and staging, it is still critical as it is holding up testing for production.

Windows

It's not yet certain that this is the cause in our case, but someone else has cited a similar issue caused by a sudden unexpected down versioning of npm without them doing anything. I am completely new to Azure, could you possibly guide me the steps to revert this?
Bill Rappleye 5 Reputation points

2023-02-01T13:12:36.4533333+00:00

I should’ve also mentioned that the version of NodeJS and NPM have to not only be compatible (as you’ve probably already assumed), but also that it must be a combination of versions MS has installed on the image. Look here for compatible Node/NPM versions (https://nodejs.org/en/download/releases/) and in your Kudu environment/console, under both the Node and NPM install folders (D:\Program Files (x86)) to determine which versions are available on your Web App image. If you’ve specified a version of NPM that exists there, you should see that reflected in the console when you query the NPM version.
VenkateshDodda-MSFT 18,176 Reputation points Microsoft Employee

2023-02-01T14:27:47.13+00:00
@andrew.hardy Thanks for sharing requested information and apologize for the delay in my response.

If you have configured your webapp with source controls as GitHub.

Then the webapp will create workflow file into your GitHub repository to handle build and deploy tasks to App Service.

When there is any change pushed to your configure repository the GitHub actions will get triggered and you can find those workflows run logs under actions as explained here.

Based on the shared screenshot, I have looked at the backend logs for this webapp dev-approval-uk we see that bitbucket is configured as source control for this webapp.
could you please help me with more information from where you are seeing these npm error logs?

2 answers

Bill Rappleye 5 Reputation points

2023-01-31T03:08:15.96+00:00

We encountered this in some of our build environments in Azure just yesterday for the first time. Things were working fine prior. An investigation of Node and NPM versions showed us that for some reason, even though the node version was set properly, it was using a very old, incorrect version of NPM. We were able to resolve by adding the configuration value with the specific NPM version compatible with the node version specified, using the configuration setting WEBSITE_NPM_DEFAULT_VERSION.

Make sure your Node and NPM versions are both compatible (https://nodejs.org/en/download/releases/) and also that those specific versions are installed on the image/environment where your app is deployed (look in the Node and NPM install directories that live under D:\Program Files (x86) in your console).

As long as you have specified existing and compatible versions, you should see those versions listed when you query Node and NPM versions on the console (node --version and npm --version). Once you confirm that your environment is reporting that it is using the correct versions, everything should start to work properly again.

Hope this helps!
Please sign in to rate this answer.

1 person found this answer helpful.
andrew.hardy 10 Reputation points

2023-01-31T08:17:31.21+00:00

@Bill Rappleye Thank you so much for responding. Really appreciate it.

This sounds like a good match for our situation. This also occurred to me but I am literally brand new to Azure and didn't want to make assumptions.
Given I am brand new to Azure, just to be clear, we are talking about navigation to here...

...and selecting 'New application setting'? Is it important how the version number is formed e.g. "v8...", "8..."? Any additional information / gotchas I should be aware of or should this be the extent of it and should this setting be picked up on a fresh deployment?
Out of interest do you know why the old version seems not to immediately fail for the tsl version, but the GET package is successful much of the time? Also did you happen to discover why npm down versioned suddenly and subsequently consistently without warning?
Regarding the CLI is this literally a sand box or a place to show config but not to change?
Apologies if anything I've written does not make sense. For someone literally brand new to Azure App Services (Web App Reactjs and C# .NET) is there any particular training material / Udemy etc etc you would recommend?

Thank you again for sharing this information. I really appreciate it.

andrew.hardy 10 Reputation points

2023-01-31T08:27:42.3066667+00:00

@Bill Rappleye please refer to previous response comment. Cannot find delete feature for this one.

andrew.hardy 10 Reputation points

2023-02-01T12:03:45.2366667+00:00

I am still getting this issue:

EXEC : npm ERR! error : 7788:error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version:openssl\ssl\s23_clnt.c:602: [D:\home\site\repository\CTM.Approval.Web\CTM.Approval.Web.csproj] npm ERR! npm ERR! at CleartextStream._puller (tls.js:501:24) npm ERR! at CleartextStream._pull (tls.js:432:19) npm ERR! at SecurePair.cycle (tls.js:727:20) npm ERR! at EncryptedStream.write (tls.js:130:13) npm ERR! at Socket.ondata (stream.js:38:26) npm ERR! at Socket.emit (events.js:67:17) npm ERR! at TCP.onread (net.js:367:14) npm ERR! [Error: 7788:error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version:openssl\ssl\s23_clnt.c:602: npm ERR! ] npm ERR! You may report this log at: npm ERR! <http://github.com/isaacs/npm/issues> npm ERR! or email it to: npm ERR! <npm-@googlegroups.com> npm ERR! System Windows_NT 6.2.9200 npm ERR! command "D:\\Program Files (x86)\\nodejs\\\\node.exe" "D:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" npm ERR! cwd D:\home\site\repository\CTM.Approval.Web\ClientApp npm ERR! node -v v0.6.20 npm ERR! npm -v 1.1.37 npm ERR! message 7788 : error : 1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version:openssl\ssl\s23_clnt.c:602: [D:\home\site\repository\CTM.Approval.Web\CTM.Approval.Web.csproj] npm ERR! message

Once during the multiple calls to...
npm http GET https://registry.npmjs.org/<package name>
After adding these settings:

Please see other suggested answers.
cc: @Bill Rappleye @Bill Rappleye @VenkateshDodda-MSFT

andrew.hardy 10 Reputation points

2023-02-01T12:13:58.84+00:00

Hi @Bill Rappleye @Bill Rappleye ,

I added this:

But I am getting the same issue described earlier. I am new to Azure are there any other steps in addition to adding the setting? Or should I be putting this setting somewhere else?

In the CLI I am getting this still:

Bill Rappleye 5 Reputation points

2023-02-01T13:11:51.56+00:00

Make sure your Node and NPM versions are both compatible (https://nodejs.org/en/download/releases/) and also that those specific versions are installed on the image/environment where your app is deployed (look in the Node and NPM install directories that live under D:\Program Files (x86) in your console).

As long as you have specified existing and compatible versions, you should see those versions listed when you query Node and NPM versions on the console (node --version and npm --version). Once you confirm that your environment is reporting that it is using the correct versions, everything should start to work properly again.

andrew.hardy 10 Reputation points

2023-02-01T13:12:09.4+00:00

I have been looking at this https://azureossd.github.io/2016/04/20/nodejs-and-npm-versions-on-azure-app-services/

@Bill Rappleye @Bill Rappleye @VenkateshDodda-MSFT

I have tried adding engines to package.json

"engines": { "node": "16.13.0", "npm": "8.1.0" }

and also WEBSITE_NPM_DEFAULT_VERSION to Settings , but I am still getting the same error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1.

Previously without us having changed any Azure config for a long time the install just worked.

Bill Rappleye 5 Reputation points

2023-02-01T13:16:40.57+00:00

This issue definitely seems like a defect and not expected behavior. It looks like it should be automatically setting up the correct NPM version for the environment with the node version specified that has been configured to be used (like it used to), but for some reason it is suddenly not anymore, so setting it explicitly (in the details I've outlined above) is the workaround.

The only downside to this workaround is that you will have to set both versions the next time you increment your node version dependency. Not a huge deal; in fact, maybe it's better. The only thing that's annoying about it is that you'll have to make sure it's one of the installed Node and NPM versions in your environment.

Bill Rappleye 5 Reputation points

2023-02-01T13:32:09.4466667+00:00

Setting engines in your package.json may also work, as long as you take care to make sure you’re using versions that are installed and exist in your environment.

andrew.hardy 10 Reputation points

2023-02-02T10:42:27.1266667+00:00

@Bill Rappleye @Bill Rappleye Just to say thank you so much for sharing this. This has now resolved our issue.

First time posting here. Do you need to edit extend you answer to include the additional comments then I can accept it. Or would the additional be obvious to most?

We probably want to install a later npm at some point so we can have the already installed later node. As completely new to Azure where is good to go?

Can you recommend any starter tutorials on Azure App Services? Or just follow Azure docs from the top. Hard to know where to start when you know nothing.
Sign in to comment
Chris Green 0 Reputation points

2023-02-01T23:46:24.5066667+00:00

Hey @andrew.hardy -- we just had this issue today and your question and @Bill Rappleye helped point us in the right direction.

For whatever reason, our azure app service has a mismatch between the npm versions listed in Kudu > Runtime versions, as opposed to what is actually installed, so it no longer could see our specified NPM version. Note the missing "8.1.0" version.

Setting WEBSITE_NPM_DEFAULT_VERSION in Application Settings to a version listed in D:\Program Files (x86)\npm worked well, and our pipelines are succeeding again.

Best of luck!
Please sign in to rate this answer.

0 comments No comments
Sign in to comment