claude-code - 💡(How to fix) Fix [BUG] Claude Desktop SSH: "Host denied (verification failed)" on Windows — VM never starts (isGuestConnected: false) [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#49060Fetched 2026-04-17 08:52:03
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×5commented ×1

Error Message

2026-04-16 [warn] Host <REMOTE_IP>:<CUSTOM_PORT> is not in known_hosts 2026-04-16 [error] Connection error: Host denied (verification failed) 2026-04-16 [error] Connection failed: Host denied (verification failed)

vm-info.json: "isGuestConnected": false (at every launch)

Code Example

2026-04-16 [warn] Host <REMOTE_IP>:<CUSTOM_PORT> is not in known_hosts
2026-04-16 [error] Connection error: Host denied (verification failed)
2026-04-16 [error] Connection failed: Host denied (verification failed)

vm-info.json: "isGuestConnected": false (at every launch)
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

SSH connection always fails with "Host denied (verification failed)" in Claude Desktop on Windows. The internal VM never starts (isGuestConnected: false in vm-info.json). The known_hosts file at the expected location exists but is ignored by the app.

What Should Happen?

The VM should start on app launch and the SSH connection should complete successfully.

Error Messages/Logs

2026-04-16 [warn] Host <REMOTE_IP>:<CUSTOM_PORT> is not in known_hosts
2026-04-16 [error] Connection error: Host denied (verification failed)
2026-04-16 [error] Connection failed: Host denied (verification failed)

vm-info.json: "isGuestConnected": false (at every launch)

Steps to Reproduce

  1. Open Claude Desktop on Windows 11
  2. Go to Code tab > New SSH connection
  3. Fill in: host <USERNAME>@<REMOTE_IP>, port <CUSTOM_PORT>, identity file path
  4. Click connect
  5. Error: "Host denied (verification failed)"

Note: Direct SSH from PowerShell works perfectly with the same credentials. Hyper-V is enabled. known_hosts manually populated. KEX algorithms restricted on server. Nothing resolves the issue.

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

1.2773.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Related issues: #26809, #25659, #35073 Attaching ssh.log and cowork_vm_node.log.

cowork_vm_node.log

ssh.log

extent analysis

TL;DR

The SSH connection issue in Claude Desktop on Windows may be resolved by ensuring the known_hosts file is correctly formatted and accessible, or by adjusting the KEX algorithms to match the server's restrictions.

Guidance

  • Verify that the known_hosts file is in the correct location and has the correct permissions, as the error message suggests it is being ignored.
  • Check the KEX algorithms restricted on the server and ensure they match the algorithms supported by Claude Desktop, as a mismatch could cause the connection to fail.
  • Review the ssh.log and cowork_vm_node.log files for any additional error messages or clues that could help diagnose the issue.
  • Consider testing the SSH connection with a different set of KEX algorithms or a different known_hosts file to isolate the cause of the problem.

Example

No code snippet is provided as the issue is related to configuration and logging rather than code.

Notes

The issue may be related to the specific configuration of the SSH server or the Claude Desktop application, and further debugging may be required to determine the root cause. The fact that direct SSH from PowerShell works perfectly with the same credentials suggests that the issue is specific to Claude Desktop.

Recommendation

Apply workaround: Adjust the KEX algorithms to match the server's restrictions, as this is a potential cause of the issue and can be easily tested.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING