Troubleshoot streaming issues
Debugging issues that occur when streaming your application can be tricky. The following instructions give you some pointers on how to start tracking down streaming issues.
First of all, check the error message that occurs. Unfortunately, it is often hard to determine why a connection fails, which is why the error message does not always give a clear indication of the source of the error. Typical errors are covered though, so in these cases, the error message should give you an idea on where to look.
If the error message does not help, check the WebRTC debug information. You can find this information in your browser:
- In Google Chrome, go to
- In Mozilla Firefox, go to
You can create a dump of the debug information by expanding the Create Dump section (in Chrome) or clicking Save Page (in Firefox).
Analyse the dump to find the source of the error, or provide it to Anbox Cloud’s support team for help.
Streaming does not start
If streaming does not start, there is usually a connection problem.
If you are using the web dashboard and, for example, creating an application works as expected, the connection problem is not that the web dashboard cannot reach Anbox Cloud. Most likely, there are some security rules in place that prevent WebRTC from establishing a connection. In this case, check your firewall configuration and VPN setup.
In the WebRTC logs, check whether the connection was established.
(Screen capture taken in Chrome)
If the connection could not be established, check the table of ICE candidates. The ICE state of the different candidates should help you identify where the problem lies.
(Screen capture taken in Firefox)
Streaming works badly and stalls
If streaming starts, but keeps stalling and the quality is bad, the reason is usually a bad network connection. The connection can be established, but something is going wrong when transferring packets.
In this case, check the WebRTC log to see if there is a high packet loss, and if so, in what situations it occurs. Most likely it is due to a bad network connection between the web dashboard (or your client application) and Anbox Cloud.
See About performance > Client devices for more information.
Last updated a month ago.