Whitelisting for Viewing Experiences
If you are unable to view Experiences on GMetri on certain networks, which is commonly the case on corporate and university networks, it may be required to whitelist GMetri's servers and ports so that they are not blocked by the firewall.
These domains cover the bare minimum domains that need to be whitelisted for any GMetri experience to run.
- 1.
*.gmetri.com - 2.
*.vrgmetri.com
We use ReadyPlayerMe as our 3D avatar provider. Users can log in to their own RPM account and import their avatars into GMetri, our create a new one as guests.
- 1.
readyplayer.me - 2.
cname.vercel-dns.com - 3.
avatars.readyplayer.me - 4.
d1a370nemizbjq.cloudfront.net
We use a number of services to keep GMetri systems functional and support advanced features.
These are required for Google SSO and location tracking. These are optional but are required is you're looking to use Social and Google Auth for your GMetri Experiences
- 1.
*.googleapis.com - 2.
developers.google.com
These are required for any remote debugging issues at the user's end. We use Trackjs to collect any errors reported on users' devices.
- 1.
*.trackjs.com
We use Agora as our service provider for all Multiplayer and Collaborative features. This is a must if you intend to use Multiplayer/Collaborative features such as Voice calls, Video calls, Screen-share, and Chat.
- 1.
*.agora.io - 2.
*.edge.agora.io - 3.
*.sd-rtn.com - 4.
*.edge.sd-rtn.com - 5.
web-1.ap.sd-rtn.com - 6.
web-2.ap.sd-rtn.com - 7.
ap-web-1.agora.io - 8.
ap-web-2.agora.io - 9.
webcollector-rtm.agora.io - 10.
logservice-rtm.agora.io - 11.
rtm.statscollector.sd-rtn.com - 12.
rtm.logservice.sd-rtn.com
Additionally, you may also need to expose certain ports on your network if there are any restrictions added to the firewall
Destination ports | Port type |
|---|---|
80; 443; 3433; 4700 - 5000; 5668; 5669; 6080; 6443; 8667; 9591; 9593; 9601; 9667; 30011 - 30013 (for RTMP converter) | TCP |
3478; 4700 - 5000 | UDP |
Last modified 3mo ago