PuTTY SSH Authentication Fixes for CSPID and Preauth Errors

You see “No supported authentication methods available” because the SSH server has reached the login stage but cannot find an authentication method that both it permits and PuTTY can complete. Most often, the username is wrong, the server accepts public keys only, or PuTTY is not offering the private key that matches a public key on the account. If the message says server sent: publickey, the server is telling PuTTY that public-key authentication is the available route, not that it sent you a usable key. Use the table to identify which part of the connection needs attention first.

Symptom Likely Cause Practical Fix
No supported authentication methods available Wrong username, wrong SSH endpoint, or no mutually usable method Verify the server address, connection port, and login name with the server administrator or hosting provider.
server sent: publickey The server allows public-key login and does not offer password login Install the correct public key on the intended account and configure PuTTY with the matching private key.
PuTTY tries a key, then disconnects The key is not authorized for that account, is the wrong type, or requires a certificate Confirm the key fingerprint, account, certificate requirements, and server-side key policy.
Server logs include preauth The connection ended before authentication completed Check server access rules, account restrictions, key authorization, and connection-rate controls.
PuTTY reports a timeout PuTTY never reached SSH authentication Check the hostname, network route, VPN, firewall, and SSH service availability instead of changing keys.

What the PuTTY Authentication Error Means

SSH authentication happens after PuTTY has connected to the server and established an encrypted session. At that point, the server advertises or accepts one or more login methods, and PuTTY attempts one that it can use.

Common SSH authentication methods include:

  • Public key: PuTTY proves it holds a private key that matches a public key authorized on the server.
  • Password: The server requests the account password.
  • Keyboard-interactive: The server presents one or more prompts, often for a password, one-time code, or institutional login system.
  • GSSAPI or single sign-on: Authentication is delegated to an identity system such as Kerberos.
  • Host-based authentication: The server trusts a connecting machine under a tightly managed policy.

The error does not usually mean PuTTY itself is broken. It means the server did not accept any credential PuTTY could present, or the server did not offer a method PuTTY is configured to use.

A password prompt appears only when the server permits a password-like authentication method. PuTTY cannot force a password prompt when the server has been configured for public-key-only access.

How to Fix “No Supported Authentication Methods Available” in PuTTY

Fix the error by using the intended account and endpoint with an authentication method the server allows.

Step 1: Record the Exact Error and Connection Details

Before changing keys or server settings, capture the details of the failed attempt.

  1. Copy the full PuTTY error text, including anything in parentheses such as server sent: publickey.
  2. Confirm the hostname or IP address you entered.
  3. Confirm the connection port supplied by the server owner, cloud provider, or internal documentation.
  4. Confirm the username. SSH accounts are case-sensitive on many systems.
  5. Check whether PuTTY showed a host-key warning before the error. A new or unexpected host key is a separate security issue; stop and verify the server identity before continuing.

A correct key for one host or account will not authenticate you to a different host or account.

Step 2: Verify You Are Logging In as the Intended Account

The username controls where the SSH server looks for authorization rules and public keys. It is common to have a valid key but use the wrong account name.

  1. Ask the administrator, hosting provider, or project documentation for the exact SSH username.
  2. Confirm whether the environment expects a personal account, a deployment account, or a provider-created account.
  3. Start a fresh PuTTY connection using that account name.
  4. Do not assume that root, admin, or your local Windows username is valid on the remote system.

If the server is shared, each user normally has separate authorization. Adding a public key to one account does not make it valid for another account.

Step 3: Identify the Authentication Method the Server Allows

Read the method list in the PuTTY error rather than guessing.

  • If the error includes publickey, prepare to use an authorized key pair.
  • If it includes password or keyboard-interactive, PuTTY should prompt after the connection reaches the authentication stage. If it does not, recheck the username and endpoint.
  • If the organization requires single sign-on, a certificate, a smart card, or a managed SSH client, a normal standalone private-key file may not be sufficient.
  • If no useful method is offered, the account may be denied before authentication or the connection may be reaching the wrong SSH service.

