Note: The local device ports and Web UI paths in this article refer to the Supervisor Web UI introduced in V13.0.0. If your device shows the earlier Web UI without the Platform sidebar, some Device ports, like 8443 for HTTPS, do not apply. The cloud endpoints, DNS, firewall, and DHCP/static guidance apply to all devices.
To ensure the reliable operation of Videon devices, including with the use of LiveEdge® Cloud Control, your network must allow access to specific endpoints, ports, and services. This guide lists the required endpoints and ports, and recommends firewall, DNS, and IP addressing settings that help keep the device connected.
Required Endpoints & Ports
The following endpoints must be accessible for Videon devices to function correctly. The first group is local traffic between your computer and the device on the same network; the second group is outbound traffic from the device to the internet.
Local access (client → device)
| Service | Endpoint / Domain | Port(s) | Protocol | Purpose / Notes |
| Device Web UI | LAN IP of the device (for example 192.168.x.x or a DHCP reservation). No public DNS; access is device-local on the subnet. |
8080 8443* |
TCP/HTTP (Client → device) |
Primary web interface for the device, including the Platform pages and the embedded Encoder page. Browse to http://<device-ip>:8080. *Port 8443 is used only when HTTPS is turned on for the Web UI. The HTTP port can be changed, and the standard web ports (80/443) can be selected instead, under Settings > Supervisor; if you change these, allow the ports you chose. |
| Encoder web UI | Same as above | 80 | TCP/HTTP (Client → device) | Web server for the Encoder (streaming) interface. The Encoder page inside the Web UI loads from this port, so your computer needs to reach both port 8080 and port 80. It can also be opened directly at http://<device-ip>/. |
| Local REST API | Same as above | 2020, 8089, 8091, 8092 | TCP/HTTP (Client → device) | Ports 2020, 8089, 8091, and 8092 are the local REST API endpoints used by the Encoder web UI and related on-device functions (subset of API surface). |
| Device discovery (mDNS) | Multicast on the local subnet (224.0.0.251), service _videon-device._tcp | 5353 | UDP (local subnet only) | Lets applications on your network find the device automatically. Local only; no firewall change is needed unless multicast is filtered between the device and your computer. Can be turned off under Settings > Supervisor > Enable network discovery. |
Screenshot 1: Settings > Supervisor. Web access shows the HTTP port (8080), the standard web ports option, and HTTPS; Discovery status shows the device's mDNS service.
Outbound access (device → internet)
| Service | Endpoint / Domain | Port(s) | Protocol | Purpose / Notes |
| MQTT (AWS IoT Core) | a3di2u0bk63rob-ats.iot.us-west-2.amazonaws.com | 443, 8443*, 8883* | MQTT (TLS) |
Used for device communication with AWS IoT Core. Do not restrict by IP. *These ports are used as fallbacks depending on network configuration. Port 443 is preferred, but 8443 and 8883 may be used in restrictive environments. |
| LiveEdge Cloud Control | videoncloud.com | 443 | HTTPS | Enables remote management and monitoring of devices. Do not restrict by IP. |
| LiveEdge Cloud Control API | api.videoncloud.com | 443 | HTTPS | Enables remote API commands of devices. Do not restrict by IP. |
| Download Logs from Device via LiveEdge Cloud | api-devices-devicelogsbucketce8d3ab0-lxnnsjk85q9eg.s3.amazonaws.com | 443 | HTTPS | Ensures Support Files can be uploaded to AWS S3. Do not restrict by IP. |
| Device Time Sync (NTP) |
pool.ntp.org or the time servers you enter under Settings > Device > Time servers |
123 | UDP | Ensures accurate device timekeeping. Time synchronization is required for secure connections to LiveEdge Cloud Control. |
| Software Updates |
LiveEdge® Max: releases.videonlabs.com releases-videonlabs.s3.us-east-1.amazonaws.com 818162850908.dkr.ecr.us-west-2.amazonaws.com prod-us-west-2-starport-layer-bucket.s3.us-west-2.amazonaws.com [OS PACKAGE HOST TO CONFIRM] LiveEdge® Node: releases.videon-central.com |
443 | HTTPS | Required for checking for and downloading software updates. On Max-series devices, updates are delivered as a release manifest, an operating system package, and application container images pulled from Amazon ECR, so all of the listed hosts must be reachable. Do not restrict by IP. |
| Docker Containers (DNS) |
Google's DNS servers: 8.8.8.8 & 8.8.4.4 |
53 | DNS (UDP/TCP) |
Recommended fallback DNS servers for Docker image pulls and container-level name resolution. Videon's own applications and containers created on the device use the DNS servers configured for the device. For Node devices, before software version V12.0.0, Docker could only use Google's DNS servers for downloading images and resolving hostnames inside containers. This requirement remained in place until the DNS configuration parameter was exposed in the Docker container creation UI. |
DNS Recommendations
Reliable DNS resolution is critical for endpoint access. We recommend using one of the following public DNS providers:
- Google DNS: 8.8.8.8, 8.8.4.4
- Cloudflare DNS: 1.1.1.1
These providers are known for high availability and fast resolution times.
The DNS servers the device is using are shown under Settings > Network, along with whether they are reachable. To confirm that a name resolves from the device itself, expand DNS cache on the same page and select DNS lookup.
Firewall Best Practices
To ensure uninterrupted device operation, follow these firewall configuration guidelines:
Allow Outbound Traffic
- Allow outbound connections on the ports listed above.
- Ensure UDP port 123 is open for NTP time synchronization.
Do Not Restrict AWS Endpoints by IP
Warning: Important: AWS services use dynamic IP ranges that change frequently and vary by region. Restricting access by IP address will likely cause connectivity issues. Instead, allow access based on domain names.
Monitor for Failures
If software updates or Cloud Control features fail, it may indicate:
- Blocked access to required domains
- DNS resolution issues
- Firewall restrictions on outbound traffic
The Overview page of the Web UI reports network health and will indicate when DNS is unreachable, when the device time is not synchronized, or when the device only has a link-local address.
Warning: If endpoints like AWS S3 are blocked, TCP-based services (such as Support File uploads) will continue retrying. This can lead to network congestion and buffer growth, especially in constrained environments. Ensure these domains are not silently dropped or filtered.
DHCP/Static Best Practices
When to Use a Static IP
If your Videon device may be powered on before the network's DHCP server is fully online, or if the DHCP server may be unavailable at times, we strongly recommend assigning the device a static IP address.
This ensures:
- The device does not fall back to a link-local IP (for example 169.254.x.x)
- Network services like Cloud Control, software updates, and Support File uploads remain functional
- You avoid unpredictable behavior during startup or reconnection
Setting a Static IP on the Device
IP addressing is configured per network interface in the device's Web UI.
- Browse to the device's Web UI at http://<device-ip>:8080 and sign in if prompted.
- In the left sidebar, expand Platform and select Settings, then open the Network tab.
- Under Interfaces, select the interface you are using (for example eth0).
- Under Address settings, set IPv4 method to Manual (static), enter the address, gateway, and DNS servers for your network, and select Apply. If you are unsure what to enter, check with your network administrator.
Screenshot 2: Settings > Network with the eth0 interface selected. Address settings is where IPv4 method is switched between Automatic (DHCP) and Manual (static).
We recommend recording the current addressing before you change it so that you can reconnect to the device at its new address. If the device is adopted in LiveEdge® Cloud Control, the same setting is available remotely; see LiveEdge® Cloud Control: Setting Up a Static IP. If the network has no DHCP server and you cannot reach the device, see Direct connect to Videon products.
Special Note for 2Go Kit Users
If you are using a cellular-bonded 2Go kit, this recommendation is especially important.
These kits often operate in mobile or temporary network environments, where:
- DHCP servers may not be present or may take time to initialize
- Devices may boot before the network is fully established
In these cases, assigning a static IP address to your Videon device helps ensure reliable connectivity and prevents issues caused by fallback IP behavior.
Best Practice Summary
- Use DHCP in stable, always-on network environments
- Use a static IP when:
- The device may boot before the network is ready
- The network lacks a reliable DHCP server
- You are deploying in mobile or ad-hoc setups (for example, 2Go kits)
Additional Notes
- Videon devices rely on AWS IoT Core for secure communication. Ensure your network policies support TLS over port 443.
- Time synchronization is essential for secure MQTT connections. If NTP is blocked, devices may fail to authenticate.
- If your organization uses a proxy or deep packet inspection, ensure that TLS traffic to the listed domains is not intercepted or altered.
- HTTPS for the device's Web UI is optional. If you turn it on with an automatic (Let's Encrypt) certificate, the device must also be able to reach Let's Encrypt to obtain and renew the certificate.
- Access to the device's Web UI, Encoder UI, and REST API is intended for your local network. If remote access is required, we recommend a VPN rather than forwarding these ports to the internet; see Network Recommendations & Troubleshooting Tips.
Related articles
- Setting up a static IP
- LiveEdge Cloud Control: Setting Up a Static IP
- Direct connect to Videon products
- Network Recommendations & Troubleshooting Tips
- LiveEdge Cloud Control Networking Information
- Known Behaviors of NTP Service on Node
- Update Videon Device Software
- Docker Container Management
- Submitting a Technical Support Request