In this article, we’ll talk about the device network requirements for Mvix CMS v3. This is mainly helpful for IT teams and network administrators who are deploying their enterprise digital signage.
The Mvix device system connects to the Mvix CMS content management server over the Internet with a regular HTTP/HTTPS protocol establishes this connection. This is the same protocol that a PC or laptop uses to connect with any website.
Which ports do you need to open to be able to connect to the Mvix CMS?
Highly-secured corporate networks may restrict web connections and file transfer protocols due to security concerns via blockers such as firewalls, managed switches, etc. They will need to have the following ports/IP addresses open for uninhibited communications with the Mvix CMS solution. We recommend keeping these devices on networks/subnets with less security-intensive needs when possible. It will reduce additional points of contact that will need to be managed.
Note: Mvix players support up to wireless N and we recommend a 2.4 GHz connection. This is for a more stable connection.
IP Addresses
Traffic will need to be allowed to https://cms.mvix.com, which is our CMS web application subdomain.
Additionally, traffic will need to be allowed to https://app.cms.mvix.com/, which is our application download page. Therefore, this domain’s IP address does not remain static.
Outbound
The following outbound ports must be opened in order to allow access to https://cms.mvix.com:
- HTTP – TCP Port 80
- HTTP – TCP Port 8080
- HTTPS – -TCP Port 443
- WebSockets – TCP Port 5001
You will also need to make the following available for outbound connections to our remote troubleshooting tool:
Port 80, 443, or 6568 connects to the remote troubleshooting tool. For standard listening ports, the direct line connection is 7070 (TCP).
The connection should work on all players connected to the Internet. Some networks with additional security may require additional steps to receive support. Further, you may find more information about the network requirements to receive remote support by clicking here.
- Note: TCP port 6568 is not required for BrightSign, LG, and Android hardware, only for Mvix and Flex for MiniPC BYOD hardware.
Please allow access to *.ntp.ubuntu.com to ensure your time is correct. You will also need to make the following outbound port available to ensure your device’s time is correct:
- UDP Port 123
To ensure proper and successful security updates, please allow outbound access to http://archive.ubuntu.com. This is done over:
- TCP Port 80 (HTTP)
The network should allow uninhibited traffic over ports 80 and 443. If the requirements have been met, the devices on your network should communicate with our server.
Note: As of March 2019, we are requiring TCP Port 5001 (WebSockets) to be open in your network. This is to enable enhanced features and faster response times for your devices.
Problems, Questions, Corrections: If you have any further questions, problems, or corrections you would like to see made, please open a support ticket.