To test your device and your network compliance with Furioos, you can use our Troubleshooter.

This tool will help you understand why your device might not be compatible with Furioos.
It will establish a diagnosis and create a report for you to take the right actions.

To begin with the test, click on “Test My Connection” (1)

The troubleshooter will start a connection with a Furioos server to test your compatibility.

Once connected, the troubleshooter will run a series of tests in order to detect potential issues.

Depending on the results the diagnosis will be different.

Browser and Network Compatibility

The troubleshooter will first test your browser/device compatibility with Websocket and WebRTC. (First three tests)
If it is not compliant, try to update browser, or use a different browser (Chrome, Firefox, Safari with last versions will  work)

STUN / TURN Servers

Then it will try to reach out to STUN and TURN servers, used to establish a link with a stream.
There will always be 4 different servers, 3 come from a Furioos Virtual Machine (STUN, using UDP 443, then TURN using UDP 443, then TCP 443, and last, a Google STUN server using UDP 19302). The displayed IP is dynamic, so it will always change.

If this step does not succeed, contact your system administrator to open the rights ports on your network.

Reflexive, UDP and TCP Connections

Reflexive Connectivity 

If this is not available, this is a not a blocking issue, performance will be a little bit degraded, but most of users won’t be able to notice, this will not change the final result (device still considered as fully compatible with Furioos even if this test does not pass)

It will not work in a lot of cases, a lot a company networks are not compatible with reflexive connectivity, so that is why we then use relay connectivity

UDP Relay Connectivity

This test needs to establish a UDP connection on port 443.
If the Reflexive Connectivity test does not succed and this one neither. The next test (TCP Relay) must pass otherwise there will be no way to use Furioos. Keep in mind that performance using UDP 443 relay is not as good as a reflexive connection, but better than a TCP relay connection. If this test and the previous one do not pass, the final result will be a warning (orange card).

To make this test pass, allow UDP 443 on GCP VM IPs (all of them as we do not have any IP address to provide).

TCP Relay Connectivity

Only needed if no reflexive connection and UDP relay connection could be established. It needs to be able to establish a connection to the GCP VM using the TCP 443 port.
Performance will be impacted if only this connection is available, but Furioos remains usable, but not in optimal conditions.

To make this test pass, allow TCP 443 on GCP VM IPs (all of them as we do not have any IP address to provide).

Result

In the result page, you will have access to the diagnosis and a report.

You will be able to detect issues and correct your configuration thanks to the provided details.