TABLE OF CONTENTS
- 1. Firewall Domain
- 2. Streaming Domain Whitelist (in case of streaming-in via RTMP)
- 3. Firewall Domains for other features
Airmeet works with WebRTC, a new technology that might require network configuration within larger companies with secured firewalls.
Suppose you are trying to enter an Airmeet event from work, a school, or a religious organization. In that case, you may run into a Firewall issue, and you may see a black loading screen or an "Unable to connect" warning.
Quick Troubleshooting & basic checks
In case If you are using a VPN to access Airmeet, you should first conduct a mic-cam test at
Quick Troubleshooting ensures the firewall setting allows you to connect on Airmeet.
1. Firewall Domain
If the Firewall setting is identified as an issue, ask your IT department or VPN provider to help.
Here are the items you will need to check with your IT department:
Minimum Requirement: -
Open TCP port 443
Whitelist the following domains
- Ping to airmeet-chat-prod.firebaseio.com should be successful.
- Ping to googleapis.com should be successful.
2. Streaming Domain Whitelist (in case of streaming-in via RTMP)
Whitelist all subdomains of
- litix.io (for Mux Data beacons) and
- mux.com (for video and dashboard-related functionality)
Essentially *.litix.io and *.mux.com. For RTMP-based sessions. Streaming won't be visible if the above domains are blocked in the user system or network.
3. Firewall Domains for other features
Your IT team can also whitelist the below domains for the different features in the Airmeet platform.
Troubleshoot tip: If you don't believe you are behind a firewall but still unable to join Airmeet, please check to see if Stealth Mode is enabled in AdGuard (adblocker).
Airmeet can't detect your firewall settings with this enabled. After disabling Stealth Mode, you should pass the Network Firewall check. Similarly, if you have Kaspersky or any other Antivirus or adblocker installed/enabled, please disable that for the time being.