[BUG] Getting constant `Client network socket disconnected before secure TLS connection was established`

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

When trying to install packages using npm install --production=false --loglevel notice --legacy-peer-deps, we get constantly getting mentioned error. The package that fails is always different, so there isn't a specific package causing the issue.

npm WARN deprecated read-package-tree@5.3.1: The functionality that this package provided is now in @npmcli/arborist
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated rollup-plugin-inject@3.0.2: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-inject.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated feathers-logger@0.3.2: This module is no longer maintained. See https://github.com/feathersjs-ecosystem/feathers-logger#migrating for more information on using a standard logger
npm WARN deprecated emailjs-com@3.2.0: The SDK name changed to @emailjs/browser
npm WARN deprecated superagent@7.1.2: Deprecated due to bug in CI build https://github.com/visionmedia/superagent/pull/1677\#issuecomment-1081361876
npm WARN deprecated uuid@3.3.2: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated core-js@2.6.12: core-js@<3.4 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code ECONNRESET
npm ERR! errno ECONNRESET
npm ERR! network request to https://registry.npmjs.org/remove-trailing-separator/-/remove-trailing-separator-1.1.0.tgz failed, reason: Client network socket disconnected before secure TLS connection was established
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-03-31T11_49_10_091Z-debug-0.log

Here are the changes I have tried so far:

1. Added npm install -g npm, still not working

2. Added following before npm i, still not working
   npm config set fetch-retry-maxtimeout 9999999 -g

3. Updated npm i command to include timeout, still not working
   npm install --production=false --loglevel notice --legacy-peer-deps --timeout=9999999

4. Installed VPN and connected to other regions, still not working.

Expected Behavior

Install packages without failing

Steps To Reproduce

Using a project with workspaces
No cache available
npm install --production=false --loglevel notice --legacy-peer-deps

Environment

• npm: 8.5.5
• Node.js: 17.8.0
• OS Name: Ubunutu 20.04

The issue provides no source file or test location. Start by reproducing the workspace install with npm 8.5.5 and Node.js 17.8.0 on Ubuntu 20.04, then investigate the failed request to the npm registry URL shown; done means installs complete without the TLS socket error.