Firewall or proxy restrictions might prevent you from running Session on your device. We recommend using the following guide to troubleshoot any firewall issues you may encounter.
Allowed Domains
Session uses a combination of primary/in-house and third-party services during normal use. The following domains should be included in a firewall allowed list:
*.session.com
*.hopin.to
*.hopin.com
*.videoml.team
chat.stream-io-api.com
*.launchdarkly.com
*.segmentapis.com
*.datadoghq.eu
images.unsplash.com
cmp.osano.com
Ports
Minimum Requirements:
The minimum requirement is that TCP port 443 is open. Some firewall/proxy rules only allow for SSL traffic over port 443. You will need to make sure that non-web traffic can also pass over this port.
Better Experience:
In addition to the minimum requirements being met, we also recommend that TCP & UDP ports 3478 be open, which is the default port for the STUN and TURN network protocols. STUN and TURN are used for realtime voice/video and messaging and blocked connectivity may disrupt video and chat functionality. We recommend not to block this traffic.
Best Experience:
For the best possible user experience, UDP ports 1025 - 65535 should be open for users. Opening this port range allows for audio/video network routes that may otherwise be relayed, which can have an adverse effect on interactive performance.
Country Firewalls
There is no official database of firewalls and blocked site by country. However, you can find an unofficial list of countries who filter access.
Some countries block access to popular sites that Session integrates with, such as Google, which includes putting our YouTube integration and Google sharing features at risk of being blocked.
Some tips:
- Try using a private VPN (if you work at a global company or use company-owned devices, you may already have one installed that you can use).
- If other attendees/hosts are joining from a country where firewalls are blocking their access, we recommend having them join early to test their connectivity. You could also try having hosts pre-record their sessions.
cheese