Firewall Configuration: Agora
Updated 5 months ago
by
Lisvan Reyes Ricardo
If the Virtual Lobby stays in a connecting state or you can’t join a session due to a Network Error, it could mean that your networking is blocking our IP addresses through a Firewall, a Gateway, or a VPN.
If you or your company uses a firewall whitelist to restrict network access to only specific websites or software, you can use the information below to ensure that your service can connect.
You can always test if your connection is going through by running a system check.
Set up your Firewall
Agora services require access to specific ports, so if you have selected Agora as your WebRTC provider, check the following requirements that must be met:
Protocol | Ports | Source | Destination |
TCP | 80, 443 | All InEvent Users | *.inevent.com |
TCP | 80, 443 | All InEvent Users | *.inevent.us |
TCP | 80, 443 | All InEvent Users | *.inevent.uk |
TCP | 443 | Virtual Lobby Users | inevent-virtual-lobby.firebaseapp.com |
TCP | 80; 443; 3433; 5668; 5669; 5866 - 6000; 6080; 6443; 8667; 9667; 30011 – 30013 (for RTMP converter) | Virtual Lobby Users | agora.io .edge.agora.io .agoraio.cn .edge.agoraio.cn |
UDP | 3478; 4700 - 5000 | Virtual Lobby Users | agora.io .edge.agora.io .agoraio.cn .edge.agoraio.cn |
TCP | 9130；9131； 9140 | Virtual Lobby Users | .agora.io |
UDP | 1080; 8000; 8130; 9120; 9121; 9700; 25000 | Virtual Lobby Users | .agora.io |
TCP | 443; 6443; 9591; 9593; 9601 | Virtual Lobby Users | .agora.io .agoraio.cn .edge.agora.io .edge.agoraio.cn ap-web-1.agora.io ap-web-1.agoraio.cn ap-web-2.agora.io ap-web-2.agoraio.cn webcollector-rtm.agora.io logservice-rtm.agora.io webcollector-rtm.agoraio.cn logservice-rtm.agoraio.cn |
TCP | 80, 443 | Virtual Lobby Users |
