Troubleshooting

Node.js was not found (or is too old)

LocHub needs a local Node.js 22.11 or newer to run its service; it checks this when you launch LocHub — open the LocHub tab (Tools > LocHub > Open LocHub), or run Push, Push (Dry Run), Pull or Restart Service — and, if anything is wrong, opens a "LocHub: Node.js required" window naming the problem, with a Download Node.js link and an Open Settings button; the tab or the notification shows the error too. The window opens once per failed launch attempt — it does not stack a second copy while one is already open.

LocHub looks for Node.js in this order, stopping at the first one that works:

1. The per-user setting Editor Preferences > Plugins > LocHub > Node.js Executable, if you have set one — when set, only that exact path is used.
2. PATH.
3. The usual install locations for the current OS (macOS: /opt/homebrew/bin, /usr/local/bin, /opt/local/bin; Linux: /usr/bin, /usr/local/bin, /snap/bin; Windows: the Program Files\nodejs folder, and Volta's install folder).
4. Version managers (nvm, fnm, asdf, mise) — the newest suitable version any of them has installed.
5. macOS/Linux only: the user's login shell, in case Node.js is only set up there.

If none of these finds a working Node.js, the window lists exactly where it looked. Install Node.js 22.11+, or point the Node.js Executable setting at an existing install, then just launch LocHub again (for example press Reload in the tab); if it is still not found, restart the editor so it picks up the updated PATH.

Port already in use

The Service Port setting (Project Settings > Plugins > LocHub > Service, default 47810) is shared across every project on the machine. If another project's LocHub service already owns that port, LocHub refuses to touch it and reports:

Port <N> is used by the LocHub service of <other project path>; set another Service Port in Project Settings > Plugins > LocHub.

Pick a different Service Port for one of the two projects and reopen LocHub (or restart the editor).

The service runs but does not answer

If something is listening on the configured port but never answers a health check, LocHub reports:

The LocHub service runs but does not answer <url>/api/health. Use Tools > LocHub > Restart Service.

Use that menu command; if it keeps happening, check the log path the message names.

"Outdated build" — the service does not report its project

A LocHub service left running from an older version of the plugin cannot be identified as belonging to any particular project, so LocHub refuses to adopt or use it: