Verified diagnostic signature
Incorrect sudo password
Ansible could not complete SSH server authentication or the later privilege-escalation authentication for the selected inventory target. Match this output from ansible, then continue with sourced, read-only checks.
- Confidence
- high
- Platforms
- linux · macos · windows
- Verified
- 2026-07-24
Recognized output
Signature matched locally
Incorrect sudo passwordOneLiners matches this pattern in your browser. Your pasted output is not stored or indexed.
Likely causes
What usually produces this signal
- The control node has no trusted host key for the selected address and port
- The managed host was rebuilt or rotated and its independently verified host key changed
- The play uses become but the runner has no interactive or protected noninteractive become credential
- The inventory selects the wrong remote user, become user, become method, or credential binding
- The remote sudo policy requires authentication or does not authorize the automation account
Safe next checks
Collect evidence before changing the system
Show the effective OpenSSH client configuration for a host
ssh -G <host> | sortThe output matches the expected target and exits without an error.
Diagnose an SSH connection without opening an interactive shell
ssh -vvv -o BatchMode=yes -o ConnectTimeout=10 <username>@<host> trueRe-run the corresponding read-only inspection and confirm the intended state.
Fetch the SSH host keys offered by a server
ssh-keyscan -H -p <port> <host>The output matches the expected target and exits without an error.
Show the current user and group identities
idThe output matches the expected target and exits without an error.
Related signals