Plink hangs
What “Plink hangs” usually means
When PuTTY reports Plink hangs, the client has already attempted a network or protocol step and failed before a normal interactive shell is available. This guide explains what the message usually means on Windows clients, which local settings to verify first, and when the problem is almost certainly on the server, firewall, or DNS path rather than inside the PuTTY GUI.
Plink waits indefinitely—often for host-key confirmation, password/passphrase prompts, or because stdout/stderr handling in automation does not surface prompts.
Independent resource: Putty.info is educational only and is not affiliated with the official PuTTY project. Compare symptoms against the official documentation for your installed version.
Symptoms you will see
Operators usually notice this failure in one of a few repeatable ways. Capture the exact dialog text, the hostname and port from the Session panel, and whether the failure happens before or after a username prompt—those details decide which checklist below applies.
- Automation job sits with no output.
- Interactive Plink appears frozen awaiting input you did not notice.
Likely causes ranked by frequency
Several independent conditions can produce the same client-facing wording. Work from the outside in: reachability first, protocol selection second, authentication third. Changing key files will not fix a TCP refusal, and opening a wider firewall will not fix a rejected public key.
- First-time host key prompt in non-interactive context.
- Passphrase prompt without a console.
- Waiting on server that never sends a banner due to TCP issues.
- Missing -batch in contexts where prompts should fail fast.
Step-by-step client checks
Use this ordered checklist on a workstation you control. Prefer saved sessions so Host Name, Port, and Connection type stay consistent while you isolate one variable at a time.
- Run the same target in GUI PuTTY first to accept a verified host key.
- Use Pageant so Plink is not waiting on passphrase UI in services.
- Add appropriate batch options for CI so prompts become hard failures.
- Enable verbose flags carefully and capture logs locally.
- Confirm Host Name/Port like any other connection problem.
- See glossary and learn guides for Plink versus GUI responsibilities.
Do not paste private keys, passphrases, or production passwords into Putty.info tools or contact forms. Diagnose locally with PuTTY, Plink, PSCP, or PSFTP from an official install.
When it is a server or network issue
Ensure automation service accounts have keys installed and host keys pre-provisioned via secure configuration management—not click-through on build agents.
If TCP connects from another network path but fails from yours, involve the network team with traceroute/path evidence rather than repeatedly regenerating keys. If authentication fails after a banner appears, collect the server sshd logs for the same timestamp and username—client-side retries alone rarely reveal AccountLocked, Match blocks, or AllowUsers denials.