-
Notifications
You must be signed in to change notification settings - Fork 271
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
Socket issue on server #113
Comments
Thanks for the bug report! Are you are running PeerCalls v4 (master branch) or v4? Can you reproduce this bug on https://peercalls.com/alpha if you're running v4? |
Actually I have set up this on ubuntu by git. I install node v8.17.0 and go go1.14.2. When I try to run this on the development by the command And on the browser, I am getting following error on the console WebSocket failed: connection to 'wss://domain/ws/123/kknGxoDSfYpHNIJn4SlDT5' Error during WebSocket handshake: Unexpected response code: 426 I am using https Help will we appreciated |
Are you running Peer Calls behind a proxy server? |
Yes I am using apache as a proxy server |
You need to ensure your proxy is configured to support websocket connections for Peer Calls. I'm using nginx, and it has these settings:
You need to find an equivalent for Apache, possibly the wstunnel module. |
Thank you but already enabled proxy_wstuneel My proxy command like this in host file *ProxyPreserveHost On I also try to change ws path in src/client/ws/index.ts to wss://domain/wss2 But no luck |
Do you have HTTP 2 enabled? |
Yes |
Can you try disabling HTTP/2 for |
Mate thank you for your response I have modified apache config for WebSocket RewriteEngine on and thats it |
Glad you were able to resolve it! |
Socket connection error
A clear and concise description of what the bug is.
WebSocket connection to 'wss://demovideo.my-domain.com/ws/123/za80HWiFPN4H4LGAHyIAc7' failed: Error during WebSocket handshake: Unexpected response code: 426
The text was updated successfully, but these errors were encountered: