Skip to content
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

Websocket connections lost with Node >= v0.10.0 #24

Open
bvallant opened this issue Apr 12, 2013 · 8 comments
Open

Websocket connections lost with Node >= v0.10.0 #24

bvallant opened this issue Apr 12, 2013 · 8 comments
Milestone

Comments

@bvallant
Copy link

Can't establish any websocket connections due to problems with ECONNRESET:

12 Apr 20:28:00 - (worker #28246) TCP error from     
{"remoteAddress":"127.0.0.1","remotePort":47976,"bytesWritten":10,
"bytesRead":384,"elapsed":0.003}; Error:     
{"code":"ECONNRESET","errno":"ECONNRESET","syscall":"read"}

(with latest version)
Handling of ECONNRESET seems to have changed in the in Node v0.10.
Downgrading Node to v0.9 solved the problem.

@bdon
Copy link

bdon commented Aug 9, 2013

+1. Neither 0.10 nor 0.9.12 worked for me, going all the way back to 0.8.25 did though.

@vlebedev
Copy link

+1

1 similar comment
@andybarlow
Copy link

+1

@sebas5384
Copy link

Having the same problem here :(
+1

@jolos
Copy link

jolos commented Feb 24, 2014

+1, using 0.8.26 does the trick.

@samalba
Copy link
Contributor

samalba commented Feb 24, 2014

Could you test the hipache master branch with node 0.10? I am working on a
new release of hipache based on node 0.10 that will address this issue.

On Monday, February 24, 2014, jolos notifications@github.com wrote:

+1, using 0.8.26 does the trick.


Reply to this email directly or view it on GitHubhttps://github.com//issues/24#issuecomment-35890816
.

@sam_alba

@dmp42 dmp42 added this to the 0.3 milestone Mar 19, 2014
@dmp42
Copy link
Member

dmp42 commented Apr 3, 2014

@samalba web-sockets heads-up: http-party/node-http-proxy#612 - we should likely freeze to http-proxy-1.0.2 until they sort things out

@samalba
Copy link
Contributor

samalba commented Apr 3, 2014

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants