I'm trying to deploy my web project using surge. I have done this successfully on previous occasions. But now i'm getting an error and cannot understand why this happens.
email: g****n5**5#yahoo.com
token: *****************
project path: C:\Users\admin\Documents\r*******r-ui-development\build\
size: 44 files, 11.8 MB
domain: r*******r-ui.surge.sh
upload: [======= ] 34%, eta: 9.7s{ Error: write ECONNRESET
at exports._errnoException (util.js:1023:11)
at WriteWrap.afterWrite [as oncomplete] (net.js:804:14) code: 'ECONNRESET', errno: 'ECONNRESET', syscall: 'write' }
{ Error: write ECONNRESET
at exports._errnoException (util.js:1023:11)
at WriteWrap.afterWrite [as oncomplete] (net.js:804:14) code: 'ECONNRESET', errno: 'ECONNRESET', syscall: 'write' }
What seems to be the problem here? And how could i fix it? Thank you.
The issue was with the internet connection I was using. Apparently, the wifi network had some restrictions. I solved this by using a hotspot created from my mobile, and it worked perfectly. This was not an issue with npm.
Related
I'm getting an error when trying to push to github from vscode terminal.
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1134:16) {
errno: 'ENOENT',
code: 'ENOENT',
syscall: 'connect',
address: '/run/user/1000/snap.code/vscode-git-0e219c7318.sock'
}
Missing or invalid credentials.
Error: connect ENOENT /run/user/1000/snap.code/vscode-git-0e219c7318.sock
at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1134:16) {
errno: 'ENOENT',
code: 'ENOENT',
syscall: 'connect',
address: '/run/user/1000/snap.code/vscode-git-0e219c7318.sock'
} ```
This is only happening in vscode terminal cause if I use a different one I dont have this, any solution for this?
I had exact same problem its connection problem of VS Code restart VS code it will work fine
Try it later, I think it's an error conection, it happened to me. I wait a couple of minutes and I could push.
It's a problem of VSC have a look at here. Try to push from console instead.
I know this is old but if there are any people that have came here with the same issue. For me at least I found out that this can also occur when you have files with the same name. So I would also encourage you to look for duplicate file names or something else that is a bit out of wack since it might help! best of luck
I cannot connect to Mongo using mongoose ,,,
querySrv ENODATA _mongodb._tcp.todocluster-3kozc.mongodb.net
[nodemon] app crashed - waiting for file changes before starting...
I found a solution in another post Error: querySrv ENODATA _mongodb._tcp.blog-cluster-0hb5z.mongodb.net at QueryReqWrap.onresolve [as oncomplete]
For some reason the dns server did not return srv records, changing the dns server to one that returns those records fixed the problem. (I used https://use.opendns.com/ to fix the it)
it works now ...
npx kill-port 5000
then,
yarn start or npm start
I am configurating protractor environment by the http://www.protractortest.org/#/ website.When execute
webdriver-manager start
webdriver-manager: using global installed version 12.0.6
events.js:183
throw er; // Unhandled 'error' event
^
Error: connect ETIMEDOUT 192.30.255.116:443
at Object._errnoException (util.js:1024:11)
at _exceptionWithHostPort (util.js:1046:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14)
But sometimes,it will execute success.
The environment is:
Protractor –version:5.2.0
Java –version:1.8.0_131
Node –v:v8.9.0
Npm –v:5.5.1
Can someone please telling me what is happening here. Your assistance is appreciated.
If you are behind a VPN, you may need to add a proxy.
> set HTTP_PROXY=http://proxy.host.blah:80
> set HTTPS_PROXY=http://proxy.host.blah:80
> webdriver-manager start
This worked for me anyway.
I am using protector with angular 4, when i run e2e test it failed to download some dependency from network as it blocked within my org proxy.
I tried to set proxy in protractor.conf.js, but it did not work for me.
capabilities: {
'browserName': 'chrome',
'proxy': {
'proxyType': 'manual',
'httpProxy': 'http://ptx.proxy.corp.sopra:8080'
}
below error I'm getting when run ng e2e
webpack: Compiled successfully.
events.js:183
throw er; // Unhandled 'error' event
^
Error: connect ETIMEDOUT 216.58.204.144:443
at Object._errnoException (util.js:1024:11)
at _exceptionWithHostPort (util.js:1046:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1182:14)
Can someone please tell me how to use the proxy within in.
I did find a way around to set the proxy, I set up proxy in system environment variable with key http_proxy and ng e2e ran fine for me.
I have installed Node.js to start with an ionic project.
I have also installed ionic and cordova using the commands below:
npm install ionic -g
npm install cordova -g
I am using the command below to create an ionic project:
ionic start myApp blank
And i m getting the following error:
D:\IonicWork>ionic start myApp blank
Creating Ionic app in folder D:\IonicWork\myApp based on blank project
Downloading: https://github.com/driftyco/ionic-app-base/archive/master.zip
Error with start Error: connect ETIMEDOUT 192.30.253.121:443
at Object.exports._errnoException (util.js:1036:11)
at exports._exceptionWithHostPort (util.js:1059:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1080:14)
Error Initializing app: Error: connect ETIMEDOUT 192.30.253.121:443
Error: connect ETIMEDOUT 192.30.253.121:443
at Object.exports._errnoException (util.js:1036:11)
at exports._exceptionWithHostPort (util.js:1059:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1080:14)
Caught exception:
Error: connect ETIMEDOUT 192.30.253.121:443
at Object.exports._errnoException (util.js:1036:11)
at exports._exceptionWithHostPort (util.js:1059:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1080:14)
Mind letting us know? https://github.com/driftyco/ionic-cli/issues
Please suggest.
Thanks,
Malini
If you are on a company network, you are most probably behind a corporate web proxy. There are plenty of solution out there.
For a headstart, you need to add http_proxy and https_proxy environment variables based on the proxy you got from your company IT department.
Open your node command prompt in administrator mode and run following command. After that, close and restart your node command prompt and try to run ionic start again.
npm config set proxy http://proxy.company.com:8080
npm config set https-proxy http://proxy.company.com:8080
Better to start in ionic creator.and its the better place for design also