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.

Sign up for GitHub

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

Jump to bottom

Socket.IO appears to stop responding. #480

Closed
itguy51 opened this issue Aug 26, 2011 · 3 comments
Closed

Socket.IO appears to stop responding. #480

itguy51 opened this issue Aug 26, 2011 · 3 comments

Comments

@itguy51
Copy link

itguy51 commented Aug 26, 2011

I have a socket.IO server, It works fine non-proxied, but it runs on port 2004, and I want to proxy it through Nginx. I do so, and it does not respond anymore. What's wrong?
@Jellyfrog
Copy link

Can this help (from wiki); http://www.letseehere.com/reverse-proxy-web-sockets

@itguy51
Copy link
Author

itguy51 commented Aug 26, 2011

I followed that, and they are working better than they were, except data isn't being pushed anymore. The server knows I am executing commands, and it is logging around the socket.emit() event, and the client is supposed to get the data, but, it appears not to.

@3rd-Eden
Copy link
Contributor

Closing this as it not a bug caused by socket.io but by a wrapping proxy.

sgress454 added a commit to sgress454/socket.io that referenced this issue Feb 16, 2017
@sgress454
Bump engine.io to version 2.0.2
dfe535d 
Includes the following (from engine.io changelog):

* [fix] Initialize the WebSocket server in the Server constructor (socketio#476)
* [chore] Bump ws to version 1.1.2 (vulnerability fix) (socketio#480)
darrachequesne pushed a commit that referenced this issue Feb 16, 2017
@sgress454 @darrachequesne
[chore] Bump engine.io to version 2.0.2 (#2864)
4d8f68c 
Includes the following (from engine.io changelog):

* [fix] Initialize the WebSocket server in the Server constructor (#476)
* [chore] Bump ws to version 1.1.2 (vulnerability fix) (#480)
@snyk-bot snyk-bot mentioned this issue Oct 26, 2020
Open
@snyk-bot snyk-bot mentioned this issue Oct 28, 2021
Open
@iamstarkdev iamstarkdev mentioned this issue May 17, 2022
Open
@snyk-bot snyk-bot mentioned this issue May 18, 2022
Open
dzad pushed a commit to dzad/socket.io that referenced this issue May 29, 2023
@sgress454 @darrachequesne
[chore] Bump engine.io to version 2.0.2 (socketio#2864)
54d5bab 
Includes the following (from engine.io changelog):

* [fix] Initialize the WebSocket server in the Server constructor (socketio#476)
* [chore] Bump ws to version 1.1.2 (vulnerability fix) (socketio#480)
darrachequesne pushed a commit that referenced this issue Jul 8, 2024
@paulrobello @darrachequesne
[chore] Bump ws to version 1.1.2 (vulnerability fix) (#480)
01e36b4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@3rd-Eden @itguy51 @Jellyfrog