This article is intended for network administrators.
To use all the features of the SpotMe platform, you need to make sure that access to the required hostnames and ports listed below is permitted at all times.
One of the most common reasons why the SpotMe platform can, at times, appear not to be working (or working with limited functionality or degraded performance) is that some of our services are blocked by corporate networks or VPNs.
How the SpotMe platform works
The SpotMe platform consists of a web-based content management system (Backstage CMS) used by corporate administrators and event app used by event attendees. The event app is available on the web, iOS and Android.
The Backstage CMS and event app use several services provided by our partners to deliver the full SpotMe experience, such as push notifications on mobile apps, video conferencing on the web, or 24/7 support chat with our support team.
Required hostnames and ports
The table below describes all required connections for the best SpotMe experience.
All connections are initiated by the Participants or Backstage users and are bi-directional. Your firewall needs to allow outgoing traffic to the listed hostnames and ports.
The hostnames for lines #4 to #6 ( in the table below) change depending on the event's data location:
| Data location | Host names |
| Australia (au) |
au-stream.spotme.com au-content.spotme.com au-channel.spotme.com |
| Europe (eu) |
eu-stream.spotme.com eu-content.spotme.com eu-channel.spotme.com |
| Singapore (ap) |
ap-stream.spotme.com ap-content.spotme.com ap-channel.spotme.com |
| US |
us-stream.spotme.com us-content.spotme.com us-channel.spotme.com |
If your firewall does not support the recommended domain allow-list approach, please contact SpotMe Support for a temporary list of fixed IPs.
If you are intending to use StreamYard, please also refer to the requirements listed here.
| # | From | To | Protocol | Port(s) | Application | Function | |
| 1 | Participants & Backstage users | *.spotme.com | TCP | 443 | HTTPS, WSS | Core SpotMe services | |
| 2 | Participants & Backstage users | *.4pax.com | TCP | 443 | HTTPS, WSS | Legacy SpotMe services | |
| 3 | Participants & Backstage users | install.events | TCP | 443 | HTTPS | Shortlink service for mobile app downloads | |
| 4 | Participants & Backstage users | {region}-stream.spotme.com | TCP | 443 | HTTPS | Content delivery network for live streaming | *1 |
| 5 | Participants & Backstage users | {region}-content.spotme.com | TCP | 443 | HTTPS | Content delivery network for static assets | *1 |
| 6 | Backstage users | {region}-channel.spotme.com | TCP | 10000-10050 | RTMPS | RTMPS ingest service for live streaming | *1 |
| 7 | Participants & Backstage users | *.chime.aws or 99.77.128.0/18 | TCP | 443 |
HTTPS, WSS (signaling) |
Studio video production, in-app video chat, video breakouts | |
| 8 | *.chime.aws or 99.77.128.0/18 | UDP | 3478 | Video and audio data transport | *2 | ||
| 9 | Participants | 17.0.0.0/8 | TCP | 443 | HTTPS | Apple iOS push notification service | |
| 10 | TCP | 5223 | |||||
| 11 | Participants | Google ASN AS15169 | TCP | 5228-5230 | Google Android push notification service | ||
| 12 | UDP | 5228-5230 | |||||
| 13 | Backstage users | *.intercom.io | TCP | 443 | HTTPS | Backstage live support chat | |
| 14 | *.intercomcdn.com | ||||||
| 15 | *.intercomusercontent.com | ||||||
| 16 | *.intercom-sheets.com | ||||||
| 17 | *.intercomassets.com | ||||||
| 18 | *.intercom-attachments.com | ||||||
| 19 | *.intercom-reporting.com | ||||||
| 20 | Backstage users | *.appcues.com | TCP | 443 | HTTPS | Backstage support content | |
| 21 | *.appcues.net | ||||||
| 22 | Backstage users | *.unlayer.com | TCP | 443 | HTTPS | Backstage email editor | |
| 23 | Participants & Backstage users | fonts.googleapis.com | TCP | 443 | HTTPS | Google font service | |
| 24 | fonts.gstatic.com | TCP | 443 | HTTPS | |||
| 25 | Participants | mcusercontent.com | TCP | 443 | HTTPS | Static assets for emails | |
| 26 | Participants & Backstage users | *.browser-intake-datadoghq.com | TCP | 443 | HTTPS | Application performance monitoring | |
| 27 |
Backstage Users |
cdn.cookielaw.org |
TCP |
443 |
HTTPS |
Cookie banner |
|
| 28 |
Backstage Users |
cookie-cdn.cookiepro.com |
TCP |
443 |
HTTPS |
Cookie banner |
|
| 29 |
Backstage Users |
*.onetrust.com |
TCP |
443 |
HTTPS |
Cookie banner |
*1: Replace "{region}" with your event's region: "ap", "au", "eu" or "us".
*2: If your firewall or network appliances do not support domain allow-listing, you must instead allow-list the specified IP ranges (99.77.128.0/18).
Comments
0 comments
Please sign in to leave a comment.