Skip to main content

Open MagicINFO without :7001/MagicInfo in the URL

To have https://magicinfo.example.com/ open the sign-in page, you solve two separate problems: Tomcat has to listen on the standard web ports (80 or 443) so the port can be left out, and the server needs a small redirect so that the bare address reaches /MagicInfo/.

Before you start​

  • The address format, default ports and the case-sensitive /MagicInfo path are covered in MagicINFO login and MagicINFO ports explained. This article only adds the change.
  • Back up C:\MagicInfo Premium\tomcat\conf\server.xml and C:\MagicInfo Premium\conf\config.properties first.
  • You need a DNS name for the server (magicinfo.example.com below) and administrator rights on the Windows machine.
  • Screens that are already registered keep the address and port they were given. If you are unsure which ones use 7001 or 7002, do not remove those ports (see step 3 below).

Why the address needs both fixes​

On a 21.1070 install, the installer writes an HTTP connector on 7001 and an HTTPS connector on 7002. Browsers assume 80 and 443, so any other port has to be typed. Separately, MagicINFO's web applications are declared in server.xml as /MagicInfo, /MagicInfoWebAuthorClient, /MagicInfoLayoutEditor, /RMServer and /kpi. There is no application at the root, so http://server/ returns a 404 page, even when the port is right.

Steps: drop the port​

  1. Check that 80 or 443 is free. Another service, IIS for example, may already be using it. Run netstat -ano | findstr :443 in a command prompt and look at the process ID in the last column. If something answers, either stop that service or use the reverse-proxy option below.
  2. Pick the approach.
    • Change the connector. Edit the connector port in server.xml, or use the web port setting in the bundled Config Tool (C:\MagicInfo Premium\bin\MagicConfigEdit.exe, "MagicInfo Server Config Tool"). The tool rewrites conf\config.properties and server.xml. Afterwards, check that every URL it wrote still uses the scheme and name your users and screens use.
    • Add a second connector. Tomcat can run several connectors. Copy the existing <Connector> element and give the copy port 80. For HTTPS, copy the HTTPS connector, give it port 443 and keep the same keystore attributes. Leave 7001/7002 as they are.
  3. Keep the old ports if screens use them. Moving the port means repointing every display (Connect a device to the server). A second connector avoids that, and you can retire 7001/7002 later, once you have seen every screen arrive on the new address.
  4. Open the new port in Windows Firewall. Add an inbound rule for TCP 80 or 443 in Windows Defender Firewall with Advanced Security, and check any network firewall in front of the server.
  5. Update the stored addresses. Several keys in config.properties (for example web_url, server.address, webauthor.web_url_public) hold the server's address, some as full URLs. If any contain :7001 or :7002 and you removed those ports, change them to match your new address. Change the IP address of your MagicINFO server lists the keys.
  6. Restart the MagicInfoPremium service. Expect five to seven minutes before the console answers.

A reverse proxy in front of MagicINFO is the alternative: it listens on 80/443 and forwards to 7001, with no change to Tomcat's ports. Make sure it serves HTTP/1.1 to screens.

Steps: drop /MagicInfo​

  1. Stop the MagicInfoPremium service.
  2. Create the folder C:\MagicInfo Premium\tomcat\webapps\ROOT\. It does not exist by default.
  3. In it, create index.html with this content:
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="refresh" content="0; url=/MagicInfo/">
<title>MagicINFO</title>
</head>
<body>
<a href="/MagicInfo/">Continue to MagicINFO</a>
</body>
</html>
  1. Start the service. The Tomcat host is set to autoDeploy="true", so it would pick the new folder up anyway, but stopping and starting avoids surprises.
warning

Do not copy C:\MagicInfo Premium\server\index.html into ROOT. That file is the web console application itself, not a redirect page.

An upgrade can replace the Tomcat folder and take the ROOT folder with it. After every upgrade, re-check the redirect, the connectors and the stored addresses.

Moving to HTTPS on 443​

MagicINFO sends a Strict-Transport-Security header (one year, including subdomains). After a browser has opened the server over HTTPS, it refuses plain HTTP to that name for a year, and you see "site can't be reached" while command-line tools still work. Decide on HTTPS first, then use it consistently. For the certificate itself see Change the HTTPS (TLS) certificate.

How to confirm it worked​

  1. https://magicinfo.example.com/ lands on the MagicINFO sign-in page.
  2. https://magicinfo.example.com/MagicInfo/openapi/auth?cmd=isMagicInfo returns a short build number such as 211070.0.
  3. If you kept the old connectors, http://magicinfo.example.com:7001/MagicInfo still answers and screens keep polling.
  4. Web Author still opens from the console menu (see Web Author won't open if not).

Checked against MagicINFO Server 21.1070 on Windows, October 2026.

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

Last updated on