STUN and TURN server errors from AWS ec2 machines

Hi,

I am trying to join a jitsi call with audio/video muted from chrome from an aws ec2 machine and trying to capture screen by ffmpeg.

I am not facing any issues when I run the same from my local ubuntu machine but from remote machines I alway see these errors and I see “fellow participant is having connectivity issues…”. I am using Jitsi global deployment. I did not have any issues till few days back, and have not changed any code from my side. Remote ubuntu server firewall is also inactive

Here is the chrome console log that I see in remote machine

[3818:3818:0820/113951.448307:INFO:CONSOLE(6)] "[modules/statistics/CallStats.js]", source: https://web-cdn.jitsi.net/meetjitsi_3577.307/libs/lib-jitsi-meet.min.js?v=3577.307 (6)
[3892:3951:0820/113951.456569:WARNING:render_delay_buffer.cc(341)] Applying total delay of 5 blocks.
[3892:3950:0820/113951.463179:ERROR:data_channel.cc(49)] Accepting maxRetransmitTime = -1 for backwards compatibility
[3892:3950:0820/113951.464109:WARNING:media_session.cc(316)] Duplicate id found. Reassigning from 104 to 127
[3892:3950:0820/113951.464172:WARNING:media_session.cc(316)] Duplicate id found. Reassigning from 106 to 125
[3892:3950:0820/113951.464249:WARNING:media_session.cc(316)] Duplicate id found. Reassigning from 110 to 124
[3892:3950:0820/113951.464284:WARNING:media_session.cc(316)] Duplicate id found. Reassigning from 112 to 123
[3892:3950:0820/113951.464365:WARNING:media_session.cc(316)] Duplicate id found. Reassigning from 103 to 122
[3892:3950:0820/113951.464426:WARNING:media_session.cc(316)] Duplicate id found. Reassigning from 105 to 121
[3892:3950:0820/113951.464604:WARNING:media_session.cc(316)] Duplicate id found. Reassigning from 111 to 120
[3892:3950:0820/113951.464651:WARNING:media_session.cc(316)] Duplicate id found. Reassigning from 109 to 119
[3892:3950:0820/113951.464715:WARNING:media_session.cc(316)] Duplicate id found. Reassigning from 1 to 14
[3892:3950:0820/113951.464755:WARNING:media_session.cc(316)] Duplicate id found. Reassigning from 2 to 13
[3892:3950:0820/113951.464810:WARNING:media_session.cc(316)] Duplicate id found. Reassigning from 3 to 12
[3892:3950:0820/113951.464862:WARNING:media_session.cc(316)] Duplicate id found. Reassigning from 5 to 11
[3892:3951:0820/113951.541661:WARNING:stun_port.cc(445)] Port[58f99a00:0:1:0:local:Net[any:0:0:0:x:x:x:x:x/0:Wildcard:id=0]]: StunPort: stun host lookup received error 0
[3892:3951:0820/113951.541774:WARNING:stun_port.cc(445)] Port[58f98e00:0:1:0:local:Net[any:0:0:0:x:x:x:x:x/0:Wildcard:id=0]]: StunPort: stun host lookup received error 0
[3892:3951:0820/113951.542119:WARNING:turn_port.cc(800)] Port[58f7a000:0:1:0:relay:Net[any:0:0:0:x:x:x:x:x/0:Wildcard:id=0]]: TURN host lookup received error 0
[3892:3951:0820/113951.542220:WARNING:turn_port.cc(800)] Port[577c0800:0:1:0:relay:Net[any:0:0:0:x:x:x:x:x/0:Wildcard:id=0]]: TURN host lookup received error 0
[3892:3951:0820/113951.542260:WARNING:turn_port.cc(800)] Port[577c0100:0:1:0:relay:Net[any:0:0:0:x:x:x:x:x/0:Wildcard:id=0]]: TURN host lookup received error 0
[3892:3951:0820/113951.542299:WARNING:turn_port.cc(800)] Port[577bfa00:0:1:0:relay:Net[any:0:0:0:x:x:x:x:x/0:Wildcard:id=0]]: TURN host lookup received error 0
[3892:3951:0820/113951.542538:WARNING:turn_port.cc(800)] Port[577bde00:0:1:0:relay:Net[any:0:0:0:x:x:x:x:x/0:Wildcard:id=0]]: TURN host lookup received error 0
[3892:3951:0820/113951.542636:WARNING:turn_port.cc(800)] Port[577bd700:0:1:0:relay:Net[any:0:0:0:x:x:x:x:x/0:Wildcard:id=0]]: TURN host lookup received error 0
[3892:3951:0820/113951.542672:WARNING:turn_port.cc(800)] Port[577bd000:0:1:0:relay:Net[any:0:0:0:x:x:x:x:x/0:Wildcard:id=0]]: TURN host lookup received error 0
[3892:3951:0820/113951.542707:WARNING:turn_port.cc(800)] Port[577cb800:0:1:0:relay:Net[any:0:0:0:x:x:x:x:x/0:Wildcard:id=0]]: TURN host lookup received error 0
[3892:3951:0820/113951.545793:WARNING:turn_port.cc(464)] Socket is bound to the address:172.31.47.65, rather than an address associated with network:Net[any:0.0.0.x/0:Wildcard:id=0]. Still allowing it since it's the 'any' address, possibly caused by multiple_routes being disabled.
[3892:3951:0820/113951.546085:WARNING:turn_port.cc(464)] Socket is bound to the address:172.31.47.65, rather than an address associated with network:Net[any:0.0.0.x/0:Wildcard:id=0]. Still allowing it since it's the 'any' address, possibly caused by multiple_routes being disabled.
[3892:3951:0820/113951.557646:WARNING:turn_port.cc(464)] Socket is bound to the address:172.31.47.65, rather than an address associated with network:Net[any:0.0.0.x/0:Wildcard:id=0]. Still allowing it since it's the 'any' address, possibly caused by multiple_routes being disabled.
[3892:3951:0820/113951.557994:WARNING:turn_port.cc(464)] Socket is bound to the address:172.31.47.65, rather than an address associated with network:Net[any:0.0.0.x/0:Wildcard:id=0]. Still allowing it since it's the 'any' address, possibly caused by multiple_routes being disabled.
[3892:3951:0820/113951.560322:WARNING:turn_port.cc(464)] Socket is bound to the address:172.31.47.65, rather than an address associated with network:Net[any:0.0.0.x/0:Wildcard:id=0]. Still allowing it since it's the 'any' address, possibly caused by multiple_routes being disabled.
[3892:3951:0820/113951.560996:WARNING:turn_port.cc(464)] Socket is bound to the address:172.31.47.65, rather than an address associated with network:Net[any:0.0.0.x/0:Wildcard:id=0]. Still allowing it since it's the 'any' address, possibly caused by multiple_routes being disabled.

Machine inbound and outbound are open for both tcp and udp from anywhere

I am not expert, but I do notice the “Socket is bound to the address:172.31.47.65”
The 172.x.x.x address is an internal IP address (this is different from an external IP of the server).
If a socket is bound to an internal address, is the socket still able to answer an external request from an external IP?

I would assume socket might be bound to an external IP or domain name? Not sure.