Skip to main content

How to fix the "Failed to resolve address" issue while casting from vibe.run

Resolve 'Failed to resolve address' error when you cast from vibe.run.

This article applies to the Vibe Board S1 55"/S1 75"/Pro 75".

šŸ’” Note:

The issue behavior is your casting from vibe.run keeps dropping or you are unable to send files to the board.

Feedback logs show:

2023-06-28T12:32:34.113304Z ERROR chrome[1800:1800]: [CONSOLE(128)] "ConnectionState: connecting", source: <URL: 24> (128) 
2023-06-28T12:32:34.130285Z ERROR chrome[1800:1800]: [CONSOLE(128)] "ConnectionState: connected", source: <URL: 24> (128)
2023-06-28T12:32:36.093020Z ERROR chrome[2011:2022]: [socket_manager.cc(127)] Failed to resolve address for <UUID: 15>.local., errorcode: -105
2023-06-28T12:45:24.875154Z ERROR chrome[1800:1800]: [CONSOLE(128)] "ConnectionState: disconnected", source: <URL: 24> (128)

Please follow below instructions to try the workaround

  1. Open Chrome on your laptop.

  2. Change the "Enable WebRTC's use of mDNS host addresses" setting to "Disable".

  3. Relaunch Chrome for the changes to take effect.

  4. Attempt to cast again from vibe.run.


šŸ’” Tip

Need more help?


Did this answer your question?