Anbox stream failed Error: signaling timed out

[chaowen guo]

I install anbox cloud on oracle cloud 4ocpu 24g memeory 100G disk. I follow:
https://anbox-cloud.io/docs/tut/installing-appliance and https://anbox-cloud.io/docs/tut/getting-started-dashboard and then I get Anbox stream failed Error: signaling timed out in the 2. Launch and test the virtual device step 3 When the stream has loaded, you can interact with your virtual device. You can see that in the attachment stream.png

[Simon Fels (morphis)]

Hey Chaowen,

can you provide us the output of

$ sudo anbox-cloud-appliance.buginfo

Furthermore have you opened all ports in the security group for the instance as documented on https://anbox-cloud.io/docs/ref/network-ports#appliance?

[chaowen guo (chaowenguo)]

the output of $ sudo anbox-cloud-appliance.buginfo is in the attachment bug.txt and I already open all the ports in the oci vm.

[chaowen guo (chaowenguo)]

I see there is 2023-06-20T10:46:08Z anbox-cloud-appliance.bootstrapper[8446]: Error: Failed to run bootstrap process, you can find more information at /var/snap/anbox-cloud-appliance/common/logs/bootstrap.log in the bug.txt. I copy the bootstrap.log in the attachment

[Simon Fels (morphis)]

Thanks!

Can you give us also the output of

$ amc exec cicn3s78dq6093s8d5k0 -- journalctl --no-pager

[Simon Fels (morphis)]

> 2023-06-20T10:46:08Z anbox-cloud-appliance.bootstrapper[8446]: Error: Failed to run bootstrap process

That can be ignored. It looks like you ran the bootstrap process twice. The appliance is correctly setup from what I see in the logs.

[chaowen guo (chaowenguo)]

the output of $ amc exec cicn3s78dq6093s8d5k0 -- journalctl --no-pager is journalctl.txt which is in the attachment

[Simon Fels (morphis)]

Thanks!

It looks like both sides fail to establish a connection over the signaling layer.

Are there any errors in the web console of your browser? I see you use chromium so you will need to enable the web dev tools to see the console (see https://developer.chrome.com/docs/devtools/open/).

[chaowen guo (chaowenguo)]

In the console:

Mixed Content: The page at 'https://192.9.129.20/sessions/cicn3s78dq6c2rvmnl80' was loaded over HTTPS, but requested an insecure element 'https://192.9.129.20/assets/Anbox_Logo-7562962b.svg'. This request was not upgraded to HTTPS because its URL's host is an IP address.
cicn3s78dq6c2rvmnl80:1 Mixed Content: The page at 'https://192.9.129.20/sessions/cicn3s78dq6c2rvmnl80' was loaded over HTTPS, but requested an insecure element 'https://192.9.129.20/assets/Anbox_Logo-7562962b.svg'. This request was not upgraded to HTTPS because its URL's host is an IP address.
index-a8b94cc2.js:3 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu
_createPlaceholderAudioTrack @ index-a8b94cc2.js:3
index-a8b94cc2.js:3 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu
_createPlaceholderAudioTrack @ index-a8b94cc2.js:3
cicn3s78dq6c2rvmnl80:1 Uncaught (in promise) DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: The order of m-lines in answer doesn't match order in offer. Rejecting answer.

[Simon Fels (morphis)]

> cicn3s78dq6c2rvmnl80:1 Uncaught (in promise) DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: The order of m-lines in answer doesn't match order in offer. Rejecting answer.

That is the problematic part here. What browser are you running? Name and exact version would be helpful.

[chaowen guo (chaowenguo)]

Chromium
Version 114.0.5735.106 (Official Build) snap (64-bit)
run in ubuntu 22.04

[chaowen guo (chaowenguo)]

I also try
Google Chrome
Version 114.0.5735.133 (Official Build) (64-bit)
run in linuxmint
the same problem appear.

[chaowen guo (chaowenguo)]

I may figure out part of the problem. I did not open firewall for udp traffic. Now I open traffic for all tcp and udp and create a new container, a new session. Now the problem is sometime working, sometime not working

[Simon Fels (morphis)]

> Now I open traffic for all tcp and udp and create a new container

What do you mean by "all tcp and udp"?

[Gary.Wang (gary-wzl77)]

The error message in the above logs has implied that something is wrong during the signaling.

```
cicn3s78dq6c2rvmnl80:1 Uncaught (in promise) DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: The order of m-lines in answer doesn't match order in offer. Rejecting answer.
```
I don't think it's related to the browser the chaowen has been using.
The issue here was that: the Anbox Cloud that chaowen has deployed on OCI may not be as near as possible. So when he tried to create/join a new session, due to the fact that a short timeout of discover message(0.5), the client used the fallback API for the signaling, which will send the settings and answer to the container via the chain(gw->nats->agent). However later the `resp:discover` message was arriving on the client side. With our current SDK, we will send the settings and offer second time.
So from the chrome:://webrtc-internals, we'll see there're 6 lines of `m-lines` in the offer

https://pastebin.ubuntu.com/p/FBdn9yXM4h/

but 3 lines of 'm-lines' in the answer received by the client.

https://pastebin.ubuntu.com/p/nWCtS5fyxk/

This essentially caused the issue you saw in the console.
```
cicn3s78dq6c2rvmnl80:1 Uncaught (in promise) DOMException: Failed to execute 'setRemoteDescription' on 'RTCPeerConnection': Failed to set remote answer sdp: The order of m-lines in answer doesn't match order in offer. Rejecting answer.
```
I can easily reproduce the same issue when streaming from China and connecting to the Anbox Cloud deployed APAC or US.

What you saw the following
```
Now the problem is sometime working, sometime not working
```
has nothing to do with open ports. It totally depends on the network condition the time you launch the stream. If it worked for you, it implies the the timeout of the discover message didn't occur and API version 2 is in use in this case while API version 1 is in use but a bug in JS SDK blocked the signaling process due to the above bug.

There is a fix for this but need to discuss with the team internally how we deliver this and in which version.

BR
Gary