New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

events.js:183 throw er; // Unhandled 'error' event ^ Error: read ECONNRESET at _errnoException (util.js:1024:11) at TCP.onread (net.js:615:25) #2922

Closed
nigel-dewar opened this Issue Dec 18, 2017 · 20 comments

Comments

Projects
None yet
@nigel-dewar

nigel-dewar commented Dec 18, 2017

Brand new install of Ionic on Windows 10 Pro

npm i ionic cordova -g

versions
Node v 8.9.1
NPM v 5.5.1
Ionic -v 3.19.0
cordova -v 7.1.0

created app with ionic start todo blank

then run
ionic lab

Browser loads, all is fine, then I go to make change to html file and get this error

image

Tried several different versions, like an older version on ionic cli. Doesnt work.

Also tried doing an npm i incase the ionic start thing didnt work. Doesnt work.

I also tried ionic serve. This works but then as soon as you change say your home.html file, boom it breaks.

Is ionic v3 working on Windows ??? Or should I be using a Mac only? Buy the way I dont have a mac. So I cant test.

@nigel-dewar

This comment has been minimized.

Show comment
Hide comment
@nigel-dewar

nigel-dewar Dec 18, 2017

Update, Issue is resolved if use another browser. Just cannot use Google Chrome. Even if close chrome completely, restart and still no go

Using Internet Explorer Edge (the new one) for Windows 10 Pro

nigel-dewar commented Dec 18, 2017

Update, Issue is resolved if use another browser. Just cannot use Google Chrome. Even if close chrome completely, restart and still no go

Using Internet Explorer Edge (the new one) for Windows 10 Pro

@wangjian1119

This comment has been minimized.

Show comment
Hide comment
@wangjian1119

wangjian1119 Dec 18, 2017

I also met this problem and asked for a solution.

wangjian1119 commented Dec 18, 2017

I also met this problem and asked for a solution.

@nigel-dewar

This comment has been minimized.

Show comment
Hide comment
@nigel-dewar

nigel-dewar Dec 18, 2017

I can confirm that this was the same issue as #2921

And it is now resolved by doing this

npm install ws@3.3.2 --save-dev --save-exact

Thank you to those who found the fixes.

nigel-dewar commented Dec 18, 2017

I can confirm that this was the same issue as #2921

And it is now resolved by doing this

npm install ws@3.3.2 --save-dev --save-exact

Thank you to those who found the fixes.

@nigel-dewar

This comment has been minimized.

Show comment
Hide comment
@nigel-dewar

nigel-dewar Dec 18, 2017

@wangjian1119 , please find the fix listed above. This works

nigel-dewar commented Dec 18, 2017

@wangjian1119 , please find the fix listed above. This works

@hiuryoliveira

This comment has been minimized.

Show comment
Hide comment
@hiuryoliveira

hiuryoliveira Dec 24, 2017

@nigel-dewar You're right!
I did what you said and was able to solve my problem.

hiuryoliveira commented Dec 24, 2017

@nigel-dewar You're right!
I did what you said and was able to solve my problem.

@nigel-dewar

This comment has been minimized.

Show comment
Hide comment
@nigel-dewar

nigel-dewar Dec 25, 2017

@hiuryoliveira sweet dude glad it workd for you. :-)

nigel-dewar commented Dec 25, 2017

@hiuryoliveira sweet dude glad it workd for you. :-)

@Riyaz0001

This comment has been minimized.

Show comment
Hide comment
@Riyaz0001

Riyaz0001 Jan 3, 2018

@nigel-dewar Thank you, It's work for me.

Riyaz0001 commented Jan 3, 2018

@nigel-dewar Thank you, It's work for me.

@danielehrhardt

This comment has been minimized.

Show comment
Hide comment
@danielehrhardt

danielehrhardt commented Jan 5, 2018

Same here

@izart1994

This comment has been minimized.

Show comment
Hide comment
@izart1994

izart1994 Jan 6, 2018

@nigel-dewar Thank you very. Solved one of my problem

izart1994 commented Jan 6, 2018

@nigel-dewar Thank you very. Solved one of my problem

@pulamusic

This comment has been minimized.

Show comment
Hide comment
@pulamusic

pulamusic Jan 8, 2018

@nigel-dewar Your solution didn't work in my case - still getting error 183. I'll keep poking at it.

pulamusic commented Jan 8, 2018

@nigel-dewar Your solution didn't work in my case - still getting error 183. I'll keep poking at it.

@PrudiviRaj

This comment has been minimized.

Show comment
Hide comment
@PrudiviRaj

PrudiviRaj Jan 9, 2018

Thq it Worked for me

PrudiviRaj commented Jan 9, 2018

Thq it Worked for me

@codyburleson

This comment has been minimized.

Show comment
Hide comment
@codyburleson

codyburleson Jan 11, 2018

I was getting the error just when I hit enter in the Chrome address bar to try to force a reload. npm install ws@3.3.2 --save-dev --save-exact worked for me also.

codyburleson commented Jan 11, 2018

I was getting the error just when I hit enter in the Chrome address bar to try to force a reload. npm install ws@3.3.2 --save-dev --save-exact worked for me also.

@jmmaguigad

This comment has been minimized.

