General tips

• If possible, we'd also recommend disabling any layer-7 filtering for the hosts listed below. We can wrap our video traffic in TLS and it has caused false positive detection in the past.
• We recommend testing on a learner's computer, logged in as a learner (or test user with the same level of access) a few days before any real lessons take place, to ensure that everything's working.
• We might add and remove new IP addresses, depending on scaling needs. While we’ll do our best to ensure that these changes happen in off peak times, sometimes a large spike might cause a scale-up. We strongly recommend your firewall refreshes the IP addresses from the hostnames provided at their TTL (60 seconds).

Data Connection

If you’re having issues with data connections, you’ll most likely not be able to load Lessonspace at all. Alternatively, it might partially load - such as getting stuck on a screen saying “Loading…” or “Connecting…”.

Often times, this means your firewall is blocking WebSocket traffic. We recommend searching the user manual of the firewall software you are using to see how to unblock or allow WebSockets on the domains listed below as well.

For data traffic, you’ll need the following hosts allowed in your firewall, for HTTPS traffic (TCP, port 443). These use standard HTTPS requests and WebSockets traffic:

• api.thelessonspace.com
• www.thelessonspace.com
  • Clients who only use the API to access lessons will not need to allow this domain.
• go.room.sh
• {as1,af1,ase2,ue2,uw2,ew2}.room.sh
  • The above IPs are dynamic and served from a CDN, and your firewall needs to ensure it re-resolves addresses periodically (or uses DNS based filtering), to ensure everything is properly allowed.
• stats.room.sh
  • This is the domain we use for recording debugging information. If this domain is blocked, the product will continue to work as expected in all respects, but we will not necessarily be able to identify the cause of any issues clients might experience.
• *.hyperbeam.com and *.hiperbeam.com
  • Only required for customers who use the Cobrowser feature.

Video Connection

<aside> 💡 As of early Feb 2023, there has been an increase in firewall problems for US school districts using the provider iBoss. It’s strongly recommended to follow the instructions below, even if video seems to be working at first glance.

</aside>

If you’re able to get into a space, but can’t see or hear anyone else (empty video boxes show up), or are having problems with a video connection being laggy / suffering frequent dropouts, it’s likely your firewall is blocking the WebRTC traffic we use to carry audio and video data.

While audio and video may still work without adding these, when in a strict firewall environment it’s likely that these will be getting relayed through our TURN server, leading to much reduced performance and possibility of connection problems down the line.

To ensure video traffic can flow freely, you’ll need the following hosts allowed in your firewall, for UDP ports 30000 - 65000. If you know that you’re only using spaces in a particular region, then you only need to add that one, but we strongly recommend adding them all.

• ue2-video.firewall.room.sh