Skip to content
FMX EPOS
Download
Help Centre home

Security and network access troubleshooting

FMX EPOS runs over HTTPS on port 5139. The desktop app on the till PC connects to it locally. Any other browser or device has to pass the terminal’s web access settings, the optional list of allowed IP addresses and the normal sign-in rules. Only an administrator can change these settings, and only in the desktop app on the till that the devices connect to.

The page shows one of these messages:

  • “… access is disabled on this till. Open the desktop app and enable it in Local Settings → Security.” The start of the message names the area: Back office web, Till web, Kitchen screen web, Host stand web, App or Remote.
  • “Till Web, Kitchen Screen Web and Host Stand Web access are disabled on this till. Open the desktop app and enable one in Local Settings → Security.” on the PIN page. Any one of the three opens it; tick the one for the device you are setting up.
  • “This device’s IP address is not allowed. Ask the till administrator to add it in Local Settings → Security.”
  • “The IP allowlist on this till cannot be read. Open the desktop app and correct it in Local Settings → Security.”
  • “This computer is a kitchen-only terminal and takes no phone orders. Connect the phone to a till.”
  • “This computer is a host-stand-only terminal: it takes no orders. Use a till.” It also appears in the desktop app on that PC if someone opens the till there.
  • “Open the desktop app on the till computer to access these settings.”, because first-run setup can only be done in the desktop app.

Illustration, not a screenshot. The real screen can differ with the theme or version.

On the host terminal, open Back Office → Local Settings → Security in the FMX EPOS desktop app. In a browser the page is read-only and says “Open the desktop app on this computer to change these settings.”

Illustration, not a screenshot. The real screen can differ with the theme or version.

  1. Under Remote Access, tick the box for the area being blocked:
    • Back Office Web Pages for the Back Office in a browser.
    • Till Web — PC, Mobile & Customer Display for the till, browser mobile ordering and /display.
    • Kitchen Screen Web for /kitchen and its sign-in.
    • Host Stand Web — PCs & Tablets for /host and its sign-in.
    • Mobile App for the Android app.
  2. Under IP Allow List, if Only Allow Listed IP Addresses is ticked, add the device’s exact IPv4 or IPv6 address under Allowed IP Addresses. Put each address on a line of its own.
  3. Select Save Security Settings. The page says “Security settings saved.”
  4. Reload the page on the other device.

The list does not accept host names, ports, ranges or subnets. A wrong entry stops the save with “Invalid IP address: … Enter one IPv4 or IPv6 address per line, without a port or subnet.” Only Allow Listed IP Addresses cannot be saved with an empty list (“Enter at least one IP address before you turn on Only Allow Listed IP Addresses.”). Enter the address of the device that connects directly to the till.

If the saved list cannot be read, the page shows “The saved list cannot be read:” with the reason. While Only Allow Listed IP Addresses is ticked, every remote device is then refused until you correct it.

Turning on web access does not bypass sign-in, roles, the licence or business permissions. Adding a new till with a pairing code works whatever these settings say.

  1. On the host, check that FMX EPOS is running and that the desktop app can open the till.
  2. On the other device, go to https://<terminal-address>:5139.
  3. Check that both devices are on the right network and that the host’s address has not changed.
  4. On the host, open Back Office → Diagnostics and read the Network card. If it shows Public Network, Windows blocks other devices on that network: in Windows network settings, open the shop network’s properties and set it to Private network.
  5. Allow incoming TCP 5139 (and UDP 5140, which other tills use to find this one) from the shop network through the host’s firewall. The FMX EPOS installer adds these rules on every install, upgrade and repair, for private and domain networks and for devices on the same local network only. If they are missing, run the installer again and choose Repair. A device on another part of the network may need the rule added in Windows Defender Firewall by whoever maintains the PC.
  6. Check that the Remote Access setting and the allowed IP addresses let the device in.

Keep the host’s address stable with a fixed address or a DHCP reservation; the Network card shows DHCP Address while it can change. A Kitchen-Only Terminal deliberately refuses mobile ordering and mobile app traffic, even when the matching setting is on. A Host-Stand-Only Terminal also refuses the till itself.

Each installation has its own local certificate authority. The desktop app already trusts its own installation’s certificate. Any other browser or device has to be told to trust that installation’s root certificate.

  1. Open the terminal’s HTTPS Certificate page at https://<terminal-address>:5139/certificates. At least one Remote Access setting must be on, and the allowed IP addresses still apply.
  2. Check that you opened the page from your own shop’s till address. The page shows the certificate name, serial number and validity dates.
  3. Select Download Certificate. Downloading does not install or trust it.
  4. Open iPhone / iPad, Android or Windows on the page and follow its steps to install and trust it. On another Windows PC, such as a kitchen screen or a Back Office browser: open the downloaded FMX-EPOS-Root-CA.cer, select Install Certificate, choose Current User, then Place all certificates in the following store, Browse and Trusted Root Certification Authorities. Select Next, Finish, and Yes on the security warning.
  5. Close every browser window, then go to the same terminal address again.

Illustration, not a screenshot. The real screen can differ with the theme or version.

Hand out only the certificate offered on that page. On the till PC itself, use the desktop app instead, as described below.

The FMX EPOS installer trusts the till’s certificate for every Windows user on the PC, so browsers on the till PC normally open FMX EPOS with no warning. If the installer could not do it, its last page says so, and the desktop app asks when it starts.

When the certificate is not trusted yet, for example on a copy of FMX EPOS that was not installed with the installer, the desktop app asks Windows to trust it for the signed-in Windows user each time it starts. Windows shows one Security Warning about a certificate from the shop’s FMX EPOS root. Select Yes.

Illustration, not a screenshot. The real screen can differ with the theme or version.

If you select No, FMX EPOS carries on without another message, and browsers on this PC may show a certificate warning. To be asked again at another time, open Back Office → Local Settings → This Terminal in the desktop app and select Trust Certificate in the Windows section. It then says “Windows trusts this till’s certificate.” or “Windows does not trust this till’s certificate: the Security Warning was answered No, or did not complete.” If Windows cannot add the certificate at all, FMX EPOS shows Certificate Setup Failed. The till keeps working in every case.

If the warning says the address does not match, check that you are using the terminal’s current IP address or its Windows computer name. The certificate covers those, not other names for the PC. FMX EPOS issues a new server certificate by itself when the PC’s network address changes, so no restart is needed. If the warning remains, look in Recent Errors in Back Office → Diagnostics for “The HTTPS server certificate could not be reissued for this PC’s new network address.”, then restart FMX EPOS.

  • The device may have been given a new address by DHCP that is not in Allowed IP Addresses.
  • An administrator may have turned a Remote Access setting off. Changes take effect straight away.
  • The terminal’s own network address may have changed.
  • A user may have been deactivated, moved to another role or had their PIN or password changed.
  • Auto lock may have ended the session.

Check Diagnostics and Local Settings → Security on the host. User changes are recorded in Reports → Audit Log; changes to Local Settings → Security are not. For Yealink callbacks, see Caller ID and dialling, because that listener has its own Allowed Callback IPs list and port.