OctoCue uses a variety of ports and protocols to communicate between:
- Our servers
- The OctoCue clicker app (iOS, Android or browser versions)
- OctoCue Receiver
For maximum compatability, we use standard ports wherever possible, but your network may have restrictions in place that prevent OctoCue from working correctly.
OctoCue uses standard HTTPS for webpage traffic, API requests and WSS for websocket traffic.
The following ports are used by OctoCue to send data to/from our servers:
Standard HTTPS connections as used by many webservers. These handle webpage traffic, static assets and API requests.
Secure websocket connnections. These handle real-time click and show data.
All traffic (both HTTPS and WSS) is sent to/from app.octocue.com
Note that the IP of our server may change over time, so we recommend you allow traffic to the hostname rather than a specific IP address.
This typically occurs when connecting to a show with OctoCue Receiver.
Receiver uses HTTPS to check show codes. If a code is valid, it'll then try to establish a WSS connection, and this is (typically) where things break down. You'll often see the following message on-screen:
Connection Error: unable to get local issuer certificate
The Receiver application is not able to build the correct certificate chain to verify the OctoCue server certificate. This is usually caused by a firewall or proxy server that intercepts HTTPS traffic and replaces the server certificate with its own.
The solution is usually to add an exception to your firewall or proxy server to allow the Receiver to connect using WSS to OctoCue.
Further error details will also be available in the Receiver log file - see Receiver logs for details of how to access these.