Closed xplatsolutions closed 4 years ago
I noticed that the WebSocket.Server
log message WebSocket.Server started at port 8080
never actually printed in my console, sounds like I am missing some configuration;
Unrelated to mediasoup, is the wss url correct? Does the connection timeout after a while? Can you connect from another websocket?
Yes, I know :/ you can close if you want, was just looking for some help to debug this.
Shouldn't the was URL be my local IP; wss://192.168.2.2:443, I didn't change the scheme from what you had, only the IP address point to my local. What do you mean to connect from another WebSocket?
I think I will try with the sample server from mediasoup site using an Express layer.
The url should reference the ip of which the server is running.
What do you mean to connect from another WebSocket?
Create a simple HTML page that connects to your websocket server, and see if that works.
You could also use tools like tcpdump on the server to see if it's actually receiving any tcp packets on connect. Also check to make sure the 443 port on your server is actually listening.
Thanks will check it out. Actually the server is running localhost.
Without touching the sample-media-server and just changing the config.js
listenIps: [ { ip: '192.168.2.2', announcedIp: undefined } ],
to my local IP address it seems that my client application refuses to show any sign of connection. I haven't touched the SSL certs from the sample-media-server repo.I am using the below pods
Starscream made some minor changes so I had to change EchoSocket to the below initialization.
Below is my code, trying to keep it short to make sure I understand the steps.
Server starting successfully
Config.js
Any help how to debug is appreciated