Gatherly whitelisting guide

Whitelisting the event domain

In order to ensure that users can access a Gatherly event, the following URLs must be whitelisted:

*.gatherly.io
*.event.gatherly.io

Additionally, any query parameters should be allowed on these URLs as well. For example, the base URL for a Gatherly event (e.g. example.event.gatherly.io) as well as a version of the URL with query parameters (e.g. example.event.gatherly.io/?uuid=rHfoo1e4HwzKuDDbEghGtd&color=Izk3MTQxNA%3D%3D) should also be accessible.

Whitelisting 3rd party video chat services

Gatherly uses two different 3rd party video chat service providers — Agora for broadcasting and Amazon Chime for huddles. To ensure full functionality of Gatherly, network administrators should ensure that both services are properly whitelisted.

Agora (source)

If users are reporting issues of not being able to see or hear broadcasts on Gatherly, this may be due to Agora being blocked.

Please add the following destinations and corresponding ports to the firewall whitelist:

.agora.io
.edge.agora.io
.agoraio.cn
.edge.agoraio.cn
.sd-rtn.com
.edge.sd-rtn.com

Chime (source)

If users are reporting issues of not being able to see or hear other users in huddles on Gatherly, this may be due to Amazon Chime being blocked.

Please add the following destination domains and the corresponding ports to the firewall whitelist:

Amazon Chime uses Amazon Elastic Compute Cloud (Amazon EC2) and other AWS services on port TCP/443. If your firewall blocks port TCP/443, you must put *.amazonaws.com on an allow list, or put AWS IP address ranges in the AWS General Reference for the following services:

• Amazon EC2

• Amazon CloudFront

• Amazon Route 53

Questions? Reach out to the Gatherly team directly with a message by clicking the blue chat icon.