Ask the server owner a focused question: “Which SSH authentication method is enabled for this account, and which public-key fingerprint or identity should I use?” That avoids the risky habit of enabling password login just to make a connection work.

Step 4: Authorize the Correct Public Key on the Server

For public-key authentication, the server needs the public half of your key pair attached to the account you are trying to use. Your private key stays on your computer and should never be copied to the server, pasted into chat, or emailed.

Use a safe administrative access method, such as a provider console, an existing administrator session, or an approved out-of-band access channel, to do the following:

  1. Obtain the public key that corresponds to the private key you intend to use in PuTTY.
  2. Add that public key to the SSH authorization configuration for the intended remote account.
  3. Preserve the public key as one complete line. Copying it with line breaks, missing prefixes, or extra characters can make it invalid.
  4. Ensure the account owns its SSH authorization files and that the server can read them under its security policy.
  5. Confirm the account is not locked, expired, restricted to another source network, or blocked by an SSH access rule.

If you do not administer the server and have no alternate access, you cannot fix this from PuTTY alone. The person who manages the account or host must authorize your public key or provide the approved login method.

Step 5: Configure PuTTY With the Matching Private Key

PuTTY must offer the private key that matches the public key installed on the server.

  1. Open the saved PuTTY session you use for this server.
  2. In PuTTY’s SSH authentication settings, choose the private-key file for this specific connection.
  3. Use a PuTTY-compatible private-key file. If you received a key in another format and PuTTY does not accept it, import or convert it with PuTTYgen instead of editing the key file manually.
  4. If you use an SSH authentication agent, make sure the intended key is loaded into that agent and that PuTTY is allowed to use it.
  5. If several keys are available, configure this session to offer the intended one first rather than relying on a long list of agent keys.

A server can reject a connection before the correct key is attempted when too many unrelated identities are offered. Using the specific key for the specific saved session prevents that failure pattern.

Step 6: Retry Once and Confirm the Result

Start a new connection after saving the session settings.

  1. Confirm that PuTTY reaches the expected host.
  2. Enter the correct account name.
  3. Unlock the private key only if PuTTY asks for its passphrase.
  4. Confirm that you receive a shell prompt, command banner, or the remote service’s expected post-login response.
  5. If the same error remains, compare the public-key fingerprint installed on the server with the fingerprint of the private key selected in PuTTY.

At this point, avoid repeatedly retrying with random usernames or keys. A precise record of the host, account, offered method, and key fingerprint gives an administrator enough information to identify the remaining server-side restriction.

Resolve Public-Key and Root Login Problems

Public-key and root login problems are resolved by matching the account, private key, server policy, and any required certificate, smart card, or SSH agent.

Public Key Is Present but Still Rejected

A public key can exist on the server and still fail authentication for several reasons:

  • It was installed for a different user account.
  • The private key selected in PuTTY belongs to another key pair.
  • The public-key line was damaged during copying.
  • The server requires an SSH certificate in addition to the key.
  • The account has a login restriction, expired access, or an allowed-source-address rule.
  • PuTTY is trying unrelated keys before it reaches the intended one.

Check the public-key fingerprint rather than comparing only file names. Key files are often renamed, copied, or stored in shared credential folders, while the fingerprint identifies the actual key material.

Public-Key Login for the Root User

A key authorized for a regular account does not automatically authorize root. The root account has its own authorization configuration, and many servers deliberately disallow direct root SSH login.

Use a normal named account when the server policy supports it, then elevate privileges through the organization’s approved administrative process. If direct root access is explicitly required, an administrator must authorize the matching public key for root and ensure the SSH service permits that account to log in.

After the policy and key are confirmed, create a new PuTTY session for the root account rather than changing a working regular-user session. This keeps the account, private key, and target host clearly separated.

Keys Managed by Certificates, Smart Cards, or an SSH Agent

Some environments use an identity provider, hardware token, certificate authority, or centrally managed SSH agent. In those environments, possessing a plain private key may not satisfy the server.

Confirm whether the server expects:

  • A public key alone
  • A public key plus an SSH certificate
  • A smart-card or security-device-backed key
  • A key offered through an approved SSH agent
  • A corporate single sign-on method

