Stefano

So after... several hours of debugging. We **think** we've found the issue. The turnserver recently had an update, I think it has to do with https://github.com/coturn/coturn/releases/tag/4.7.0 We have checked, and...

Nevermind the above comment **partially**, still facing the same issue now. It didn't report the error, but after another restart. The error has returned. I'm back at where I started....

@mlsmaycon No errors in specific: STUN errors from issue above:  Current: ``` Management: Connected to https://vpn.anon-JHcgA.domain:443 Signal: Connected to https://vpn.anon-JHcgA.domain:443 Relays: [stun:vpn.anon-JHcgA.domain:3478] is Available [turn:vpn.anon-JHcgA.domain:3478?transport=udp] is Available [rel://relay.anon-JHcgA.domain:33080] is...

> If you are not experiencing some connectivity issues between your peers, then it should be ok. > > You can confirm that by running `netbird debug for 1m` and...

It has been the relay, it looks like I missed updating the infrastructure files. SInce this is not included in the updates. I assume the system was expecting the relay...

Anyways, thanks for the help @mlsmaycon!

> Has anyone found a fix or workaround for this? So no idea if this solves it *somewhat* for people, but I had the exact issue with using DNS/Domain names....