meshO Manager

Appearance

Download, install and update ​

Audience: Anyone setting up Manager on a computer for the first time, or keeping an existing install up to date.

How to obtain meshO Manager, install it on Windows, Mac or Linux, run it from the system tray or menu bar, open it on other devices, and keep it updated.

Install on one machine only ​

Before you start, the most important thing to understand:

You only install Manager on one computer per event. Every other device — registration laptops, the download desk, leaderboard TVs, commentators' tablets, spectators' phones — connects to that one machine through a web browser. Nothing to install on them. No accounts to create. They just open a URL (and type the access PIN, if you've set one).

Pick whichever computer you'd like to act as the server — your registration PC, your download PC, or a dedicated machine. As long as the other devices can reach it on the local network, it works. See What is meshO Manager? for the architecture in more detail.

One exception: meshO Prime must plug into the server ​

There's a single piece of hardware that has to be physically connected to the server computer rather than any of the browser-only devices: the meshO Prime field unit that receives radio punches from the controls in the forest.

Prime connects to the server over USB (serial) and the server process is what reads from it. Browsers can't talk to Prime — they only display what the server has already received.

So when you pick which computer to install Manager on, make sure it has a free USB port for the Prime field unit.

Everything else — SportIdent download units, leaderboard TVs, registration laptops — can be on any device because those run through the browser. See Connecting meshO Prime and radios for the full setup.

System requirements ​

  • Windows 10 or 11 (64-bit), or
  • macOS 12 (Monterey) or later — both Apple Silicon (M1/M2/M3/M4) and Intel are supported, or
  • Linux (64-bit, x86_64) — distributed as an AppImage that runs on most modern distributions.
  • A local network the other event devices can reach (Wi-Fi or wired). The server doesn't need an internet connection during the event — it's only required for downloading updates.
  • On every device, a modern web browser. Any computer that reads cards or SportIdent stations needs Chrome, Edge (89 or later) or Firefox (151 or later), because those use the browser's Web Serial support; Safari and phone or tablet browsers can't. (Cards read by a radio download station at the finish need no browser at all — see Cards read over the radio network.)

Download ​

Pick the file that matches your computer. These links always download the latest version:

ComputerDownload
Windows PCDownload for Windows (.exe installer)
Mac with Apple Silicon (M1/M2/M3/M4)Download for Apple Silicon Mac (.dmg)
Intel-based MacDownload for Intel Mac (.dmg)
Linux PC (64-bit)Download for Linux (.AppImage)

Not sure which Mac you have? Click the Apple menu → About This Mac. If the Chip line says "Apple M1" / "M2" / "M3" / "M4", choose the Apple Silicon download. If it says "Intel", choose the Intel download.

The downloaded file is named meshOManager-latest-… rather than carrying a version number — that's expected for these always-current links. The actual version is baked into the app; check it any time via Tray / menu bar icon → About.

Install on Windows ​

  1. Run the installer you downloaded (meshOManager-latest-win-x64-setup.exe).
  2. Work around the browser and SmartScreen warnings — see Allowing the install on Windows below. Manager is currently distributed without a Microsoft-recognised code-signing certificate, so Windows will warn you about it the first time you install or run it.
  3. The installer is a per-user install — there's no UAC / admin prompt. Manager is installed under your user account at %LOCALAPPDATA%\Programs\meshO Manager.
  4. Accept the default install location (recommended) or change it.
  5. Click Install.
  6. On the final page, leave Launch meshO Manager now ticked and click Finish.

The installer creates:

  • A Start Menu entry under "meshO Manager"
  • A desktop shortcut

Both shortcuts launch the tray app, not the server directly — see The tray icon (Windows) below.

Allowing the install on Windows ​

Until Manager ships with a code-signing certificate that Microsoft recognises, you'll have to click past two or three "are you sure?" prompts during install. None of them indicate a real problem — they just mean Microsoft hasn't seen this exact file enough times yet to vouch for it.

1. Browser download warning. Chrome and Edge may flag the setup.exe as "not commonly downloaded" and refuse to save it.

  • Edge: click the ⋯ next to the blocked download → Keep → confirm Keep anyway.
  • Chrome: click the ⋮ next to the blocked download → Keep.

2. Windows SmartScreen — "Windows protected your PC". When you run the installer, a blue dialog may appear: "Microsoft Defender SmartScreen prevented an unrecognised app from starting."

  • Click More info (the small link below the message).
  • A Run anyway button appears — click it.

3. Antivirus quarantine. Some third-party antivirus products will quarantine the installer or the installed meshOManagerServer.exe because it's an unsigned executable that listens on a network port. If Manager fails to start after install, check your antivirus's quarantine list and add an exclusion for the install folder (%LOCALAPPDATA%\Programs\meshO Manager).

Install on macOS ​

  1. Double-click the downloaded .dmg. Finder mounts it and opens a window showing meshO Manager.app next to an Applications shortcut.
  2. Drag meshO Manager.app onto the Applications shortcut to copy it across.
  3. Eject the disk image — drag its icon to the Trash, or click the ⏏ next to its entry in the Finder sidebar.
  4. Open Applications and launch meshO Manager for the first time.
  5. Work around Gatekeeper — macOS blocks the first launch because Manager isn't notarised by Apple yet. Which message you see, and how to clear it, depends on your Mac — see Allowing the app on macOS below.
  6. Once you've allowed it, the app launches into the menu bar — see The menu bar icon (macOS) below.

Allowing the app on macOS ​

Manager isn't notarised by Apple yet, so macOS blocks it the first time you launch it. This is expected and does not mean anything is wrong with the download — you just need to clear the block once. After the first successful launch, macOS remembers your decision and Manager opens normally from then on (including auto-updates).

Which message you get depends on the macOS version and how the app was downloaded — not on whether your Mac is Intel or Apple Silicon — so follow the section that matches what you see:

"…is damaged and can't be opened. You should move it to the Bin/Trash." ​

This is the most common message, on Apple Silicon and Intel Macs alike. Despite the wording, the app is not damaged — macOS shows this because your browser tagged the download with a "quarantine" flag and Manager isn't notarised. Do not move it to the Bin.

The one reliable fix is to strip the quarantine flag from Terminal. Open Terminal (Applications → Utilities → Terminal, or press ⌘+Space and type "Terminal"), then paste this line and press Return:

bash
xattr -cr /Applications/meshO\ Manager.app

Then launch meshO Manager normally from Applications. That's it — the command only removes the quarantine flag; the app itself is untouched.

Right-click → Open does not clear the "damaged" message, on any Mac — only the Terminal command above does. If you tried right-clicking first and it still refused, that's expected; run the command and you're set.

"…can't be opened because it is from an unidentified developer" / "Apple could not verify…" ​

Some Macs show this milder message instead. Here you have two options — either works:

Option A — Right-click → Open. In the Applications folder, right-click (or Control-click) meshO Manager.app and choose Open. A dialog appears warning that the developer can't be verified — click Open to confirm. Double-clicking the app instead of right-clicking won't show the Open button — it just blocks.

Option B — Approve from System Settings. If the right-click dialog only offers Cancel (no Open):

  • Open System Settings → Privacy & Security.
  • Scroll to the Security section. You should see a message: "meshO Manager.app was blocked from use because it is not from an identified developer."
  • Click Open Anyway next to that message.
  • Authenticate with Touch ID or your password if prompted.
  • Launch the app again — this time a dialog will offer an Open button. Click it.

If Option A or B doesn't clear it, fall back to the Terminal command from the "damaged" section above — xattr -cr /Applications/meshO\ Manager.app clears the block regardless of which message you saw.

Why does this happen? Apple requires developers to submit each app build to its notarisation service, which scans for malware and signs the result. Manager isn't put through that process yet, so macOS treats it as coming from an unidentified developer and blocks the quarantined download. Notarisation is on the roadmap and will remove these steps for future versions. It is not related to which browser you used — Safari, Chrome and Edge all tag downloads with the same quarantine flag.

Downloading cards on this Mac? One more one-time step, unrelated to Gatekeeper: macOS doesn't recognise SportIdent's USB stations, so the browser can't see your reader until you install the Silicon Labs CP210x driver. See SportIdent USB stations on macOS. You don't need it if this Mac is only the server and cards are downloaded elsewhere.

Install on Linux ​

The Linux build is distributed as an AppImage — a single self-contained file you can run from anywhere, with nothing to install system-wide.

  1. Download the AppImage (meshOManager-latest-linux-x64.AppImage) using the link above.

  2. Make it executable — either in your file manager (Properties → Permissions → "Allow executing file as program") or from a terminal:

    bash
    chmod +x meshOManager-*-linux-x64.AppImage

  3. Run it — double-click in your file manager, or from a terminal:

    bash
    ./meshOManager-*-linux-x64.AppImage

Your browser opens automatically to http://localhost:5154/manager once the server is up. If nothing opens (for example on a minimal install with no xdg-open or google-chrome on the PATH), open that URL yourself.

No tray icon yet. Unlike Windows and macOS, the Linux build does not add a system-tray/menu-bar icon in this version. The AppImage runs the server directly in the foreground:

  • Started from a terminal, the server logs to that terminal; press Ctrl+C there to stop it.
  • Started by double-clicking, it runs in the background with no window. Quit it from your system monitor, or from a terminal with pkill -f meshOManager / pkill -f meshOManagerServer.

A proper tray launcher (matching Windows/macOS) is on the roadmap. Until then, Manager on Linux doesn't start at login or restart itself after a crash on its own — use systemd for that, as described below.

FUSE requirement. AppImages need FUSE to mount themselves. Most desktop distributions ship it; if you see an error like "dlopen(): error loading libfuse.so.2", either install your distro's FUSE 2 package (e.g. sudo apt install libfuse2 on Debian/Ubuntu) or run the AppImage with the --appimage-extract-and-run flag, or use the portable folder instead: meshOManager-<version>-linux-x64.zip, from the releases page.

Keeping Manager running on Linux ​

On Linux, systemd — the service manager on almost every modern distribution — can do what the tray app does on Windows and macOS: start Manager when you log in, and start it again if it stops unexpectedly.

  1. Put the AppImage somewhere it will stay, for example ~/Applications/, and make it executable as above.

  2. Create the file ~/.config/systemd/user/mesho-manager.service with this in it, changing the ExecStart line to where your AppImage is (%h means your home folder):

    ini
    [Unit]
Description=meshO Manager
# About the limit the Windows and macOS tray apps use: six starts in ten minutes (the first and
# five restarts), and then it stops trying.
StartLimitIntervalSec=600
StartLimitBurst=6

[Service]
ExecStart=%h/Applications/meshOManager-latest-linux-x64.AppImage
# Start it again whenever it stops without being told to, as the tray apps do. Being told to is
# `systemctl --user stop`, which systemd does not undo.
Restart=always
# A flat wait, where the tray apps wait a little longer each time.
RestartSec=2
# Nobody asked for a browser window when systemd starts it.
Environment=MESHO_SKIP_BROWSER_AUTO_OPEN=1

[Install]
WantedBy=default.target

  3. Turn it on, and start it now:

    bash
    systemctl --user daemon-reload
systemctl --user enable --now mesho-manager.service

  4. On a computer with no screen, let it start at boot without anyone logging in:

    bash
    sudo loginctl enable-linger "$USER"

systemctl --user stop mesho-manager stops it, and it stays stopped — systemd only restarts it when it stops on its own, the same as Quit on the other platforms. systemctl --user disable --now mesho-manager stops it and stops it starting at login. systemctl --user status mesho-manager shows whether it's running.

If it keeps stopping, systemd stops trying, as the tray apps do, and systemctl --user start is refused for the rest of the ten minutes. Once you've fixed the cause, start it again — the Linux version of Start Server — with:

bash
systemctl --user reset-failed mesho-manager
systemctl --user start mesho-manager

How the server runs in the background ​

Manager is split into two pieces:

  • The server — the background process that holds your event data, receives radio punches from a connected meshO Prime field unit, and serves the web UI.
  • A small tray / menu bar app that starts the server, keeps an icon visible so you can interact with it, and shuts the server down cleanly when you quit.

SportIdent USB reader stations (BSM7-USB / BSM8-USB) are not handled by the server. They're read directly by the browser on whichever device runs the download desk, using the browser's built-in Web Serial support, and the downloads are sent up to the server from there. That's why your download desk can be a different computer to the server — the SportIdent reader plugs into the download laptop, not the server. (meshO Prime, on the other hand, does plug into the server — see above.)

You never see a console window or a main app window. The server runs silently in the background; everything you see is in a browser tab.

When the tray / menu bar app starts:

  1. It launches the server as a child process.
  2. The server binds to port 5154 by default and starts serving the web UI.
  3. Your browser opens automatically to http://localhost:5154/manager — Google Chrome if it's installed, otherwise your default browser — when you opened Manager yourself. A start at login, or a restart after Manager stopped unexpectedly, doesn't open a browser.
  4. The tray / menu bar icon stays visible so you can re-open the browser, find your data files, read the documentation, or quit.

If Manager stops unexpectedly ​

Manager starts itself again. Nobody needs to be at the computer, so this also works on a computer with no screen.

  • If the server stops — it crashes, or something ends it — the tray / menu bar app starts it again within a few seconds, or up to half a minute if it has already stopped several times. The menu then shows a line at the top saying when that happened.
  • If the tray / menu bar app itself stops — it crashes, or it's ended from Task Manager or Activity Monitor — it is started again too, and starts the server with it.
  • Quitting is different. Quit from the tray / menu bar is a deliberate stop, and Manager stays stopped until you open it again (or until you next log in, if Start at Login is on — see Launching at login).

If the server keeps stopping — six times in ten minutes — Manager stops trying, because something is wrong that restarting won't fix (another program holding port 5154, for example). The line at the top of the menu then reads Server stopped: it kept stopping unexpectedly, an alert explains what went wrong, and Start Server in the menu tries again once you've fixed it.

A restart doesn't resume a live event on its own. If an event was live when the server stopped, it comes back as interrupted. Open Manager in a browser — on any device — and choose Resume event when it asks, or Resume event on the event's dashboard. Until you do, radio punches from meshO Prime aren't being recorded. See the dashboard.

Tip: If you have Google Chrome installed, Manager opens in it. Chrome is the browser the UI is developed and tested against, so it tends to give the best results. Other browsers also work, though card download and reading SportIdent stations need Chrome, Edge or Firefox 151 or later.

On the server machine, use localhost. When you're working on the computer that runs the server, always reach Manager at http://localhost:5154/manager — that's what the tray / menu bar app opens for you. It's the preferred address rather than the machine's host name or IP: it's shorter, it always works regardless of which network the computer is on, and localhost is automatically a secure context so card download works without any HTTPS setup. Save the IP address for the other devices (see below).

The documentation works offline. The Documentation item in the tray / menu bar opens the copy that ships inside Manager itself, served at http://localhost:5154/docs/ alongside Manager — so it's there at an event with no internet, and it matches the version you have installed. The same pages are online at docs.mesho.live if you'd rather read them on another device.

The tray icon (Windows) ​

After install, look for the meshO icon in the system tray (bottom-right of the taskbar, near the clock). You may need to click the ^ arrow to see hidden icons.

Available actions:

ActionHow
Open Manager in browserDouble-click the tray icon, or right-click → Open (or Ctrl+O while the menu is open)
Find your event files in ExplorerRight-click → Show Files in Explorer
Read the documentationRight-click → Documentation
See the installed versionRight-click → About
Start Manager when you log in, or stop it doing soRight-click → Start at Login (ticked by default)
Restart the serverRight-click → Restart Server — it reads Start Server while the server is stopped
Turn off a forgotten Access Protection PINRight-click → Reset Access Protection PIN
Quit (also stops the server)Right-click → Quit (or Ctrl+Q while the menu is open)

The menu bar icon (macOS) ​

After launch, look for the meshO icon in the menu bar at the top-right of the screen.

Available actions:

ActionHow
Open Manager in browserClick the menu bar icon → Open (or ⌘O while the menu is open)
Re-open Manager after closing the browser tabClick the menu bar icon → Open, or simply launch meshO Manager again from Applications, the Dock or Spotlight
Find your event files in FinderClick the menu bar icon → Show Files in Finder
Read the documentationClick the menu bar icon → Documentation
See the installed versionClick the menu bar icon → About
Start Manager when you log in, or stop it doing soClick the menu bar icon → Start at Login (ticked by default)
Restart the serverClick the menu bar icon → Restart Server — it reads Start Server while the server is stopped
Turn off a forgotten Access Protection PINClick the menu bar icon → Reset Access Protection PIN
Quit (also stops the server)Click the menu bar icon → Quit (or ⌘Q while the menu is open)

Manager doesn't appear in the Dock or ⌘+Tab switcher by design — it's a background app, controlled from the menu bar. Launching it again while it's already running doesn't start a second copy: it re-opens Manager in your browser, exactly as Open does.

Opening Manager on other devices ​

The other devices at your event — laptops, tablets, phones, TVs — connect to the server over your local network.

1. Take the link from Settings → Server ​

The easiest way is to let Manager give you the link. On the server, open Settings → Server. Under Access links you'll find a ready-made link for each part of Manager — Manager, Registration, Spectator, Kiosk, Info and Commentary — each by the computer's name and by its IP address, with Show QR code to open one on a phone or tablet without typing. Which of the two to hand each device is explained in Reaching the server: name or IP; when in doubt, use the IP one.

If you'd rather work it out yourself, find the server's local IP address:

  • Windows: open Command Prompt and run ipconfig. Look for an IPv4 Address under your active network adapter (e.g. 192.168.1.42).
  • macOS: open System Settings → Network, click your active connection, and read the IP address at the top.

2. Open the link on the other device ​

On the other device, open a web browser and navigate to the link, for example:

http://192.168.1.42:5154/manager

That's it — no install, no account. The page loads the full Manager UI and stays in sync in real time with everyone else. If you've set a PIN in Settings → Access protection, the manager screens and the registration desk ask for it first; the spectator, kiosk and leaderboard screens never do.

Tip: Bookmark the URL on each device, or save it as a Home Screen shortcut on phones and tablets, so volunteers can re-open it with one tap on event day.

A download laptop needs HTTPS. A browser only lets a page use a card reader over a secure link, and localhost is the only address that counts as secure without it. To download cards on any computer other than the server, turn on Enable HTTPS in Settings → Server, restart the server, and trust meshO's certificate on that laptop once. See HTTPS and certificates.

Different port? ​

If you've changed the HTTP port in Settings → Server, use that port number instead of 5154 in the URL.

Nothing loads on the other device? ​

  • Allow access from other devices on the network in Settings → Server must be on (it is, to begin with). Off, only the server computer itself can open Manager. A change to it takes effect the next time the server starts — Restart Server in the tray or menu bar.
  • The device must be on the same network as the server, and the server's firewall must let it in (below).
  • If the name-based link fails, use the IP one — see Reaching the server: name or IP.

Firewall prompt on first launch ​

Windows may show a Windows Defender Firewall prompt the first time the server starts, asking whether to allow Manager to communicate on private and public networks. Tick Private networks and click Allow access — without it, other devices on the network can't reach the server.

Quitting Manager ​

Quit through the tray / menu bar icon:

  • Windows: right-click the tray icon → Quit.
  • macOS: click the menu bar icon → Quit.

This shuts down the server cleanly, and Manager stays stopped — it isn't started again the way it is after a crash (see If Manager stops unexpectedly). Closing the browser tab on its own does not stop the server — the server keeps running in the background until you quit from the tray / menu bar.

Use Quit, not Task Manager or Activity Monitor. Ending Manager from Task Manager (End task) or Activity Monitor (Force Quit) looks the same as a crash, so Manager starts itself again a second later.

Tip: You don't have to quit between events. Manager is happy sitting in the tray / menu bar indefinitely — leave it running and it'll be there for the next event with all your previous events still loaded. Many users just leave it running all the time.

Warning: Don't shut down the server PC mid-event. The server flushes event data to disk continuously, but a sudden power-off can still cost you the last few seconds of in-flight data. Always quit Manager first, or use the OS shutdown command (which gives Manager a chance to exit cleanly).

Re-launching ​

  • Windows: open the Start Menu and search for "meshO Manager", or use the desktop shortcut.
  • macOS: open Applications → meshO Manager, or launch it from Spotlight (⌘+Space, type "meshO").

Manager re-opens silently into the tray / menu bar and reopens your browser to the events page. Your previous events, settings, and downloads are all preserved — they live in a separate folder from the application itself (see Where your data is stored).

Launching at login ​

Once you've opened Manager once, it starts automatically when you log in. It starts quietly into the tray / menu bar without opening a browser.

To stop it doing that, untick Start at Login in the tray / menu bar menu. Tick it again to turn it back on. It's per user and per computer.

  • Windows lists it as meshO Manager under Task Manager → Startup apps. Disabling it there works too.
  • macOS 13 and later lists it under System Settings → General → Login Items (Login Items & Extensions on newer versions), in Allow in the Background. Turning it off there works too. The first time Manager adds itself, macOS shows a "Background Items Added" notification — that's expected.

If you turn it off in Task Manager or System Settings, Manager's own menu still shows Start at Login ticked — it can't see that switch. To turn it back on, use the same place you turned it off.

Added Manager to your login items by hand in an earlier version? Remove that entry (the shortcut in shell:startup on Windows, or meshO Manager under Open at Login on macOS). Otherwise both start it at login and a browser window opens each time.

Opened Manager straight from the disk image on macOS? It doesn't add itself to login then, because the disk image won't be there next time. Copy it to Applications and open it from there.

Running Manager on a computer with no screen ​

Manager can run on a computer that sits in a box with no monitor, keyboard or mouse — a Mac mini or a small PC with meshO Prime plugged in, for example. Everyone uses it from a browser on another device. Set it up once, with a screen attached:

  1. Install Manager and open it once. Start at Login is on by default, so from then on it starts whenever the computer's user logs in.
  2. Make the computer log in by itself. The tray / menu bar app runs inside a logged-in session, so the computer has to log in on its own after it starts up.
    • macOS: System Settings → Users & Groups → Automatically log in as, and choose the user (on macOS 12, System Preferences → Users & Groups → Login Options → Automatic login). FileVault has to be off for this option to be available.
    • Windows: turn on automatic sign-in for the user (for example with Microsoft's Autologon tool from Sysinternals).
  3. Stop it from going to sleep while it's plugged in.
    • macOS: in System Settings (System Preferences on macOS 12), open Energy — Energy Saver on older versions, or Battery → Options on a laptop — and turn on Prevent automatic sleeping when the display is off.
    • Windows: Settings → System → Power & sleep (Power & battery → Screen and sleep on Windows 11) and set sleep to Never when plugged in.
  4. Have it start up again after a power cut, if it can.
    • macOS: in the same Energy (or Energy Saver) settings, turn on Start up automatically after a power failure.
    • Windows: look for Restore on AC power loss (or similar) in the computer's firmware settings.
  5. Write down its address from Settings → Server — see Reaching the server: name or IP — so you can reach it from another device.

From then on Manager starts when the computer does, starts itself again if it stops unexpectedly (see If Manager stops unexpectedly), and you never need to touch the computer itself. One thing still needs a person: after a restart in the middle of an event, open Manager from any device and choose Resume event.

Updating ​

Manager checks for new versions in the background and tells you when one is available. You can apply updates manually, or let Manager apply them automatically when nothing's going on.

When a new version is available ​

A notification appears in the bottom-right corner of the Manager UI:

A new version (X) is available. Your current version is Y.

The notification has three buttons:

  • Dismiss — hides the notification in this browser tab. Reloading the page doesn't bring it back; it shows again in a new tab or window, or the next time you open Manager.
  • Update now — downloads and installs the new version immediately. The server stops, replaces itself, and restarts. Every connected browser shows the update's progress, and the page reloads automatically once the new server is ready (usually 10–30 seconds).
  • Release notes — opens the release page in a new tab so you can see what changed.

Tip: The update notification is automatically hidden while a live event is running, so an installer banner can't distract a timing operator. It shows again once the event is finished.

Automatic updates ​

If you'd rather not think about it, turn on automatic updates:

  1. Open Settings → Auto update.
  2. Turn on Automatically install updates.

With auto-update on, the server checks for new versions every 30 minutes and applies them when all of these are true:

  • No event is currently live.
  • No browser tab is connected to Manager.

Those two guards mean an auto-update never interrupts an active event, and never yanks the page out from under you mid-session. If either guard fails, the update is deferred — auto-update will simply try again at the next check. The first check is made about five minutes after the server starts.

While browsers are connected and no event is live, the notification banner appears instead and you choose when to apply the update. While an event is live, nothing appears until it's finished.

Manual check for updates ​

You can also force a check at any time:

  1. Open Settings → Auto update.
  2. Click Check for updates.

If a newer version exists, an Update now button appears next to the result. Click it to apply the update immediately. Manager won't install an update while an event is live: it tells you an event is running, and the update waits until the event has finished.

Installing an update manually ​

If you'd rather install updates by hand turn off Automatically install updates and download a new installer the same way you did for a fresh install — use the direct download links above.

  • Windows: run the new setup.exe and let it install over the existing version — the installer closes a running Manager for you before it copies files, so you don't need to quit it from the tray first. You'll see the same SmartScreen and browser warnings as the original install — clear them the same way (see Allowing the install on Windows).
  • macOS: quit Manager from the menu bar, mount the new .dmg, and drag meshO Manager.app onto the Applications shortcut, choosing Replace when prompted. Because the new download carries a fresh quarantine attribute, Gatekeeper will block the first launch of the replacement — clear it the same way (see Allowing the app on macOS).
  • Linux: stop the running server, download the new .AppImage, make it executable (chmod +x), and replace the old file. Linux updates are always manual — the in-app updater is disabled on the AppImage because it can't modify the read-only AppImage file, so you won't get a one-click Update now there. Your events and settings are preserved across the swap (they live in ~/.local/share/meshO Manager, separate from the AppImage).

Your events, settings, and downloads are kept across the upgrade.

Auto-updates don't hit these warnings. When Automatically install updates is on, the in-app updater downloads new versions directly (not through your browser, so no quarantine attribute on macOS) and on macOS it ad-hoc re-signs the new bundle and clears the quarantine flag for you. There's nothing to click past.

Where your data is stored ​

Manager keeps application files (the program itself) and your data (events, settings, logs) in separate places. Uninstalling or upgrading Manager only touches the application files — your data is preserved.

Windows ​

  • Application files: %LOCALAPPDATA%\Programs\meshO Manager (e.g. C:\Users\<you>\AppData\Local\Programs\meshO Manager).
  • Settings, logs and runtime state: %LOCALAPPDATA%\meshO Manager.
  • Events and downloads: C:\Users\Public\Documents\meshO Manager — shared across users on the machine.

The fastest way to find your event files is Tray icon → Show Files in Explorer.

macOS ​

  • Application: /Applications/meshO Manager.app.
  • Events, settings, logs and downloads: ~/Library/Application Support/meshO Manager.

The fastest way to find your event files is Menu bar icon → Show Files in Finder.

Linux ​

  • Application: wherever you saved the .AppImage (it's a single self-contained file — nothing is installed elsewhere).
  • Events, settings, logs and downloads: ~/.local/share/meshO Manager (or $XDG_DATA_HOME/meshO Manager if you've set XDG_DATA_HOME).

Uninstalling ​

Windows ​

  1. Quit Manager from the tray icon.
  2. Open Settings → Apps → Installed apps, find meshO Manager, and choose Uninstall. This also removes its Start at Login entry.

Your data folders (%LOCALAPPDATA%\meshO Manager and Public\Documents\meshO Manager) are intentionally left in place so you don't lose events if you reinstall later. Delete them manually if you want them gone.

macOS ​

  1. Quit Manager from the menu bar icon.
  2. Drag meshO Manager.app from Applications to the Trash.

Quit it first. Skip step 1 and Finder refuses with "meshO Manager.app can't be moved to the Bin because it's open" — the server is still running in the background. Manager won't be listed in Force Quit Applications either: that window only lists apps with windows, never menu bar apps. Click the meshO menu bar icon → Quit, then drag it to the Trash.

Untick Start at Login before you quit, if you're removing Manager for good. Otherwise its login entry stays behind: it does nothing once the app is gone, but macOS keeps listing it under Login Items. To remove it afterwards, delete ~/Library/LaunchAgents/live.mesho.manager.login.plist.

Your data folder (~/Library/Application Support/meshO Manager) is left in place. Delete it manually if you want a clean slate.

Linux ​

  1. Stop the server (see No tray icon yet — Ctrl+C in its terminal, or pkill -f meshOManagerServer). If you set it up under systemd, run systemctl --user disable --now mesho-manager instead, delete ~/.config/systemd/user/mesho-manager.service, and run systemctl --user daemon-reload. If you turned on lingering for a computer with no screen, sudo loginctl disable-linger "$USER" turns it off again.
  2. Delete the .AppImage file.

Your data folder (~/.local/share/meshO Manager) is left in place. Delete it manually if you want a clean slate.