atuinsh/atuin · error
Hub password change failed with status {status}
Error message
Hub password change failed with status {status} What it means
Final fallback in the auth-module change_password: the Hub response was a non-success status with no parseable structured error and not 401/403, so only the raw status is reported. This catches gateway/proxy failures and unexpected server states during the password-change request.
Source
Thrown at crates/atuin-client/src/auth.rs:420
Some("2fa_required") => return Ok(MutateResponse::TwoFactorRequired),
Some("invalid_2fa_code") => {
bail!("invalid two-factor code");
}
_ => {
bail!("{}", err.reason);
}
}
}
match status {
StatusCode::UNAUTHORIZED => {
bail!("current password is incorrect");
}
StatusCode::FORBIDDEN => {
bail!("invalid login details");
}
_ => {
bail!("Hub password change failed with status {status}");
}
}
}
async fn delete_account(
&self,
password: &str,
totp_code: Option<&str>,
) -> Result<MutateResponse> {
let hub_token = self.hub_token.as_deref().ok_or_else(|| {
eyre::eyre!("Not logged in to Atuin Hub. Please run 'atuin login' to authenticate.")
})?;
if !hub_token.starts_with("atapi_") {
bail!(
"Your Hub session token is invalid. Please run 'atuin login' to re-authenticate \
with Atuin Hub."
);View on GitHub (pinned to c0c717ab04)
Solutions
- Retry after a delay; 5xx statuses here are usually transient
- Check https://status.atuin.sh for incidents
- Use the interpolated {status} to diagnose proxy or server-side failures
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at crates/atuin-client/src/auth.rs:420 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of atuinsh/atuin@c0c717ab04 (2026-09-12).
Data as JSON: /api/errors/75f502ecaa27ad04.
Report an issue: GitHub.