-
-
Notifications
You must be signed in to change notification settings - Fork 11
WebSocket connection to 'ws://localhost/websocket' failed #31
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
Comments
Managed to apparently connect to the server by using port 8080, but looking at the console the websocket shows as "Finished" instead of "Switching protocols". |
Hey, regarding your first comment is that if you pass it through a webserver you have to set it up to proxy the websocket connections to What browser are you using? In chrome you can track websocket connections in the developer console. Can you see incoming connection on the Rachet console? |
Thanks for promptly answer. Right, I'm using the chrome developer console, I can see the websocket connection being listed, but its status is marked as "Finished". |
Ok but what is on your console, like you quoted on your first comment? |
This is the full console output
|
So no incoming connection on it, on what port is it running? If you're on linux you can check with: |
I got it fixed, I was connecting to port 8080 in the client, but Ratchet.Connection.websocket.port config was set as 11001. Thanks for your help! |
Cheers, if you have any other questions just shoot 👍 . |
Actually I have also seen this error, and the reason is using Safari to debug. |
Hello. I've started the server successfully from console but after loading page it won't connect to the ws. The error message is "WebSocket connection to 'ws://localhost/websocket' failed: Error during WebSocket handshake: Unexpected response code: 404".
The console task seems to be running normaly, this is the output:
The text was updated successfully, but these errors were encountered: