Invalid stun/turn servers when giving empty public address in Anbox Cloud Appliance init

Bug #2072367 reported by Michele Lo Russo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Anbox Cloud
Fix Released
Medium
Simon Fels

Bug Description

After installing the appliance, I received this error in the console of the browser when joining a session:

Uncaught DOMException: Failed to construct 'RTCPeerConnection': ICE server parsing failed: Invalid hostname format
    at AnboxWebRTCManager._onWsOpen (http://localhost:8406/js/sdk/anbox-stream-sdk.js:2716:16)

Indeed, by inspecting the list of ICE servers received, it turns out that an empty address was being sent:

[
    {
        "urls": [
            "stun:stun.l.google.com:19302"
        ]
    },
    {
        "urls": [
            "stun::5349",
            "turn::5349"
        ],
        "username": <omitted>,
        "credential": <omitted>
    }
]

Steps to reproduce:

1. Do a fresh init of the anbox cloud appliance
2. Provide an empty public IP address
3. Check that the /var/snap/anbox-cloud-appliance/common/agent/config.yaml file ends up with this content:

coturn:
  urls:
  - stun::5349
  - turn::5349

Simon Fels (morphis)
Changed in anbox-cloud:
milestone: none → 1.23.0
assignee: nobody → Simon Fels (morphis)
importance: Undecided → Medium
status: New → In Progress
Gary.Wang (gary-wzl77)
Changed in anbox-cloud:
status: In Progress → Fix Committed
Simon Fels (morphis)
Changed in anbox-cloud:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.