#876·coturn

coTURN behind load balancer in kubernetes

Author: DrZoidberg09Created Jan 7, 2022Updated Feb 27, 2026
Labelsquestion

Hi there,

I am trying to deploy in a Kubernetes environment behind a load balancer using the tcp-proxy option of coTURN.

So far, the coTURN deployment is reachable via Port 5555 using proxy-protocol on the load-balancer and the nginx-ingress.

However, I cannot get a TURN connection.

These are the most interesting parts of the log (IMO) that might explain it:

2035: : Trying to bind fd 58 to <_POD-IP_:39340>: errno=99 2035: : Trying to bind fd 58 to <POD-IP_:43541>: errno=99 2035: : Trying to bind fd 58 to <POD-IP_:38760>: errno=99 2035: : Trying to bind fd 58 to <POD-IP_:60732>: errno=99 2035: : Trying to bind fd 58 to <POD-IP_:50115>: errno=99 2035: : Trying to bind fd 58 to <POD-IP_:39340>: errno=99 2035: : Trying to bind fd 58 to <POD-IP_:44143>: errno=99 2035: : session 001000000000000172: realm <_REALM_> user <1641550838:turn-test-user>: incoming packet ALLOCATE processed, error 508: Cannot create socket 2035: : session 001000000000000172: realm <REALM_> user <1641550838:turn-test-user>: incoming packet message processed, error 508: Cannot create socket

In the turnserver.conf I have tried to work with:

Relay-IP (Eventually I left it undefined as it is supposed to be the internal IP and the POD-IP is changing each time) External-IP (Here I use the IP of the LoadBalancer) Listener-IP (Eventually I left it undefined as it is supposed to be the internal IP and the POD-IP is changing each time) Realm (the domain name of the coTURN deployment)

Any suggestions where to look would be really great, as I am not even sure what to check...

Thank you so much!