Restoring Access to EloView 3 Following End of Life (EOL) via IP Allowlisting
Audience: Public / Elo Customers, IT Administrators, Network Engineers, and Support Teams
Article type: Support and Troubleshooting Guide
⚠️ EloView 3 End-of-Life (EOL) Access Notice:
EloView® 3 reached official End of Life (EOL) on September 15. All general, public traffic to legacy EloView 3 servers is now blocked by default, causing un-migrated devices to appear offline and preventing administrators from signing into the portal.
If you have lost access to your EloView 3 account and need additional time to complete your transition to EloView® 4, follow the instructions below to submit your public IP addresses and restore temporary connectivity for both your devices and admin users.
Temporary Access Timeline & Hard Deadlines
This exception is provided strictly as a temporary bridge to complete active migration efforts:
| Deadline Date | Operational Impact |
|---|---|
| December 30, 2026 | Temporary Allowlist Access Ends: All IP allowlist exceptions will expire. All customer portal access and device connectivity to EloView 3 will permanently end. |
| January 15, 2027 | Server Decommissioning: Legacy EloView 3 backend infrastructure will be permanently shut down. |
How to Collect Your Public Egress IP Addresses
To allow your deployed devices to connect and enable your administrators to log in, you must provide the public outbound (egress) IP addresses for all physical locations where devices or support personnel operate.
-
Identify Support & Administrator Locations:
From a computer or laptop connected to the same network as your support/admin personnel (office network, VPN gateway, or remote workspace), open a browser and visit:Record the displayed public IPv4 address (or IPv6 address). This is required so your administrators can authenticate and manage the portal.
-
Identify Device Locations (Stores, Warehouses, Staging Depots):
From a device, laptop, or phone connected to the exact same local Wi-Fi or Ethernet network where your EloView devices are installed, visit whatismyip.com to capture the site's public gateway IP address. This enables the devices to check in and come back online. -
Cellular (4G/5G LTE) Deployments:
For cellular-connected units, obtain the public carrier NAT egress IP or corporate APN gateway IP (not the internal cellular modem IP).
IP Address Formatting Guidelines:
-
Must Be Public IPs: Private RFC 1918 local addresses (e.g.,
10.x.x.x,172.16.x.x–172.31.x.x, or192.168.x.x) cannot be routed across the Internet and will not work. -
CIDR Subnet Ranges Preferred: If your organization owns a static block of public IPs (e.g.,
198.51.100.0/24), provide the CIDR range to cover all egress points. - IP Changes: If your ISP or VPN egress IP changes at any point during the extension period, you will need to submit the updated IP to restore access.
Troubleshooting Common IP Access Issues
Issue: My IP was allowlisted but I still do not have access to EV3
Some internet service providers (KUB Fiber, as one example) use pooled or shared IPv4 addresses because they have already transitioned their networks to IPv6. In these environments, your system may prioritize network traffic over IPv6 automatically. Because the legacy EloView 3 portal relies on your allowlisted IPv4 signature, this automatic prioritization can block your access.
Solution 1: Allowlist Your IPv6 Address
If you find that your IPv4 allowlist rule fails to function, determine your IPv6 address using whatismyip.com and submit it to be added to the security perimeter.
Solution 2: Force IPv4 for the EloView Portal Domain (Firefox-based Browsers)
If your public IPv6 address changes dynamically (e.g., daily), allowlisting it may not be a viable long-term workaround. If you use a Firefox-based browser, you can force it to route connections to EloView via IPv4 only, while leaving IPv6 enabled for everything else:
- Open Firefox and type
about:configin the address bar, then press Enter. - Accept any warning prompts to proceed.
- Search for the preference name:
network.dns.ipv4OnlyDomains. - Modify this preference by adding
manage.eloview.comto its value list. This isolates the EloView domain to resolve over IPv4 only.
Solution 3: Temporarily Disable IPv6 System-Wide (Windows)
If other methods are unavailable, you can force your entire operating system to prioritize IPv4 by temporarily disabling IPv6 on your network adapter settings:
- Search for "View network connections" in the Windows search bar and open the Control Panel menu.
- Identify your active network adapter (e.g., Wi-Fi or Ethernet), right-click it, and select Properties.
- Scroll down the list and uncheck Internet Protocol Version 6 (TCP/IPv6).
- Click OK to apply settings and force IPv4 connections.
How to Submit Your IPs to Restore Access
Once you have gathered the public IP addresses for your administrator locations and device sites:
- Contact Elo Technical Support by submitting a request at Elo Technical Support Portal or reach out directly to your designated Elo Solutions Architect / Account Representative.
- Provide your EloView 3 Organization Name / OrgID, your target EloView 4 migration timeline, and the list of public IP addresses/CIDR blocks collected.
- Once Elo Engineering applies the allowlist rules to the security perimeter, your administrators will be able to log in and devices will automatically reconnect and return online.
Please report any broken links by emailing elo.support@zebra.com and include a link to the knowledge article