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

Server turned off after client not safe disconnection #85

Open
lindevs opened this issue Aug 23, 2016 · 2 comments
Open

Server turned off after client not safe disconnection #85

lindevs opened this issue Aug 23, 2016 · 2 comments

Comments

@lindevs
Copy link

lindevs commented Aug 23, 2016

When client disconnect from websocket server and don't close connection safely, I get error "Socket error: an existing connection was forcibly closed by the remote host" and server closed. How to fix this problem?
@ThePureCC
Copy link

I don't think it's a fatal problem?

@hienngong
Copy link

When client disconnect by wifi disconnected or shut-downed suddenly (for example), my server is suspended and doesn't respond anymore. How to solve this situation?

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
@ThePureCC @lindevs @hienngong