atuinsh/atuin · error
Hub registration failed with status {status}
Error message
Hub registration failed with status {status} What it means
Final fallback in the auth-module register: registration on the Hub failed with a non-success status whose body did not decode as a HubErrorResponse, so only the HTTP status is reported. The username may already be taken, but here the server gave an unparseable or unexpected response.
Source
Thrown at crates/atuin-client/src/auth.rs:353
.send()
.await
.context("failed to connect to Atuin Hub")?;
let status = resp.status();
if status.is_success() {
let reg: RegisterResponse = resp.json().await?;
return Ok(AuthResponse::Success {
session: reg.session,
auth_type: reg.auth,
});
}
if let Ok(err) = resp.json::<HubErrorResponse>().await {
bail!("{}", err.reason);
}
bail!("Hub registration failed with status {status}");
}
async fn change_password(
&self,
current_password: &str,
new_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 registration; if the username is taken, choose another
- Check the interpolated {status}: 5xx indicates a server-side issue
- Confirm connectivity and that no proxy is intercepting the request
Defensive patterns
Strategy: retry
When it happens
Trigger: Thrown at crates/atuin-client/src/auth.rs:353 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/241e465cd8591238.
Report an issue: GitHub.