Skip to main content

MagicINFO ports explained: 7001, 7002, 443 and the screen

A Samsung display needs to reach just one port on the MagicINFO server: the web port entered in the display's server settings. That is 7001 (HTTP) or 7002 (HTTPS) by default, or 443 when the server, or a proxy in front of it, serves HTTPS there. The display opens every connection itself, so nothing needs to connect into the screen.

What each port is for​

PortWhat it isWho needs to reach it
7001Default HTTP port of the MagicINFO web application: the browser interface, the REST API and all display traffic (registration, polling, status, downloads over HTTP)Displays and users, if you run without encryption
7002Default HTTPS port for the same applicationDisplays and users, encrypted
443 / 80Standard web ports, used when the server is configured to answer there, or when a reverse proxy or load balancer sits in front of itDisplays and users, instead of 7002 / 7001
21, 990, passive rangeThe server's built-in FTP service, which some setups use to hand content to displaysOnly if your server delivers content over FTP
5500, 5800, 5901, 7000Remote control (VNC) and video streaming featuresOnly if you use those features
5432Default PostgreSQL database portOnly the MagicINFO server itself, never displays or the internet

The full list is in MagicINFO Server ports.

Displays poll the server every five seconds for new commands, so normal operation needs no inbound rule towards the displays.

The three settings on the display must agree​

In the display's server network settings, the server address, the TLS switch and the port belong together. (Older display menus call the TLS switch SSL.)

TLS on the displayPort to enter
On7002, or 443 if the server or proxy serves HTTPS there
Off7001, or 80

A mismatch such as TLS on with port 80 fails silently: the display shows no clear error, and nothing arrives on the server. The same happens when the display points at a port where nothing listens. It simply never appears under Unapproved. Address typos, a wrong TLS/port pair and firewalls are the most common causes we see in support cases.

Common failures​

  • "Connection refused" on 7002. Nothing on the server is listening on that port. Either the HTTPS connector is not enabled, or the server was installed on different ports. Test it as described below.
  • Firewall. Allow the port inbound on the server's own firewall, and outbound from the display network.
  • TLS-inspecting proxies. Displays do not trust a certificate that a proxy has re-signed. Exempt the MagicINFO server from inspection.
  • Certificate check on the display. Recent firmware can verify the server's certificate. When that check is on, a self-signed or otherwise untrusted certificate makes the connection fail without a clear message on screen, so use a certificate from a public authority.
  • Display clock far off. TLS fails because the certificate looks expired or not yet valid. See Setting the device time and date.
  • Reverse proxy in front of MagicINFO. Samsung displays need HTTP/1.1, so do not offer them HTTP/2. Some older models also send the host name www.rmdevice.samsung.com instead of your server name. If your proxy routes by host name, make MagicINFO its default destination so those displays still arrive.

Test a port before blaming the screen​

  1. On a computer on the display's network, open http://your-server:7001/MagicInfo/openapi/auth?cmd=isMagicInfo or, for HTTPS, https://your-server:7002/MagicInfo/openapi/auth?cmd=isMagicInfo. This is the first request a display makes. A short version number such as 211070.0 means MagicINFO answers on that address and port.
  2. If it answers on the server itself but not from the display network, the firewall or routing between them is the problem.
  3. If it answers from the display network, enter the same address, TLS setting and port on the display, save, and wait a minute or two.

How to confirm it worked​

The display appears under Unapproved (or, if it was approved before, as connected in the device list), and its requests show up in the server's access log every few seconds.

Checked against MagicINFO Server 21.1070 behaviour, October 2026.

Prefer not to run the server yourself? MiCloud hosts MagicINFO for you.