Show comment
Hide comment
@jmmaguigad

jmmaguigad Jan 11, 2018

@nigel-dewar just did what you said and it works. Thank you.

jmmaguigad commented Jan 11, 2018

@nigel-dewar just did what you said and it works. Thank you.

@nigel-dewar

This comment has been minimized.

Show comment
Hide comment
@nigel-dewar

nigel-dewar Jan 11, 2018

nigel-dewar commented Jan 11, 2018

@nanirocks125

This comment has been minimized.

Show comment
Hide comment
@nanirocks125

nanirocks125 Jan 16, 2018

Thank You 👍 👍

nanirocks125 commented Jan 16, 2018

Thank You 👍 👍

@Yogesh1994

This comment has been minimized.

Show comment
Hide comment
@Yogesh1994

Yogesh1994 Jan 25, 2018

npm install @ionic/app-scripts@3.1.6 --save -dev worked for me.

Yogesh1994 commented Jan 25, 2018

npm install @ionic/app-scripts@3.1.6 --save -dev worked for me.

@simonbrazell

This comment has been minimized.

Show comment
Hide comment
@simonbrazell

simonbrazell Jan 31, 2018

Installing "ws": "3.3.2" as a dev dependency did not resolve the issue for me.

@nigel-dewar's fix is a workaround, this should not be closed, needs to be addressed with a new release.

simonbrazell commented Jan 31, 2018

Installing "ws": "3.3.2" as a dev dependency did not resolve the issue for me.

@nigel-dewar's fix is a workaround, this should not be closed, needs to be addressed with a new release.

@shenbagapandian

This comment has been minimized.

Show comment
Hide comment
@shenbagapandian

shenbagapandian Feb 12, 2018

I am trying to convert speech to text using voice base in nexmo. I have faced the issue in WebSocket client. My response error is: info:
Server listening on:8900 info: A client is connected! events.js:183 throw er; // Unhandled 'error' event Error: This socket is closed at Socket._writeGeneric (net.js:726:18) at Socket._write (net.js:786:8) at doWrite (_stream_writable.js:387:12) at writeOrBuffer (_stream_writable.js:373:5) at Socket.Writable.write (_stream_writable.js:290:11) at Socket.write (net.js:704:40) at WebSocketRequest.accept (/home/apptivo/Music/nexmoVoicebaseSample/Nexmo-RTS-Voicebase-master/WS-node/node_modules/websocket/lib/WebSocketRequest.js:450:21) at WebSocketServer.handleUpgrade (/home/apptivo/Music/nexmoVoicebaseSample/Nexmo-RTS-Voicebase-master/WS-node/node_modules/websocket/lib/WebSocketServer.js:216:19) at emitThree (events.js:141:20) at Server.emit (events.js:217:7)
How to resolved this issue ???``

shenbagapandian commented Feb 12, 2018

I am trying to convert speech to text using voice base in nexmo. I have faced the issue in WebSocket client. My response error is: info:
Server listening on:8900 info: A client is connected! events.js:183 throw er; // Unhandled 'error' event Error: This socket is closed at Socket._writeGeneric (net.js:726:18) at Socket._write (net.js:786:8) at doWrite (_stream_writable.js:387:12) at writeOrBuffer (_stream_writable.js:373:5) at Socket.Writable.write (_stream_writable.js:290:11) at Socket.write (net.js:704:40) at WebSocketRequest.accept (/home/apptivo/Music/nexmoVoicebaseSample/Nexmo-RTS-Voicebase-master/WS-node/node_modules/websocket/lib/WebSocketRequest.js:450:21) at WebSocketServer.handleUpgrade (/home/apptivo/Music/nexmoVoicebaseSample/Nexmo-RTS-Voicebase-master/WS-node/node_modules/websocket/lib/WebSocketServer.js:216:19) at emitThree (events.js:141:20) at Server.emit (events.js:217:7)
How to resolved this issue ???``

@vidya47

This comment has been minimized.

Show comment
Hide comment
@vidya47

vidya47 Feb 14, 2018

npm install @ionic/app-scripts@3.1.6 --save -dev did not work for me. I am still waiting for the solution.

vidya47 commented Feb 14, 2018

npm install @ionic/app-scripts@3.1.6 --save -dev did not work for me. I am still waiting for the solution.

@dwieeb

This comment has been minimized.

Show comment
Hide comment
@dwieeb

dwieeb Feb 14, 2018

Contributor

This is an issue with a very general title, so likely the newer comments have similar but different issues. The ws issue was fixed in 3.1.6 by pinning the version. It continues to be pinned in later releases of app-scripts. Ensure you have the latest with these commands:

npm uninstall ws
npm install @ionic/app-scripts@latest

If you are getting an error, please create a new issue and fill out the issue template. Thanks!

Contributor

dwieeb commented Feb 14, 2018

This is an issue with a very general title, so likely the newer comments have similar but different issues. The ws issue was fixed in 3.1.6 by pinning the version. It continues to be pinned in later releases of app-scripts. Ensure you have the latest with these commands:

npm uninstall ws
npm install @ionic/app-scripts@latest

If you are getting an error, please create a new issue and fill out the issue template. Thanks!

@ionic-team ionic-team locked and limited conversation to collaborators Feb 14, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.