I see an error about Websockets, what should I do?
Due to the nature of Vevox there are many ‘real-time’ components to our dashboard and participant apps with data being passed back and forth regularly. We make use of persistent TCP connections to enable the server to push state changes directly.
To facilitate this, we use websockets and in the case of our dashboard and the HTML web app this is done through port 443 (HTTPS). In the case of the native participant apps (iOS and Android), this is also done on port 443, however the traffic is not HTTPS. Instead, it is TLS-encrypted TCP traffic using a proprietary protocol at the layer 7 (Application) layer.
The persistent connection is a requirement, there is no “fall back” to a non-persistent connection mechanism. Therefore, your network must allow for these sorts of connections otherwise operation will fail. Proxy servers or firewalls that disallow connections of this type should be configured to allow them for Vevox. Also, DPI firewalls/routers that inspect traffic on port 443 and disallow traffic that is not HTTPS should be configured to allow our proprietary connection to succeed.
If you see an error pop up when using your dashboard referencing websockets, the most common reason for this is if you are on a network managed by your organisation or institution which uses proxy or VPN.
You will need to contact your IT department or Network administrator to allow websocket communications in order to use the Vevox dashboard.
What domains do I need to unblock in order to use Vevox?
The following domains need to be accessible for Vevox to work as expected:
What Ports does Vevox use?
We use ports 80 (HTTP) and 443 (HTTPS) for our dashboard and all participant clients (80 is only used to perform a HTTP 301 redirect to the HTTPS port)
Vevox never transmits data over unencrypted channels. All data to/from our systems is encrypted in-transit.