'could not reach control plane' / activation failed
'could not reach control plane' / activation failed
The robot can’t reach the internet. The
192.168.123.x network is the
robot’s internal bus, not internet — connect its Wi‑Fi / 4G‑5G uplink and
confirm with curl https://kovio-api.fly.dev/healthz.'fleet key invalid or revoked' (HTTP 401/403)
'fleet key invalid or revoked' (HTTP 401/403)
The key is wrong or has been revoked. Double-check the key you were issued;
if it was revoked, contact your Kovio representative for a new one. Nothing
is installed in this case.
'unsupported runtime' (HTTP 409)
'unsupported runtime' (HTTP 409)
The robot’s Python/glibc/architecture isn’t one we ship a build for. Send
your Kovio rep the
arch / python / glibc line the installer printed and
we’ll add a matching build.Service isn't running after install
Service isn't running after install
Check
systemctl status kovio and journalctl -u kovio -n 100. If it
exited with code 77, the key/robot was revoked (the service intentionally
stays down). Otherwise share the logs with your Kovio rep.Robot appears, but impressions stay at 0
Robot appears, but impressions stay at 0
Events are arriving but not costing into impressions — usually because the
matching campaign’s advertiser has no balance, so charges are declined. Fund
the advertiser or point the fleet at a funded campaign.
sha256 mismatch — refusing to install
sha256 mismatch — refusing to install
The downloaded artifact didn’t match its expected hash; the installer
refuses to proceed. Re-run the install; if it persists, contact Kovio.