SSH_DISCONNECT_NO_MORE_AUTH_METHODS_AVAILABLE
SSH_DISCONNECT_NO_MORE_AUTH_METHODS_AVAILABLE (14) is sent when all available authentication methods have been exhausted without success. The client has tried every method the server advertised and none succeeded. This is the terminal authentication failure disconnect, distinct from per-method failures which keep the connection open.
Code
14
Category
Disconnect
Standard
RFC 4253 §11.1
Description
SSH authentication works by the client trying authentication methods from the server's advertised list. The server sends SSH_MSG_USERAUTH_FAILURE after each failed attempt, listing remaining available methods. When the client determines it has no more methods to try – either because the server's list is empty or because all remaining methods require credentials the client does not have – it sends disconnect code 14.
This is distinct from reaching the server's MaxAuthTries limit. When MaxAuthTries is reached, the server sends SSH_MSG_DISCONNECT with this same code (or similar). When the client exhausts its own options, it sends code 14.
Common in automated scenarios: a CI pipeline with only an SSH key configured, connecting to a server that requires password authentication. The client tries publickey, fails (key not authorized), and then has no more methods to try.
Common Causes
- –Client has no more authentication methods to try after all failed
- –Server's MaxAuthTries limit reached (server side)
- –Key not in authorized_keys and no password authentication configured
- –All auth methods tried in automated context with limited credentials
- –Server only accepts methods the client does not support