Articles in this section
Category / Section

How to Whitelist Zuddl Domains and Ports

Published:
2 mins read
Updated:

Zuddl uses WebRTC technology for its real-time engagement functions and requires network configuration for environments with restricted access. If you are behind a firewall or a VPN and are trying to attend an event, you may encounter errors or connection failures.

This set up may require you to reach out to your IT team.

In order to prevent such failures, Zuddl recommends whitelisting certain domains and ports, thereby providing a faster and efficient service and an overall better meeting experience. The illustration below depicts how you can whitelist Zuddl and WebRTC ports and domains to grant access to your resources through a firewall or across a VPN.

Whitelist ports to grant access


Function-wise whitelisting

FunctionDomainsTCPUDPWebsockets
Zuddl CDN

*.zuddl.com

*.mux.com

*.imgix.net

*.pusher.com

443

WebRTC (Audio & Video)

*.agora.io

*.edge.agora.io

*.sd-rtn.com

*.edge.sd-rtn.com

80

443

3433

4700 - 5000

5668

5669

6080

6443

8667

9667

3478

4700 - 5000

✔️
Pusher websocketsws-ap2.pusher.com443
✔️

Zuddl large rooms network infrastructure


*.daily.co

*.wss.daily.co


443


3478



✔️

If the above whitelisting cannot be implemented because your organization uses a stricter firewall with many restrictions, please reach out to our customer success manager.

Note on websockets:

Websockets need to be allowed on the device browsers (like Google Chrome, Microsoft Edge, etc.) and also in the network whitelist.

Was this article useful?
Yes
No
Help us improve this page
Please provide feedback or comments
Comments (0)
Please  to leave a comment
Access denied
Access denied