claude-code - 💡(How to fix) Fix [BUG] Claude Code Desktop SSH connection fails on Windows with Synology NAS on non-standard port [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#48428Fetched 2026-04-16 07:00:25
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×3closed ×1commented ×1cross-referenced ×1

Error Message

Claude Code Desktop app on Windows fails to establish SSH connection to a Synology NAS on a non-standard port (6069). App briefly shows "Installing Claude Code..." then silently fails with "Connection failed". No error details shown. Terminal SSH to the same host works perfectly.

Error Messages/Logs

No error message displayed in app UI. App shows "Connection failed" only.

Code Example

No error message displayed in app UI. App shows "Connection failed" only.
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?

Claude Code Desktop app on Windows fails to establish SSH connection to a Synology NAS on a non-standard port (6069). App briefly shows "Installing Claude Code..." then silently fails with "Connection failed". No error details shown. Terminal SSH to the same host works perfectly.

Environment:

  • Client: Windows 11, OpenSSH 9.5p2 (C:\Windows\System32\OpenSSH\ssh.exe)
  • Remote: Synology NAS (DSM), OpenSSH 8.2, port 6069
  • Auth: ed25519 key (no passphrase)
  • Claude Code on remote: v2.1.109 at ~/.local/bin/claude
  • Node.js on remote: v20.19.5

Debugging already attempted:

  • Terminal SSH works: ssh -v -p 6069 -i ~/.ssh/id_ed25519 [email protected] succeeds
  • Added host key via ssh-keyscan -p 6069 >> ~/.ssh/known_hosts
  • Confirmed ~/.local/bin in PATH on remote (.bashrc and .bash_profile)
  • Tried alias-based host (nas) and explicit user@ip — both fail
  • Created symlink C:\usr\bin\ssh -> C:\Windows\System32\OpenSSH\ssh.exe — no effect

Suspected cause: app uses internal Node.js ssh2 library, not system OpenSSH, and fails to handle non-standard ports or Windows key paths correctly. Related: #25659, #26809, #32734

What Should Happen?

Successful SSH connection and Claude Code session, same as terminal SSH.

Error Messages/Logs

No error message displayed in app UI. App shows "Connection failed" only.

Steps to Reproduce

  1. Open Claude Code Desktop app on Windows 11
  2. Add SSH connection: host [email protected], port 6069, identity file ~/.ssh/id_ed25519
  3. App shows "Installing Claude Code..." briefly
  4. App shows "Connection failed" with no further details

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.109 (Claude Code)

Platform

Other

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

This is a Desktop app SSH remote connection issue, not a CLI issue. The app connects to a Synology NAS (192.168.1.238) via SSH on port 6069. The remote server has Claude Code installed and working. The issue appears to be that the Desktop app uses an internal Node.js ssh2 library rather than the system OpenSSH binary, causing it to fail silently with non-standard port configurations on Windows.

extent analysis

TL;DR

The issue is likely due to the Claude Code Desktop app's internal Node.js ssh2 library failing to handle non-standard ports or Windows key paths correctly, and a potential workaround is to use a standard port or modify the app's configuration to use the system OpenSSH binary.

Guidance

  • Verify that the issue is indeed related to the non-standard port by trying to connect to the Synology NAS using a standard port (e.g., 22) and checking if the connection is successful.
  • Check the Claude Code app's configuration to see if there are any options to specify the SSH library or binary to use, and consider modifying it to use the system OpenSSH binary.
  • Investigate the related issues (#25659, #26809, #32734) to see if they provide any insights or solutions to the problem.
  • Consider downgrading to a previous version of Claude Code that worked with non-standard ports, if possible.

Example

No code snippet is provided as the issue is related to the app's internal library and configuration.

Notes

The issue appears to be specific to the Claude Code Desktop app on Windows and non-standard ports, and may not be related to the Synology NAS or the SSH connection itself. The fact that terminal SSH works perfectly suggests that the issue is with the app's internal library or configuration.

Recommendation

Apply workaround: try using a standard port or modifying the app's configuration to use the system OpenSSH binary, as the issue is likely related to the internal Node.js ssh2 library. This is because the app's internal library may not be compatible with non-standard ports or Windows key paths, and using a standard port or the system OpenSSH binary may resolve the issue.

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