I have followed the readme and update announcedIp with my AWS static IP. I opened all

Hello <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-ur

No remote stream in chrome/firefox about mediasoup-sfu-webrtc-video-rooms HOT 3 OPEN

dirvann commented on May 18, 2024

No remote stream in chrome/firefox

from mediasoup-sfu-webrtc-video-rooms.

miroslavpejic85 commented on May 18, 2024

Hello @faizul123,
It should work fine on ec2-aws as well. Make sure you've set up all the inbound rules correctly, mainly something like this:

Port range	Protocol	Source	Description
3016	TCP	0.0.0.0/0	App listen on tcp
10000-10100	TCP	0.0.0.0/0	RTC port ranges tcp
10000-10100	UDP	0.0.0.0/0	RTC port ranges udp

Edit config.js:

 announcedIp: 'Public IPv4 address' // 'xx.xxx.xxx.xx'

Then you will be able to access by https://xx.xxx.xxx.xx:3016

Regards

from mediasoup-sfu-webrtc-video-rooms.

jakobheb commented on May 18, 2024

And if you want to use ssl with port 443. Because my application isn't working with port 3016.

from mediasoup-sfu-webrtc-video-rooms.

jakobheb commented on May 18, 2024

I work with digital ocean

from mediasoup-sfu-webrtc-video-rooms.