This article outlines the network configuration and allowlisting required to ensure full communication between EloView 3 and managed devices.
Table of Contents
- Overview
- Required Domains to Allowlist
- Additional IP Allowlisting
- Port Requirements
- Additional Notes
- Gipper-Specific Domains
Overview
To ensure proper device management and content delivery, EloView requires specific domains, ports, and optional IP addresses to be accessible on your network.
Required Domains to Allowlist
The following EloView domains must be allowlisted to enable essential cloud-to-device communication:
| Purpose | Domain |
|---|---|
| Core services | io.eloview.com |
| Portal access | manage.eloview.com |
| Content download | content.eloview.com |
| Device log uploads | device.eloview.com |
| Device status queries | dsq.eloview.com |
Additional IP Allowlisting
While domain allowlisting is strongly recommended, some networks may require explicit IPs.
Armor Hosts
- 74.120.218.143
- 74.120.218.144
Cloudflare CDN (Content Delivery Network)
Note: These IP addresses are dynamic and may change. It is strongly recommended to allowlist the domains listed above instead of individual IPs to avoid service interruptions.
IPv4
- 104.16.64.227
- 104.16.61.227
- 104.16.62.227
- 104.16.63.227
- 104.16.60.227
IPv6
- 2606:4700::6810:3fe3
- 2606:4700::6810:3ee3
- 2606:4700::6810:3ce3
- 2606:4700::6810:40e3
- 2606:4700::6810:3de3
Port Requirements
The following ports must be open to allow Elo devices to connect properly:
- Port 443 (HTTPS): Full access to all EloView domains (*.eloview.com) is required.
-
Port 123 (NTP): Required for time synchronization via
2.android.pool.ntp.org.
Additional Notes
- EloView-enabled Android devices use WebSocket (WSS) for secure, persistent communication with the EloView cloud.
- WebSocket sessions are initiated by the device, not the network.
Gipper-Specific Domains and Links
Please request that IT place the following domains on a safe/do not block list to ensure you can use the Gipper platform to the fullest extent:
*.gogipper.com
https://platform.gogipper.com
https://display.gogipper.com
https://view.gogipper.com
https://contentrequests.gogipper.com
https://www.gipper.com
https://analytics-api.gogipper.com
https://platform-api.gogipper.com
https://templates-api.gogipper.com
https://dzfa1uifb0sb6.cloudfront.net
https://d2apt9kpoa4p1o.cloudfront.net
https://d1txs74qdv0iht.cloudfront.net
https://stripe.com
https://platform-gipper.s3.us-east-1.amazonaws.com
https://gipper-static-assets.s3.us-east-1.amazonaws.com
Additionally, to make sure you are receiving all communications from Gipper, it is best to allowlist/allow all emails coming from the domains @gogipper.com, @gipper.com, and the following emails:
support@gogipper.com
customersuccess@gogipper.com
team@gogipper.com
billing@gogipper.com
Still have questions? Our team is here to help. Reach out anytime at support@gogipper.com or through the chat in your Gipper dashboard.