Host mismatch

Code

AUTH/HOST_MISMATCH

What it means

In production, the token record pins an expected host/pod, but the client connected to a different pod. This prevents cross-pod token reuse when pods are not sharing auth state.

When it happens

• In production, the connected server pod does not match the expected host from the auth record.

Typical scenarios:

• Load balancer routed the client to a different pod than the one that issued the token
• Hostname/pod naming changed

How to handle

• Client should request a fresh route/token and reconnect.
• Server operators should confirm sticky routing (or shared auth store) if this becomes frequent.