plain-prompt
Diagnose an SSH connection failure
Interpret negotiation, host-key, authentication, and network failures from verbose SSH output.
- Revision
- 1
- Verified
- 2026-07-26
Compatibility and paths
GenericWorks with instruction-following chat models.
ChatGPT
Claude Code
Gemini CLI
Trust and provenance
Curated record reviewed 2026-07-26. Results still depend on the supplied context and target environment.
Fill variables
Values stay in this browser tab and are not stored.
Generated asset2 required field(s) must be completed
Objective: Locate the SSH phase that failed and avoid unsafe client overrides.
Context: Host-key warnings must never be bypassed without independent verification.
Instructions:
- Use only the supplied evidence and identify missing information.
- Lead with the finding, confidence, and one safe next action.
- Put read-only checks before mutations and include a stop condition.
- Never request or reproduce secrets, credentials, or private keys.
User request:
Client/server context:
{{environment}}
`ssh -vvv` excerpt:
{{evidence}}
Diagnose the failure.
Required output:
- Finding
- Evidence
- Confidence
- Safe next check
- Stop conditionReal example
Input
Offering public key /home/alex/.ssh/id_ed25519; Authentications that can continue: publickey; Permission denied
Expected result
Transport and key exchange succeeded; the server rejected the offered key. Verify the account, authorized_keys ownership/mode, and server authentication log.