As the title message shows, I’ve recently starting experiencing this issue when connecting to the same laptop. After rebooting the laptop and Comet RM1 this didn’t help.
I did however find the only way it seems around this is to flip the Video > Transfer settings from Web RTC to Direct which brings up the video and then flip it back to WebRTC and it keeps running fine (until the next power cycle).
I have generated a log bundle ready to go if required.
I've looked at your logs, and I think I understand the issue. You must have blocked our device from accessing the internet on the router. So, when our device starts up, it spends over two minutes trying to connect to the STUN server, but ultimately fails. During this attempt, WebRTC cannot function properly.
Hi, I found the issue now you provided that info - I had a defunct DNS server referenced in the static IP configuration which doesn't exist since I switched my router to to a GL-MT6000. The moment I put the correct DNS server in place everything sprung to life.