Comments (5)
Is it possible to bypass this error?
from node-nightly.
Try the network at home, got another error
Downloading the nightly version, hang on...
FetchError: request to https://nodejs.org/download/nightly/index.json failed, reason: Client network socket disconnected before secure TLS connection was established
at ClientRequest. (C:\Users\clu\AppData\Roaming\npm\node_modules\node-nightly\node_modules\node-fetch\index.js:133:11)
at ClientRequest.emit (events.js:310:20)
at TLSSocket.socketErrorListener (_http_client.js:426:9)
at TLSSocket.emit (events.js:310:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
type: 'system',
errno: 'ECONNRESET',
code: 'ECONNRESET'
}
from node-nightly.
Client network socket disconnected before secure TLS connection was established caused by proxy, I did not have proxy at home.
Turn off the npm proxy, then I got the same error self signed certificate in certificate chain
from node-nightly.
Tried to npm set strict-ssl false
, still have the same problem
from node-nightly.
The self signed certificate in certificate chain
problem was caused by Forcepoint used in company, just disable it can bypass this problem.
from node-nightly.
Related Issues (20)
- Consider using lerna for repos.. HOT 1
- use of const in strict mode HOT 3
- Installing modules with binary bindings HOT 9
- Pick architecture HOT 1
- (feat)Enable Network tab HOT 3
- "Please check your internet connectivity" error message HOT 2
- Using node-nightly when there is no internet connectivity HOT 1
- Using node-nightly behind a proxy HOT 4
- 404 on initial launch HOT 4
- Adjust command line options HOT 3
- errors when upgrade HOT 3
- Issue with Node 7.9.0 32 bit HOT 1
- Add notes that "Run as Administrator is required"
- Compatibility with node-sass using webpack
- Error: EPERM: operation not permitted, rename node-nightly required HOT 3
- `node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` and `node --inspect-brk` instead. HOT 2
- TypeError: Cannot read properties of undefined (reading 'version') HOT 5
- Launch node-nightly initially with no reponse
- GotError [HTTPError]: Response code 404 (Not Found)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-nightly.