Use the organization’s supported client configuration and retry with the assigned account. If the environment issues short-lived certificates, an expired certificate can look like an ordinary public-key rejection until the server logs are checked.

Understand CSPID and Preauth Messages

What CSPID Means in This Situation

CSPID is not a standard SSH user-authentication method name like publickey, password, or keyboard-interactive. In a PuTTY-related error report, it is usually an environment-specific label for an account, connection profile, certificate provider, service, or internal system.

Treat it as a clue about where the connection is managed, not as an authentication option to select in PuTTY. Identify whether CSPID refers to:

  • The remote host or gateway
  • A saved connection profile
  • A user or organization identifier
  • A certificate or smart-card provider
  • An internal access-management system

Then ask the administrator of that system which SSH username, endpoint, and credential type it requires. The repair is still to make PuTTY and the server agree on one permitted method.

What preauth Means While Connecting

preauth means “before authentication completed.” It commonly appears in server-side SSH logs when a connection closes or is rejected before the user has successfully logged in.

A preauth message can result from a rejected key, a disallowed username, an address-based restriction, an authentication policy, or a connection control that ends the session early. Review the corresponding server log entry using the connection time, source address, and attempted username, then correct the specific policy or credential mismatch and test a fresh connection.

Separate Authentication Failures From Network Timeouts

A timeout is not the same as “No supported authentication methods available.”

With an authentication-method error, PuTTY has already reached an SSH server and started negotiating a login. With a timeout, PuTTY has not reached that stage at all.

For a timeout, check these items in order:

  1. Verify the hostname or IP address is current.
  2. Confirm the SSH connection port with the service owner.
  3. Connect to any required VPN or internal network before opening PuTTY.
  4. Check whether a firewall, corporate network policy, security group, or router rule blocks the connection.
  5. Confirm that the SSH service is running on the target host.
  6. Test again from an approved network after the route or firewall issue is corrected.

Do not regenerate keys or change SSH authentication settings to solve a timeout. Those changes cannot help until the network connection reaches the SSH service.

Confirm the Connection and Prevent a Repeat

After a successful login, save enough information to reproduce the working setup without guesswork:

  • Server hostname and connection port
  • SSH username
  • Required authentication method
  • Private-key file or agent identity used
  • Public-key fingerprint authorized on the server
  • Whether a certificate, VPN, jump host, or single sign-on system is required

Keep separate PuTTY sessions for different environments and accounts. A saved session for a production host should not silently reuse the username or key intended for a test server.

If access stops working later, inspect the server’s authentication logs or provider audit records using the failed connection time. They usually reveal whether the server rejected the account, could not read the key authorization, did not recognize the key, required a certificate, or blocked the connection under a policy.

Frequently Asked Questions

What are the common authentication methods used in SSH?

The most common SSH methods are public key, password, keyboard-interactive prompts, GSSAPI or single sign-on, and host-based authentication. Public-key authentication uses a private key on your computer and a matching public key authorized on the server. PuTTY can only use methods that the server offers and that your connection is configured to complete.

What does server sent: publickey mean in PuTTY?

It means the server reported publickey as an available or required authentication method. The server might not have given PuTTY a usable public key or PuTTY might not have automatically selected the correct private key. Configure PuTTY to offer the private key whose matching public key is authorized for the remote username.

Why does PuTTY not ask for my password?

PuTTY does not ask for a password when the server does not offer password or keyboard-interactive authentication. A public-key-only server expects a private key that matches a public key authorized for the target account. Verify the username and key pairing instead of waiting for a password prompt that the server will never send.

Can I fix this error on Windows?

Windows is not usually the cause of this SSH error. PuTTY on Windows can authenticate successfully when the host, username, private key, and server policy match. Focus on the remote account and the credential PuTTY is offering, then retry the saved connection.

How do I fix a network connection timed out error in PuTTY?

A PuTTY timeout means the SSH connection did not reach the authentication stage. Verify the server address, connection port, VPN requirement, firewall rules, and SSH service availability. Once PuTTY reaches the SSH service, it will either prompt for an allowed credential or show an authentication-specific error that you can address with the correct account and key.