Strigo is a fully managed solution that runs in the browser, so there are no downloads or installations needed. There are, however, some prerequisites for ensuring a smooth training experience.
Note: We would like to provide an automated tool for testing that all pre-requisites are met prior to attending a training session (it is very high on our roadmap). Until then, please see below.
- A stable internet connection.
- A supported browser (Chrome v51+, Mozilla Firefox).
- A screen resolution of at least 1280x720
Note: You can check which browser you're running here.
Audio / Video requirements
If the training session you are attending is delivered remotely, we highly recommend going through this pre-course system test.
Note: It's important you run the test from the same computer and network you plan to use during the training, and that you use the same camera and microphone.
At the time of the training, we recommend following these guidelines:
- Make sure you don't have other applications running that are using your media devices (microphone, camera, or speakers).
- Disable any ad blockers or script blockers.
- The required bandwidth for video is 300kbps at minimum, and for audio is 50 kbps at minimum.
We recommend going through the list below with your organization's IT admin.
Make sure that:
- Port 443 is open.
- WebSocket traffic is allowed in the organization's firewall (both
Note: You can use this tool to check whether the port is opened and WebSocket traffic is allowed.
These following domains must be accessible to you:
For the main application to work
- *.strigo.io (You can check that it's available by going to https://app.strigo.io)
For Audio/Video to work
For Lab the editor to work
For face-to-face training - where neither audio nor video are used - you don't have to white-list *.opentok.com and *.tokbox.com.
Lab Bandwidth Requirements
- The required bandwidth is expected to be around 5-10mbps (mbit). That's for regular, continuous work within Strigo's labs.
- For less graphical lab interfaces, or for interfaces that have less dynamic movements (i.e. Terminal or rather static Windows/Linux desktop work), even less may suffice.