Skip to main content

Change the IP address of your MagicINFO server

MagicINFO does not read its own address from Windows. The server's IP address or name is written into C:\MagicInfo Premium\conf\config.properties, and every screen has been told an address too. Changing the IP therefore means three jobs: edit that file, fix whatever else names the old address (firewalls, certificates, a remote database), and get the screens to follow.

Before you start​

  • Plan for a restart. config.properties is read once at start, so every change needs a restart of the MagicInfo-i Premium Edition Server service (service name MagicInfoPremium), and the web console takes several minutes to answer afterwards (5 to 7 minutes on a 21.1070 install).
  • Copy config.properties somewhere safe first, outside the install folder.
  • Decide how screens will find the new address. A DNS name is the easy case; screens that were given a raw IP are the hard case (see below).

Where the address lives​

On a 21.1070 install the server's address appears on 13 lines of config.properties and nowhere else in the install folder. The keys that hold it include:

KeyHolds
web_url, webauthor.web_url_public, mail.templet.url, mail.templet.loginurla full URL, for example https://magicinfo.example.com/MagicInfo
server.address, ws_addressing.header.from, ws_addressing.header.replyToa full URL of the server's web service address, for example https://magicinfo.example.com/MagicInfo/WSRMService
magicinfo.server.ip, download.server.ip, webauthor.ftp.hosta bare name or IP

The list is not exhaustive on every build, which is why step 5 searches the whole file. Some values are full URLs and some are bare names, so replace the host part only; do not overwrite whole lines. Two further keys, wsrm.url and org.quartz.dataSource.databaseDS.URL, are database addresses; they change only if the database moves too.

webauthor.web_url is different: it is the address Web Author's server side uses to call MagicINFO, so it must work from the server itself (on the install we checked it points at localhost). Leave it alone unless it names the old IP.

Steps​

  1. Take the backup of config.properties described above.

  2. Stop the MagicInfoPremium service.

  3. Change the address. The install includes a bundled tool for this, C:\MagicInfo Premium\bin\MagicConfigEdit.exe (window title "MagicInfo Server Config Tool"). From its screen text it edits the server IP, web port, FTP IP and port, streaming port and the database IP and port, and it keeps a copy of the old file in conf\backup\. We have read it but not run it, so treat it as a convenience and the check in step 5 as the authority. If you prefer, edit the keys above in a text editor started as administrator.

  4. If the database runs on another computer, read the next section before you start the service.

  5. Check what was written. The tool shows no sign of handling https, so open config.properties and confirm every URL uses the scheme (http or https) and the name your users and screens really use. Then prove nothing was missed, from PowerShell:

    Select-String -Path "C:\MagicInfo Premium\conf\config.properties" -Pattern "198.51.100.20"

    Replace the example with your old address. No output means no line still names it. Repeat for the old host name if you used one. Also look in C:\MagicInfo Premium\tomcat\conf\server.xml if you ever bound a connector to a specific address.

  6. Start the service and wait the several minutes it needs.

If the database is on another computer​

  • The two JDBC URLs, wsrm.url and org.quartz.dataSource.databaseDS.URL, change only if the database computer changed address. Change them together so both data sources point at the same database.
  • PostgreSQL's pg_hba.conf (in its data folder) must allow the new address of the application server. Add a rule for that one address (192.0.2.10/32 style) and remove the old rule. Never open it to all addresses as a quick fix. Reload or restart PostgreSQL, then start MagicINFO. See Clustering: Separate Database, WAS and Proxy Servers.

Things that still name the old address​

  • Windows Firewall rules, or a network firewall, written for the old IP.
  • A reverse proxy whose upstream is the old address.
  • A remote control server registered by IP under Setting > External Server Management > Remote Server. Edit its IP if it moved (Add a Remote Control Server).
  • A certificate issued for the old IP. A certificate naming a bare IP cannot be reused; get a new one, or switch to a DNS name (Change the HTTPS (TLS) Certificate).

Screens​

Screens keep the address they were given.

  • They use a DNS name: change the record to the new IP and you are done. Lower its TTL a day ahead. Even with a 120-second TTL, Tizen displays in our own moves kept polling the old address for about 6 minutes, and screens that were asleep or off moved only when they woke. A power cycle clears a display's cached address.
  • They use the IP: either repoint each display (Connect a Device to MagicINFO Server), or keep the old IP reachable (an extra address on the adapter, or a forwarding rule) until every screen has moved.
  • If a screen vanishes from both addresses right after the change, look for a firewall on that screen's network that only allows the old server IP.
tip

Put a DNS name on screens from the start. The next address change then costs one record and a few minutes, not a visit per display.

How to confirm it worked​

  1. Open http://192.0.2.10:7001/MagicInfo/openapi/auth?cmd=isMagicInfo (your new address, scheme and port). A short build number such as 211070.0 means MagicINFO is answering.
  2. Sign in on the new URL (MagicINFO login).
  3. Watch the device list and see screens reconnect. Do not retire the old address until you have seen every screen arrive, not after a fixed time.

Checked against MagicINFO Server 21.1070 on Windows, October 2026.

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