bad_base64

Summary

base64 decode failed in `{0}`

Help

the encoded blob is not valid standard base64

Details

When this fires

A base64 blob came in that the standard alphabet decoder could not parse. The context string in the error message tells you which one. Common sources:

• A key line in authorized_keys or [admin].authorized (key payload garbled).
• The x-nanook-nonce header sent by a buggy client (context "nonce").
• The x-nanook-signature header (context "signature").
• An on-disk identity file at ~/.nanook/admin/id_ed25519.

What to check

• For a corrupted private key, regenerate with nanook keygen and re-add the matching .pub line to the trust list.
• For a custom client, use standard base64 (not URL-safe) and avoid line wrapping.