Gatherly whitelisting guide
Carl Liu avatar
Written by Carl Liu
Updated over a week ago

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

Video chat on Gatherly is powered by, Amazon Chime, a 3rd party video chat service provider. To ensure full functionality of Gatherly, network administrators should ensure that Amazon Chime is properly whitelisted.

Chime (source)

If users are reporting issues of not being able to see or hear other users 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:

Destination

Ports

chime.aws

TCP/443

*.chime.aws

TCP/443

*.amazonaws.com

TCP/443

99.77.128.0/18

TCP/443

99.77.128.0/18

UDP/3478

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.

Did this answer your question?