Replies: 1 comment
-
@Maypul there is no mystery in how You may always debug how it works via simple command: docker run --rm coturn/coturn:alpine detect-external-ip As you're behind CloudFlare, I guess that the DNS way, used by it, just doesn't work for you:
You may always write your own docker run --rm -v /path/to/my-detect-external-ip.sh:/usr/local/bin/detect-external-ip.sh coturn/coturn:alpine However, I guess, the alternative HTTP way (like via Moreover, TURN/STUN protocols are not HTTP, so CloudFlare is not able to proxy them. So you simply cannot hide Coturn behind CloudFlare, despite the solution of the original question. |
Beta Was this translation helpful? Give feedback.
-
Hi there, I am trying to understand how coturn works. From what I read, it needs external/public IP (the one that anyone from the internet could connect to me).
But then I try to use detect-external-ip in docker and it seems to always returning local IP addresses. Now I am not sure if Iunderstand it correctly or maybe it does not work. If it does not work ,how could I "improve" it so it detects my public IP?
If I use with ports mapped in docker, it detects docker container IP. If I map container as host, it detects host local ip in addition.
My setup is:
Internet <> router <> router <> host <> docker
Also I am behind cloudflare but I am guessing I would need to use my IP, not proxied from CF? But then, how would I achieve to have it automatic each time container starts (and possibly reboots on change)?
Beta Was this translation helpful? Give feedback.
All reactions