Why does SSH report too many authentication failures?
An SSH client may offer several agent identities before reaching the right one, exhausting the server’s attempt allowance. This can happen even when you know the correct key. Restrict the client’s identity for this connection first.
Instructions
1. Inspect loaded identities
The agent inventory helps explain why many keys might be offered.
ssh-add -lThis shows public fingerprints only. Several loaded identities are legitimate when you manage several services.
2. Retry with the intended identity only
Select the key explicitly for the intended remote user.
ssh -o IdentitiesOnly=yes -i "$env:USERPROFILE\.ssh\server_ed25519" adminuser@203.0.113.10The setting narrows this invocation. It does not remove other agent keys or alter the server’s authentication limit.
3. Review one host profile if the retry works
Set IdentityFile and IdentitiesOnly in that server’s Host entry, then use ssh -G to verify it. If the explicit identity is still rejected, investigate the account or key enrolment rather than increasing server-wide authentication limits.
Check the result
- The connection offers the intended identity without a long sequence of unrelated attempts.
- The session authenticates using the expected account.
Troubleshooting
- The explicit attempt still fails
- Read the precise authentication error; the selected public key may not be authorised.
- The alias ignores the setting
- Inspect effective client configuration and the ordering of wildcard Host entries.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.