Most reported issues related to connectivity to the real-time database are intermittent and resolved by a workaround. However, some issues arise from client or network configurations (e.g. firewalls and network blocking) that may be difficult to troubleshoot.
Bandwidth requirements
As a general rule, a reliable average connection of at least 50 KB/s per attendee is enough to guarantee steady performance with Conferences i/o. This is most important during in-person gatherings where many devices will be connecting to a local network.
Firebase connectivity
- Conferences i/o cannot function without an active connection to Firebase.
- View Firebase's status to ensure a connection can be made: https://status.firebase.google.com/
Note: Conferences i/o's support and engineering teams are constantly monitoring the status of the Firebase service. If an outage negatively impacts an event, contact Conferences i/o support for more information.
Required services and domains
- Below are the services and domains that Conferences i/o requires in order to function
- If applicable, contact the appropriate technical support teams to ensure these services and domains are added to any corporate allow lists, firewalls, or proxies
| Service Needed | Reason |
|---|---|
| JavaScript | Critical for real-time services |
| jQuery | Critical for real-time services |
| Websockets | Primary and most reliable real-time connection |
| Long-polling (repeated requests to a remote server) | A backup if websockets are not available |
| Port 443 | All Conferences i/o resources and connections use SSL on port 443 |
| Domain Needed | Use Case |
|---|---|
| *.cnf.io | Conferences i/o core application |
| teamsapp.conferences.io | Conferences i/o Teams and Zoom apps |
| cnf.firebaseio.com | Real-time database service (via Firebase) |
| d3r1vvs66lg0fx.cloudfront.net | CDN for user assets, like uploaded logos |