Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running coturn via Docker in AWS results in only private IP for relay #1474

Open
calebtote opened this issue Apr 19, 2024 · 1 comment
Open
Labels
docker Docker image related question

Comments

@calebtote
Copy link

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):

[...]
0.075	srflx	4	udp	xxx.xxx.xxx.xxx	57000	100 | 32285 | 255		
0.076	relay	5	udp	10.53.34.156	65535	5 | 32285 | 255		
0.077	srflx	3	udp	xxx.xxx.xxx.xxx	57000	100 | 32287 | 255		
0.097	srflx	4	udp	xxx.xxx.xxx.xxx	61094	100 | 32285 | 254		
0.097	relay	5	udp	10.53.34.156	65525	5 | 32285 | 254		
0.116	Done

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.

@tyranron tyranron added question docker Docker image related labels Apr 22, 2024
@tyranron
Copy link
Collaborator

@calebtote did you try to specify the relay-ip option too?

Could you also provide the log after start?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docker Docker image related question
Projects
None yet
Development

No branches or pull requests

2 participants