Diagnostics and support information
Open Back Office → Diagnostics on the affected terminal. Only administrators can open it. The page is read-only and refreshes itself every 5 seconds; the line under the title shows when it was last updated. Select Refresh to update it straight away.
Updated 14:05:32 · refreshes every 5 s
Database
- Mode
- Remote
- Pending Writes
- 0
Continuity
- Queueing Writes
- No
Integration Host
- Host Terminal
- Front Till
Clover Bridge
- Bridge Process
- Running
Printing
- Failed Jobs
- 0
Network
- Addresses
- 192.168.1.20 (DHCP)
Illustration, not a screenshot. The real screen can differ with the theme or version.
Read the cards
Section titled “Read the cards”- Terminal shows this terminal’s name, Terminal ID, computer name and FMX EPOS version.
- Database shows which database is in use (without any passwords), whether it is Available, Unavailable or Paused for maintenance, when it was last checked, the Pending Writes and Review Writes counts and the latest connection message.
- Continuity shows whether this terminal is Synchronised, has Queued or Review writes, or is in Emergency Mode, whether it is the designated emergency terminal and, under Attention, anything holding up the emergency upload. On a Remote store with no Emergency Terminal it warns “No emergency terminal is chosen, so during a database outage no terminal can sign staff in, open tables or print kitchen tickets. Choose one in Back Office → Database.”
- Integration Host shows which terminal fetches online orders (This Terminal, Another Terminal or No Host) and, for each platform connection, its last poll, failures in a row and last error.
- Clover Bridge shows whether Clover is turned on, whether the bridge is running and the Flex’s state. Manual Card Mode means Clover is not turned on for this terminal.
- Telephony shows the caller ID source chosen, the state of its device and the Yealink listener port, and under Last Refused Callback the address and time of the latest Yealink event refused because its address is not allowed.
- Printing shows how many print jobs are pending, failed or unknown across the shop, this terminal’s receipt printer and whether its print worker is running.
- Automatic Backup shows the shop’s backup schedule and folder, the last backup and the terminal that made it, and any failure, warning, missed or interrupted backup.
- Network shows this PC’s addresses and the Windows networks it is on. Public Network means Windows treats the shop network as public, so other tills and phones cannot reach this PC; set that network to Private network in Windows network settings. DHCP Address means the PC’s address may change; reserve it in the router or set a fixed address in Windows.
- Terminals lists every terminal registered on the database in use, with its version, last contact, pending writes and maintenance state.
A green card confirms only what the software can see right now. It cannot tell whether the paper is loaded properly, the cash drawer cable works, customers can reach an online platform or a card will be approved.
Recent Errors
Section titled “Recent Errors”Recent Errors shows up to 50 recorded warnings and errors from today and yesterday, newest first, for example the database dropping out, the HTTPS certificate not being reissued after a network address change, a Clover failure, an unfinished card request, a clock correction, a failed automatic backup or a start-up being stopped. “No errors logged.” means there are none.
Each entry starts with the date and time in UTC (Coordinated Universal Time), followed by a technical reference and then the message. During British Summer Time, UTC is one hour behind the till’s clock, so an error at 14:05 on the till shows as 13:05.
Recent Errors2
Newest first, today and yesterday
- 2026-10-21T12:58:02+00:00 …Remote database unavailable: Remote database connection failed. Check the server, credentials and network. New records remain local until it reconnects.
- 2026-10-21T02:00:41+00:00 …The automatic backup into D:\Backups failed.
Illustration, not a screenshot. The real screen can differ with the theme or version.
- Match the time of the error to the reported incident, allowing for UTC.
- Read the first relevant message and the matching card above.
- Fix the cause it names, then select Refresh.
- If the error is still listed but the status is now healthy, note both the time of the error and the current status for support.
Fixing a fault does not remove its earlier entries from the list.
Start-up and runtime messages
Section titled “Start-up and runtime messages”| Message | What it means | What to do |
|---|---|---|
| “The Windows clock is … behind/ahead of … and FMX EPOS could not correct it.” then “FMX EPOS will now close.” | The clock is 10 seconds or more out and FMX EPOS could not set it, because it was not started with Windows administrator rights. | Right-click FMX EPOS and choose Run as administrator, or correct the clock in Windows Settings → Time & language, then start FMX EPOS again. See Windows clock check. |
| Till banner “This PC’s clock is … out and could not be corrected. Close FMX EPOS and start it as a Windows administrator.” | The Windows clock is 10 seconds or more out and FMX EPOS could not correct it. The till carries on trading. | Start FMX EPOS as a Windows administrator, or correct the Windows clock. The banner clears within about 10 minutes of the clock being right. |
| “Restarting EPOS…” on every FMX EPOS window | FMX EPOS or its browser engine stopped unexpectedly. The desktop app restarts it and takes each window back to its page. | Wait, and do not close the app. Then check any payment or print that was in progress before you repeat it. |
| “The local FMX EPOS service keeps stopping … restarts did not keep it running” | Six restarts did not help, so the desktop app has stopped trying and closes after OK. The message ends with the error log folder. | Check the database connection, note the message and contact support with the checklist below. |
| “FMX EPOS could not start” with “Another program is using port 5139” | Another program is using the port FMX EPOS needs. The page names the program. | Select Close It and Start if the program can be closed, then confirm (anything it has not saved is lost). Or close it yourself and select Try Again. Exit closes FMX EPOS. |
| The port page says “It is another copy of FMX EPOS …” | A second installation of FMX EPOS is already running on this PC. Only one copy can run at a time. | Close the other copy, then select Try Again. |
| The port page says “Windows is using it for a web service, such as IIS.” | A Windows service holds the port, so Close It and Start is not offered. | Ask whoever maintains the PC to stop that service or move it off port 5139, then select Try Again. |
| “The local FMX EPOS service did not answer within 10 minutes and was stopped.” | Start-up took too long, often because the database could not be reached. | Check the database server and network, then start FMX EPOS again. If it happens again, contact support. |
| “FMX EPOS … cannot start the local service … Run FMX EPOS Setup and choose Repair, or copy the complete release folder again, then start FMX EPOS.” | An update was copied only in part. | Run FMX EPOS Setup and choose Repair, or ask support. |
| “Microsoft Edge WebView2 Runtime is required.” | The browser engine FMX EPOS uses is missing. The installer for it comes with FMX EPOS. | Select Yes to install it, then start FMX EPOS again. If the message says the offline installer is missing, run the FMX EPOS installer again. |
| “The local HTTPS root certificate is missing”, “… is incomplete”, “… is invalid or expired” or “The HTTPS certificate … is damaged or cannot be opened.” | This installation’s own security certificate files have been removed or changed. | Do not replace or delete any files. Contact support. |
| “FMX EPOS could not start” with another reason | Start-up failed. The message gives the cause and, where relevant, the error log folder. | If the cause is clear, fix it; otherwise contact support. |
| “FMX EPOS is already running for another Windows user on this PC.” | FMX EPOS runs only once per PC, and another Windows user has it open. | Close FMX EPOS in that user’s session, or use that session. |
| Terminal Identity In Use | Two PCs are running the same copied installation. | See Terminal identity conflict. |
| Till banner New sales are paused, with a reason | The licence does not allow new sales on this till, for example No Seat, Expired, Clock Behind or Virtual Machine on the Licence page. Orders already open can still be finished. | Deal with the reason given, then see Licence status recovery. |
| Sign-in warning “Update this till to EPOS … or later for cloud sync.” or till banner Cloud sync stopped | FMX EPOS Cloud needs a newer till version. Local trading carries on. | Arrange the update with support. See Till and Cloud version compatibility and Cloud sync and store status. |
| Till banner Database offline, “Sales are kept on this till.”, then Syncing … local writes | The shared database cannot be reached, then the till is sending the work it kept. | Leave the till running. See The database is unavailable. |
| Till banner No Integration Host is running | No terminal is fetching online orders. | See Online platforms and Integration Host. |
| Till banner “… polling failing. Check Online Platforms” | A platform connection has failed three checks in a row. | See A connection is not fetching orders. |
| Till banner “Printer …: N jobs need attention” | Print jobs for this terminal need someone to deal with them. | See The till shows a printer banner. |
| Till banner Automatic backup failed, with a reason | The scheduled backup failed. It is tried again at the next scheduled time. | Check that the backup folder exists and can be written to, then check the Automatic Backup card. See Manage database storage and maintenance. |
| Till banner Automatic backup missed or Automatic backup interrupted, “The backup due … was not made.” or “… was interrupted.” | No terminal made the scheduled backup, usually because the Integration Host was switched off or busy at that time, or the backup stopped part-way. | Keep the Integration Host running at the backup time. Check the Automatic Backup card. |
| Till banner Automatic backup warning | The backup was made, but something else went wrong, such as older backups not being removed. | Read the reason and check the backup folder. |
The backup banners appear only on the Integration Host’s till.
Another program is using port 5139
Example Web Server · process 4120
FMX EPOS needs port 5139 to run. Close that program, or ask whoever maintains this PC to move it to another port, then select Try Again.
Illustration, not a screenshot. The real screen can differ with the theme or version.
The till’s warning banners appear in the bottom-right corner. Red banners are for problems that stop trading or affect money: the licence, the card terminal, online orders that need attention, print failures, failing platforms and no Integration Host. Amber banners are notices about the database connection, the clock, backups and cloud sync. A platform with polling off, or with deliveries or collections closed or paused, gets no banner: the Platforms button in the left rail shows an amber number instead, and the Platforms workspace shows which platform and why. The banners are hidden while a table dialog is open. On the payment and refund screens they are folded into one warning triangle with a count; tap the triangle to open them there. They are also folded into the triangle when you open a feature workspace (Tables, Orders, Customers, Cash & Card, Platforms or Insights), so they do not cover it; tap the triangle to open them, and a new warning opens them by itself. Back on the till, including a table’s order, they show as before. The minimise button (a short line) on any banner folds all of them into the triangle, and tapping the triangle shows them again. They also open again by themselves when a new warning arrives, except on the payment and refund screens. The triangle is red when any warning in it is red, otherwise amber. If it is in the way, drag it: it moves to the nearest edge of the screen and stays there until the till screen reloads. Minimising only hides the banners and does not fix or acknowledge anything.
Open Print Jobs
The backup folder is not available.
Online orders are not polled and scheduled courses are not released. Check the host in Online Platforms.
Illustration, not a screenshot. The real screen can differ with the theme or version.
FMX EPOS does not start when Windows starts
Section titled “FMX EPOS does not start when Windows starts”FMX EPOS normally starts by itself when anyone signs in to Windows on this PC.
- In the desktop app, open Back Office → Local Settings → This Terminal and find the Windows section.
- Check that Start at Windows sign-in shows Enabled. If not, select Enable.
- Windows asks “Start FMX EPOS automatically when anyone signs in to Windows?”. Select Yes.
- If the till says “Starting FMX EPOS at sign-in can only be changed with Windows administrator rights.”, close FMX EPOS, right-click it, choose Run as administrator and try again.
Windows
- Start at Windows sign-inDisabledEnable
- HTTPS certificateTrust Certificate
Starting FMX EPOS at sign-in can only be changed with Windows administrator rights. Right-click FMX EPOS, choose Run as administrator, then try again.
Illustration, not a screenshot. The real screen can differ with the theme or version.
When FMX EPOS is started this way from a Windows administrator account, it can also correct the Windows clock at start-up without asking.
Copy a support summary
Section titled “Copy a support summary”Select Copy Summary to copy the same status as plain text. The page says “Summary copied.” Before you share it:
- Paste it into a text editor on the PC.
- Look through the terminal and machine details, folder and database names, platform names and recent error text.
- Remove any customer details or other business information that appears in an error message.
- Send only the part support needs.
The Diagnostics page does not show database passwords, platform passwords or saved sign-in tokens. Check the copied text all the same, because folder paths, server names and recent error messages can be sensitive for your shop.
Contact support
Section titled “Contact support”Include these with every support request:
- The terminal name, as shown on the Terminal card or in Local Settings.
- The FMX EPOS version from the Terminal card.
- The date and time the problem happened.
- A screenshot or photo of the exact message.
- The Copy Summary text, checked as described above.
If FMX EPOS will not start and you cannot open Diagnostics, send the start-up message instead. If the message names an error log folder, also send the file from that folder for the day of the problem; the files are named by date in UTC and kept for 30 days. Do not delete or move the installation folder.
When Diagnostics cannot read the database
Section titled “When Diagnostics cannot read the database”While the remote database is unavailable, anything Diagnostics reads from it cannot refresh: the print job counts stay at 0, the Automatic Backup schedule shows Unknown and the Terminals card says “Terminals are read once the database answers.”. Follow Database and continuity troubleshooting, and do not take a missing or empty section to mean the database is empty.
Back Office needs the database to sign in, so open Diagnostics during an outage only on a terminal where Back Office is already open.