Hi everyone, I’ve spent the past week learning about mediasoup. My video room works fine when running locally, however after I deploy to render.com.
I can’t get the video and audio of other people in the room (black screen). No errors appear, the parameters of consumer and media tracks are returned well. Whether this has something to do with PORT or something, I don’t know I have no experience related to hosting.
These JS objects are just independent local data, doing perfectly well with or without media streams. You should check what happens with the actual WebRTC connections. Look at chrome://webrtc-internals/.
Then you should learn at least some basics about network interfaces and ports. It all starts from there. 127.0.0.1 is the address of the virtual loopback interface, it is not reachable from outside. Announcing it as the server address, you are directing external clients to their own local loopback interfaces.
Hmm, let me spend more time to learn about network interfaces and ports.
I will put my source code in here GitHub - nndang27/video_room . I know you guys are busy but if you can please take a moment to look at my code, it’s pretty simple.
“Network requests from your service to the public internet…” suggests a service that is hosted on this render.com, makes some outbound requests and those requests come with one of the source addresses listed above. But this scenario is not siutable for mediasoup, because mediasoup server does not initiate connections. It just sits listening on some address and accepts inbound requests.
Do run it on a test server first, before running it on something like render.com. Make it running on test server and then move it to renderer or whatever. This renderer may be causing problem in your case so get a small try server, run things there and then figure out what render.com can do for you.