ctl_remote_error

Diagnostic `nanook::ctl::remote_error`

Summary

admin returned `{0}`: {1}

Help

the agent rejected the request; check the code and message above

Details

When this fires

The admin server reached the request just fine but returned a structured ErrResp (see nanook-admin/src/wire.rs), and the client surfaces it as Remote(code, message). The code is the actionable bit: it'll be one of the dispatch codes (unknown_alert, unknown_collector, alert_not_silenced, reload_unavailable) or an auth code (missing_auth, unauthorized, bad_signature, clock_skew, replay, bad_auth, bad_json, bad_utf8, body_too_large).

What to check

  • Look up the inner code in this same error reference; each has its own page with the real fix.
  • For auth codes, point at the right identity:
nanook ctl --identity ~/.config/nanook/id_ed25519 state
  • For clock_skew: timedatectl status on both ends.