-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
ankurCES edited this page Jun 4, 2026
·
3 revisions
-
blumi: command not found—~/.local/binisn't onPATH. Addexport PATH="$HOME/.local/bin:$PATH"to your shell rc, or setBLUMI_INSTALL_DIR. -
Source build fails — install Rust (https://rustup.rs); the source path needs
cargo. -
No provider configured — run
blumi login. See Configuration.
-
serve statussays not running —blumi serve start; check~/.blumi/serve.log. -
Phone can't reach it — confirm you installed with
--host <LAN-ip>(not loopback) and that phone + machine share the same Wi-Fi. Test from another device:curl http://<ip>:7777/api/health. -
"password required" — a non-loopback bind must have a password. Run
blumi serve pair. -
Linux: service doesn't start before login —
loginctl enable-linger $USER. - macOS: "Unload failed" during install — harmless (it pre-unloads a non-existent agent).
-
Gateway not discovered — add it by IP (
host:port) instead; ensureserve statusis running and you're on the same LAN. (Android needs multicast permission, which the app declares.) -
Login fails — re-check the password from
blumi serve pair. - Stale view — pull-to-refresh on the chat; cached tabs revalidate automatically.
-
Voice key won't "stick" — keys are write-only; the app shows
saved ✓and never returns them. Re-enter the key to re-authenticate / reload the voice dropdown. See Voice.
-
Peers don't appear — every node needs
grid.enabled: trueand the samegrid.secret; all must be on the same LAN with mDNS allowed. Verify withGET /api/grid/peers. See Grid. -
A node vanished after changing the secret — its
grid_idchanged; restart all nodes with the same secret (identity is set at startup).
-
CI red on
cargo fmt— runcargo fmt --alland commit. -
Clippy passes locally but fails in CI — CI runs on Linux; macOS-only code must be
#[cfg(target_os = "macos")]-guarded or it tripsdead_codeunder-D warnings. -
A TUI test flakes — tests that set the process-global icon mode must be serialized
(a shared
Mutex), since cargo runs tests in parallel.
Still stuck? Open an issue with blumi --version, your OS, and the relevant ~/.blumi/serve.log
lines (redact secrets).