Setting up Lessonspace in a school environment (firewalls, domains and more)

Firewalls may prevent access to Spaces, video, or audio when first establishing Lessonspace in a school environment with strict network limitations. Please check with the school's network manager or IT specialist to ensure that all of the following steps are enabled:

• Make sure to whitelist the wildcard domains for *.room.sh and *.thelessonspace.com. Allowlisting these domains should help in making sure the Lessonspace Spaces are not filtered out by the school.
• If possible, we'd also recommend disabling any layer-7 filtering for the aforementioned hosts too.
• 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.
• If you are able to open a Space but see that it hangs with “Loading…” or “Connecting…” messages, then your firewall is most likely 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 https://.room.sh and https://.thelessonspace.com domains as well.
• In some cases, you may need to activate Relay Mode. 

Setting up the Cobrowser in a school environment:

• If the cobrowser isn’t working as expected in a school environment, it’s likely due to the network blocking the initial connection to our cobrowser provider, Hyperbeam. To resolve this, the school’s IT team should whitelist the domains *.hyperbeam.com and/or *.hiperbeam.com. If granting access to *.hyperbeam.com raises concerns—since it includes the main watchparty platform—allowing only *.hiperbeam.com will ensure the cobrowser functions correctly while restricting access to the watchparty platform.

Because each school firewall is different, extra investigation may be required in order to allow Lessonspace to work on school computers. If you have any questions, please email us at support@thelessonspace.com.