You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
We're trying to run coturn in AWS via Docker.
We have set the config to autodetect our interface but it continually binds to the private IP of the docker container and not the public IP of the EC2 host.
We are launching docker in --network host mode.
We are not behind a NAT at all
When I test using Trickle ICE, I get this output (my public IP redacted with xxx):
This relay IP is the private IP in our docker container. Am I correct in understanding that this should be the public IP of the EC2 instance? If so, what can we try to make this correct? If we manually set our external-ip=<ec2 public IP> in the config I just get no relay endpoints returned at all from Trickle ICE.
The text was updated successfully, but these errors were encountered:
Hi there,
We're trying to run coturn in AWS via Docker.
When I test using Trickle ICE, I get this output (my public IP redacted with xxx):
This relay IP is the private IP in our docker container. Am I correct in understanding that this should be the public IP of the EC2 instance? If so, what can we try to make this correct? If we manually set our
external-ip=<ec2 public IP>
in the config I just get no relay endpoints returned at all from Trickle ICE.The text was updated successfully, but these errors were encountered: