STUN answered on the wrong node, so kamocrm.com:3478 was dead

FixKlusterServices
Ya
5 Agosti 2026, 01:36 UTC
Mwandishi
Kamo
Ahadi ya
5aa66d6

coturn is hostNetwork with no nodeSelector, so it was scheduled on k3m1 (public 47.181.8.87). Its own --external-ip, and every client's `stun:kamocrm.com:3478`, point at 47.181.8.84 — k1m1. UDP/3478 does reach k1m1 (verified with tcpdump), but nothing was listening there, so every STUN binding request timed out. Consequences: meet clients got no server-reflexive candidates, so P2P could not form between two NAT'd participants; and the videobridge's STUN mapping harvester failed at startup (stunDiscoveryFailed=true), removing the only dynamic source of its public address. Pin coturn to k1m1 so it answers on the address the name resolves to. Verified 3478/udp and the 52000+ relay range are free there.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila moja ya hizi updates ardhi katika nafasi yako ya kazi moja kwa moja. Kuanza bure na kuangalia kukua wiki baada ya wiki.

Kuwa Huru MileleMtazamo wa bei