This message was deleted.

I did solve this issue. TURN/TLS on chrome must use TRUN/TLS default port 3478. Thank you.

@calm-yak-90435 can you say more about that? what did you change in the config in order to get it to work?

@dry-elephant-14928 hello. I followed the config at "livekit/config-sample.yaml line 207"

# # defaults to 3478 - recommended to 443 if not running HTTP3/QUIC server

But I got error only on chrome based browser such as chrome or edge. And then, I found chrome must use default port TURN/TLS somewhere on blog. I changed TURN/TLS port 443 to 3478 and I got all pass.

hey @calm-yak-90435, we are using 443 to optimize for firewall accessibility as documented here. I'll test what you've suggested. I don't remember Chrome having an issue with 443 previously.

@dry-elephant-14928 thank you for your quick reply. When you're ready please share your test result please.

443 is working well for me. Do you have it open on the firewall by any chance? keep in mind that it's 443 for UDP that needs to be exposed.

For test i did open any udp and tcp port for any source but not worked on chrome. Did you test on connection test on chrome browser? In my case, after i changed 443 to 3478 then i got all pass green light on connection test on chrome. https://livekit.io/connection-test

yeah I did test with Chrome. using our vm deployment. In either case, we'll change the default port to 3478 since there appears to be more conflicts over 443

Thank you for your reply and good product!