Troubleshooting
Fixes for the problems people run into most.
A plan provider says it isn't installed or signed in
Claude, Codex, Grok, Cursor, Kimi and OpenCode run through their own apps. Install the app on the host the bot runs on, sign in with it once (for example claude auth login), then choose Connect again in Models & API keys. On a server, do this as the inkbot user over SSH.
"Sign in again" on a provider or plugin
The sign-in expired or was revoked. Open the provider or plugin and connect it again. For a plugin on a server, the sign-in opens on your PC and is handed to the server.
Bots can't get a computer
Computers need Docker on the bot's host. On your PC, start Docker Desktop. On a server, check docker ps works and that you didn't install with --no-docker. A computer also only starts when its memory limit (Settings → Computers) is free.
The app can't reach my server
- Check the service:
systemctl status inkbotandjournalctl -u inkbot -n 50. - An
https://address needs DNS pointing at the server and Caddy running (systemctl status caddy). http://addresses only work for127.0.0.1orlocalhost, for example through an SSH tunnel.- A
401means the token is wrong: compare it withserver-tokenin the server's data folder.
A webhook returns 401
The request has no secret, or the signature doesn't match. Check the secret in the sending app, or add ?key=<secret> to the URL. Signatures must be made over the exact body that's sent. See Webhook triggers.
A local model won't load or is slow
Open View log for the model to see what llama-server said. If it doesn't fit, pick a smaller quant (use Only ones that fit on the GPU), reduce its context length, or let experts move to system memory. Close other apps that use the GPU.
Dictation doesn't hear me
Check the microphone in Windows' privacy settings, and that InkBot is allowed to use it. With the speech model, the first use downloads it; wait for the download to finish.
A routine didn't run
Routines on your PC only run while InkBot is running. Turn on Run in the tray and Start with Windows, and Catch up on missed routines to run ones that were due in the last 12 hours. Check the routine's last status and the Incidents list.