-
Notifications
You must be signed in to change notification settings - Fork 47
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
Conflict with socket.io #58
Comments
Reload uses ws. It's a possible port conflict issue I imagine. Reload needs to support cutsom config for port as right now it uses the appplication's port. So opening your own WebSocket can cause a conflict. A temporary fix would be to move your WebSocket to another port. I will open an issue on reload supporting custom ports for WebSockets now. |
Thanks |
Okay with closing this? |
Sure |
Okay great thanks for the issue, feel free to track the status of this over at #61. |
I have an app that uses both reload and socket.io, and the browser console shows an error:
When I don't use reload, the error doesn't appear.
Despite the error, socket.io still works for me, strangely. I want to eliminate the annoying error message though.
I'm assuming reload uses socket.io too. I thought that there might be a path conflict, so I tried using a different path for socket.io (/sock instead of /socket.io), but it didn't help.
The text was updated successfully, but these errors were encountered: