When things go wrong

For each problem: what you see, what causes it, what helps.

Map, Mini FC and the panels stay empty

Symptom. The pages do not load, the in-game panel shows nothing, and the app reports that port 55055 could not be opened.

Usually handled by itself. If 55055 cannot be opened, the tracker switches to one of the fallback ports 45055-45058 for that session and says so in a message. Map, Mini FC and the in-game panels find the port on their own (the in-game panels from the current SSC-Tracker panel packages). Only when all of them are blocked do the pages stay empty - then the steps below apply. The next start tries 55055 again first.

Cause. Port 55055 lies in the range Windows uses to assign outgoing connections their local port (49152-65535). So some program may already have it before the tracker starts - in which case the port is neither "blocked" nor occupied by a server, it has simply been handed out.

What helps. Click the message: the tracker then takes 55055 out of that range permanently (one admin dialog, once). After that no other program can snatch it. If that does not work, another program is holding the port right now - after restarting the PC, start the tracker first and repeat the reservation.

A rarer case: Hyper-V, WSL or Docker reserve whole blocks of this range. The tracker then says explicitly that Windows has reserved the port; here only a restart helps, which redistributes the blocks.

Cause. MSFS reads its Community folder only at start-up. A package installed just now is unknown to the running simulator.

What helps. Quit MSFS and start it again. Then switch the panel on in the toolbar.

A second device cannot reach the map

Cause. The local web server listens on localhost only, as long as Windows has not granted it access to all network interfaces.

What helps. Open ☰ → Connections. If it says "LAN access is off", click Enable LAN access - that sets the URL reservation and the firewall rule in a single admin step. Then close the window once and open it again; the LAN addresses will work.

If it still does not: are the PC and the device on the same network? Is a guest network or client isolation active in the router? Is a second firewall (Norton, Bitdefender …) blocking the port?

The NB21 logger does not follow

Symptom. The logger knows a different task from the tracker, or the message "NB21 logger is not running while airborne" appears.

Cause and remedy. The sync depends on NB21 logger sync in the settings (a change takes effect after restarting the app). With it on: when connecting, the logger reports its task, and the tracker only takes it over if it has none of its own. If you load a task in NB21 in the middle of a session, the logger wins - except over a running task, which is off limits. The other way round, Set logger to current task pushes your task across.

The height profiles stay empty

Cause. The terrain tiles for the route are missing.

What helps. Switch Auto load on in the settings under ELEVATION - then the tracker fetches them as soon as a task is loaded. The progress is shown in the Preflight tab next to the heading. Without internet, only what is already in the cache is available.

The settings are suddenly back to default

Cause. The app writes its settings to %LocalAppData%\SSC-Tracker\settings.json. If that file is edited from outside while the app is running, the app's next save overwrites the change again.