LocalMate problems

Problems with LocalMate show up in two places: in the LocalMate status line at the top of every Tools → Integrations tab, and in the program you are trying to connect. Work through the sections in order.

"Error: Connection failed — is LocalMate running?"

The console could not reach LocalMate.

Look for LocalMate's icon in the menu bar (macOS) or system tray (Windows). If it is not there, start LocalMate.
Click the icon and choose Settings.... Compare LocalMate Port with the LocalMate Port field in the console. They must match; 40001 is the default.
Click Connect in the console.

If LocalMate is running but the status never changes, its server did not start. The usual cause is one of the next two sections.

No internet on the first run

LocalMate fetches a security certificate from RHR the first time it runs, and renews it when fewer than 30 days remain. Without it the browser refuses to connect and LocalMate cannot start its server. Make sure the computer is online, then quit LocalMate and start it again. Afterwards it works offline from the certificate it saved.

A port is already in use

LocalMate listens on three ports: 40001 for the console and TCI clients, 2237 for WSJT-X messages and 2001 for N1MM+. If another program holds one of them, that feature silently does nothing.

Port 40001 is rarely contested. If it is, change LocalMate Port in LocalMate's settings window and in the console.
Port 2237 is WSJT-X's own UDP port. If you run WSJT-X and a program such as JTAlert or GridTracker that also listens on 2237, only one of them gets the messages. Give the second program a different port, and set the matching Server Port or Destination Port in the console.
Port 2001 is a common CAT port. Change Port on the N1MM+ tab if another program uses it, and enter the new address in N1MM+.

"LocalMate is already running"

LocalMate runs once per computer. If this message appears when you open it, the first copy is already in the menu bar or tray; click that icon instead.

My software cannot connect

You are not connected to a station. LocalMate only accepts TCI and N1MM+ connections while the console is connected to a station. Connect first, then start or reconnect the program.
Another console tab has the session. Only one console tab or browser can use LocalMate at a time. Close the others, or disconnect LocalMate in them.
The address is wrong. TCI apps use ws://127.0.0.1:40001, plain ws://. N1MM+ needs the address and port in one field, exactly 127.0.0.1:2001, with the radio set to Kenwood and the port to TCP.
N1MM+ was started first. In N1MM+, choose Tools → Rescan/Reset Radios after you connect to the station.
The tab's checkbox is off. Check Accept TCI clients, WSJT-X UDP Server, Send to UDP server or Accept N1MM+ connections as appropriate. Remember that WSJT-X Server and WSJT-X Client cannot both be on.

When a program is connected, the status line counts it: 1 TCI client connected, 1 N1MM+ client connected.

WSJT-X did not get the grid square

AutoGrid must be on in two places: the console's WSJT-X Server tab, and WSJT-X itself under Settings → General → AutoGrid. The grid is sent when you connect to a station, so connect in the console before you expect it to change.

A WSJT-X contact was not logged

Logging on the WSJT-X Server tab adds contacts to the logbook currently selected in the console's Log Entry panel. If none is selected, the console shows WSJT-X contact with … was not logged — no RHR logbook selected. Pick a logbook and log the contact by hand this once; later contacts import on their own.

An orange A LocalMate update is available banner on the Integrations page means your copy is older than the current release. Quit LocalMate, download the new version from the link and start it. LocalMate does not update itself.

Where LocalMate keeps its files

Settings and the saved certificate are in ~/Library/Application Support/LocalMate/ on macOS and %APPDATA%\LocalMate\ on Windows. Deleting that folder resets LocalMate; it fetches a new certificate on the next start.