Skip to main content

MagicINFO login: find your server's sign-in page

There is no central MagicINFO login website: you sign in at the address of your own MagicINFO Server, which looks like http://your-server:7001/MagicInfo or https://your-server:7002/MagicInfo.

If MiCloud hosts your MagicINFO​

MiCloud runs the server for you, so there is no server IP, port or certificate to find.

  • Sign-in address: the MagicINFO address shown on your licence page in your MiCloud account.
  • Two separate accounts. Your MiCloud account (e-mail address) is for licences, displays and invoices. Your MagicINFO account (a user ID, not always an e-mail address) is for content, playlists and schedules. A password for one does not work for the other.
  • Forgot your MagicINFO password? Use the reset option on the MagicINFO sign-in page: enter your user ID, name and e-mail address. You receive a one-time code (not a link) from [email protected]. Paste it, do not type it.
  • Locked out, or the reset e-mail does not arrive? E-mail [email protected] with your user ID and your organisation name. Never send your password; support never asks for it.

Step by step: MiCloud login and password reset help.

The address format​

Every sign-in address has four parts:

<protocol>://<server address>:<port>/MagicInfo
PartWhat to enter
Protocolhttp for the plain web port, https for the encrypted one.
Server addressThe IP address or DNS name of the computer that runs MagicINFO Server, for example 192.0.2.10 or mi.example.com.
PortThe port chosen during installation. The defaults are 7001 for HTTP and 7002 for HTTPS. If the server answers on the standard ports (80 or 443), for example behind a reverse proxy, leave the port out.
Path/MagicInfo. The path is case-sensitive, so type it exactly as shown.

Working examples:

  • http://192.0.2.10:7001/MagicInfo
  • https://mi.example.com:7002/MagicInfo
  • https://mi.example.com/MagicInfo (server or proxy on port 443)
  • http://localhost:7001/MagicInfo, which only works in a browser on the server itself. Colleagues need the server's network address instead.

The sign-in page shows the server version at the bottom, so you can confirm that you reached the right server before you sign in.

Who can sign in​

Installation creates one general administrator account, with the user ID admin. Every organisation has at least one organisation administrator, who creates the other users. People who register through the sign-up link cannot sign in until an administrator approves them. If two-step verification is turned on for the server, each account enrols an authenticator app on its first sign-in.

When the sign-in page won't open​

Typical symptoms: "This site can't be reached", a timeout, a blank page, a certificate warning, a 404 page or a 503 page.

  1. Match the protocol to the port. Use http with 7001 and https with 7002. https://…:7001 or http://…:7002 fails.
  2. Check the path. A 404 page from the server usually means the path is misspelt. It must be /MagicInfo.
  3. Ask the server whether MagicINFO is answering. Open http://your-server:7001/MagicInfo/openapi/auth?cmd=isMagicInfo (or the https / 7002 equivalent). This is the identity check that displays run first. A short version number such as 211070.0 means MagicINFO is answering on that address and port, so the problem is in the browser. If nothing comes back, look at the network, the firewall or the service.
  4. Wait after a restart. A busy server can take five minutes or more after a restart before the sign-in page answers. While it starts, a proxy in front of it returns 503.
  5. Open the port in every firewall on the path. That includes the firewall on the server itself. See MagicINFO ports explained.
  6. Get "This site can't be reached" on an http:// address that works elsewhere? That is the browser's HSTS cache, not the server. MagicINFO sends a header that tells browsers to use HTTPS only, for a whole year and for every name in the same domain. After one HTTPS visit, the browser silently rewrites http:// to https:// before it connects. Fix: use the https address, use the server's IP address (an IP cannot be pinned), or delete the entry for that host in chrome://net-internals/#hsts (Edge: edge://net-internals/#hsts). Displays do not use HSTS and are not affected.
  7. Certificate warning on 7002. The server is using a certificate that your browser does not trust, often a self-signed one. Confirm the address is right before you continue, and plan to install a certificate from a trusted authority.
  8. Find the ports your server really uses. Ports chosen at installation are in C:\MagicInfo Premium\tomcat\conf\server.xml, in the Connector port= lines. A server installed with HTTP only does not answer on 7002 at all; see Change the HTTPS (TLS) certificate.
  9. Check the service. On the server, the Windows service MagicInfo-i Premium Edition Server must be running (services.msc).
  10. The page loads, but signing in fails. See "An unexpected error has occurred" at MagicINFO sign-in.

Use a current browser. Chrome is the tested reference, see Recommended browser.

Forgotten password​

  • Self-service reset. Use the password-reset option on the sign-in page. It asks for your user ID (not your e-mail address), your name and your e-mail address, and all three must match the account. MagicINFO then e-mails a one-time code, not a link. This only works if e-mail (SMTP) is set up for your organisation. See Password-reset e-mail not arriving.
  • Change your own password (when you can still sign in): Setting > My Account > My Information.
  • Administrator reset. An administrator can set a new password for any user in the organisation. See Resetting a password.
  • The only administrator password is lost. It cannot be recovered through the web interface.

How to confirm it worked​

The MagicINFO sign-in form loads and shows a version number at the bottom. After you sign in (with your authenticator code, if asked), the dashboard opens. Bookmark that exact address and give your users the same one, including protocol, port and /MagicInfo.

Checked against MagicINFO Server 21.1070 behaviour, October 2026.

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

Last updated on