Skip to content
Sidemesh

Troubleshooting

“No providers configured”

Section titled ““No providers configured””

Run sidemesh up for the default Codex path, or run sidemesh setup and select at least one provider.

”Port already in use”

Section titled “”Port already in use””

Another Sidemesh daemon is running. Run sidemesh status to find it. Use --allow-duplicate if you genuinely need two daemons.

”Unknown provider: pi”

Section titled “”Unknown provider: pi””

The daemon was built before the Pi provider. Rebuild:

Terminal window
npm run build && npm link

“Connection failed” in mobile app

Section titled ““Connection failed” in mobile app”
  • Verify host and client are on the same network (or Tailscale)
  • Check sidemesh status shows healthy
  • Verify token matches exactly
  • Try http://HOST:PORT/healthz in a browser

Pi model list is empty

Section titled “Pi model list is empty”

Pi has no authenticated providers. Run pi /login for your model provider.

”Port already in use” with systemd

Section titled “”Port already in use” with systemd”

A stale daemon is holding the port:

Terminal window
sudo sidemesh service restart --yes

App says “daemon is restarting” or “daemon is updating” but the host does not come back

Section titled “App says “daemon is restarting” or “daemon is updating” but the host does not come back”

This works best when Sidemesh is installed as a background service on macOS or Linux.

If you started the daemon with sidemesh daemon, sidemesh start, or sidemesh up, start it again yourself or switch to the service install path:

Terminal window
# macOS
sidemesh service install
sidemesh service restart --yes


# Linux
sudo sidemesh service install
sudo sidemesh service restart --yes

Slow session list with Pi

Section titled “Slow session list with Pi”

The first scan after startup walks all .jsonl files. Subsequent calls use a stat-based fingerprint cache. Large session files (>10 MB) may still parse slowly on cache misses.