Hi, I've met this problem when I run $ scripts/install-sdk.sh. When I installed https://github.com/cloud9ide/sdk-deps-win32/releases/download/v0.0.1/node.tar.gz it said SSL_ERROR_SYSCALL, errno 10054
At first I tried git config http.postBuffer 524288000
and env GIT_SSL_NO_VERIFY=true
But it still occured.
Actually, I can download the node.tar.gz file directly, so I do not think there was a network problem.
Here it is the log:
$ scripts/install-sdk.sh
Already up to date.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1017 100 1017 0 0 1086 0 --:--:-- --:--:-- --:--:-- 1086+ C9_DIR=/c/Users/admin/.c9
+ has wget
+ type wget
+ return 1
+ has curl
+ type curl
+ return 0
+ DOWNLOAD='curl -sSOLk'
+ URL=https://github.com/cloud9ide/sdk-deps-win32/releases/download/v0.0.1
+ mkdir -p /c/Users/admin/.c9
+ echo '*'
+ rm -rf /c/Users/admin/.c9/msys
+ rm -rf /c/Users/admin/.c9/node.exe
+ rm -rf /c/Users/admin/.c9/node_modules/pty.js
+ rm -rf /c/Users/admin/.c9/node_modules/sqlite3
+ getTar node.tar.gz
+ cd /c/Users/admin/.c9
+ curl -sSOLk https://github.com/cloud9ide/sdk-deps-win32/releases/download/v0.0.1/node.tar.gz
curl: (56) OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 10054
$ node server.js
Starting standalone
{ [Error: ENOENT: no such file or directory, open 'C:\Users\admin\.c9\standalone
.settings']
errno: -4058,
code: 'ENOENT',
syscall: 'open',
path: 'C:\\Users\\admin\\.c9\\standalone.settings' }
Connect server listening at http://127.0.0.1:8181
CDN: version standalone initialized E:\git\c9sdk\build
Started 'E:\git\c9sdk\configs\standalone' with config 'standalone'!
Cloud9 is up and running
Hi, I've met this problem when I run $ scripts/install-sdk.sh. When I installed https://github.com/cloud9ide/sdk-deps-win32/releases/download/v0.0.1/node.tar.gz it said SSL_ERROR_SYSCALL, errno 10054 At first I tried git config http.postBuffer 524288000 and env GIT_SSL_NO_VERIFY=true But it still occured. Actually, I can download the node.tar.gz file directly, so I do not think there was a network problem.
Here it is the log: