VS Code/Cursor Remote-SSH连接卡在.log和.pid检查阶段求助

问题现象 #

使用VS Code（v1.108.2）或Cursor通过Remote-SSH连接特定内部机构远程服务器时，连接流程持续卡在**"Checking .log and .pid"**阶段，手动检查远程服务器的/home/zzh/.vscode-server/目录，发现日志中提到的.log和.pid文件从未生成。

连接日志 #

[16:37:33.986] Log Level: 1
[16:37:33.988] Registering chat participant remote-ssh
[16:37:33.998] SSH Resolver called for "ssh-remote+labserver", attempt 1
[16:37:34.000] remote.SSH.useLocalServer = false
[16:37:34.001] remote.SSH.useExecServer = false
[16:37:34.001] remote.SSH.bindHost = {}
[16:37:34.001] remote.SSH.showLoginTerminal = false
[16:37:34.001] remote.SSH.remotePlatform = {"Kirin Galaxy":"linux","JetautoREDIAN":"linux","Kirin Galaxy host":"linux","labserver":"linux", ...}
[16:37:34.008] VS Code version: 1.108.2
[16:37:34.008] Remote-SSH version: remote-ssh@0.122.0
[16:37:34.008] win32 x64
[16:37:34.011] Found relevant configuration for host labserver in JSON data
[16:37:34.011] SSH Resolver called for host: labserver
[16:37:34.011] Setting up SSH remote "labserver"
[16:37:34.017] Using commit id "c9d77990917f3102ada88be140d28b038d1dd7c7" and quality "stable" for server
[16:37:34.021] Install and start server if needed
[16:37:34.023] Checking ssh with "C:\...\ssh.exe -V"
[16:37:34.059] > OpenSSH_for_Windows_9.5p2, LibreSSL 3.8.2

[16:37:34.063] Running script with connection command: "ssh" -T -D 37333 labserver bash
[16:37:34.065] Terminal shell path: C:\Windows\System32\cmd.exe
[16:37:34.471] "install" terminal received data: ""
[16:37:34.675] "install" terminal received data: "zzh@10.201.2.54's password: "
[16:37:37.629] Got password response
[16:37:37.795] "install" terminal received data: "769e7714fd1d: running"
[16:37:37.807] "install" terminal received data: "Acquiring lock on /home/zzh/.vscode-server/bin/c9d77990917f3102ada88be140d28b038d1dd7c7/vscode-remote-lock.zzh..."
[16:37:37.807] \ln "/home/zzh/.vscode-server/bin/c9d77990917f3102ada88be140d28b038d1dd7c7/vscode-remote-lock.zzh.target" "/home/zzh/.vscode-server/bin/c9d77990917f3102ada88be140d28b038d1dd7c7/vscode-remote-lock.zzh"
[16:37:37.807] Installing to /home/zzh/.vscode-server/bin/c9d77990917f3102ada88be140d28b038d1dd7c7...
[16:37:37.807] 769e7714fd1d%%1%%
[16:37:37.807] Downloading with wget
[16:37:56.810] "install" terminal received data: "Download complete"
[16:37:56.810] 769e7714fd1d%%2%%
[16:37:56.810] tar --version:
[16:37:56.810] tar (GNU tar) 1.30
[16:37:56.810] Copyright (C) 2017 Free Software Foundation, Inc.
[16:37:56.810] License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>
[16:37:56.810] This is free software: you are free to change and redistribute it.
[16:37:56.810] There is NO WARRANTY, to the extent permitted by law. Written by John Gilmore and Jay Fenlason.
[16:37:57.652] "install" terminal received data: "Checking /home/zzh/.vscode-server/.c9d77990917f3102ada88be140d28b038d1dd7c7.log and /home/zzh/.vscode-server/.c9d77990917f3102ada88be140d28b038d1dd7c7.pid for a running server"

已尝试的无效操作 #

• 手动创建accepted--license-terms文件，自动检查仍无法识别服务器
• 在.vscode-server目录执行touch命令时表现异常（偶尔无法创建文件）
• 相同配置在其他云服务商服务器可正常运行，仅内部服务器出现此问题，怀疑是服务器环境的文件锁或VS Code远程SSH连接逻辑冲突导致

排查与解决步骤 #

1. 检查服务器文件系统权限与锁机制 #

• 确认.vscode-server目录权限：执行ls -ld /home/zzh/.vscode-server/和ls -l /home/zzh/.vscode-server/bin/，确保当前用户拥有读写执行权限
• 联系运维确认服务器是否启用特殊安全软件，限制了文件创建/重命名操作，或存在进程锁定.vscode-server目录
• 删除现有锁文件：执行rm -rf /home/zzh/.vscode-server/bin/*/vscode-remote-lock.zzh*，然后重新发起连接

2. 手动部署VS Code Server，跳过自动安装 #

• 提取日志中的commit id：c9d77990917f3102ada88be140d28b038d1dd7c7，下载对应版本的Linux x64 VS Code Server包
• 通过SCP将包上传到服务器的/home/zzh/.vscode-server/bin/c9d77990917f3102ada88be140d28b038d1dd7c7/目录
• 解压包：执行tar -xzf vscode-server-linux-x64.tar.gz --strip-components=1
• 手动启动Server：执行./server.sh --port 0 --host 127.0.0.1 --enable-remote-auto-shutdown，之后重新发起SSH连接

3. 修改VS Code Remote-SSH配置，规避锁检测 #

• 在VS Code的settings.json中添加以下配置：

  "remote.SSH.useLocalServer": true,
  "remote.SSH.showLoginTerminal": true
  

• 开启showLoginTerminal可在连接时弹出终端，手动监控Server启动过程；useLocalServer切换为本地代理模式，绕过部分远程锁检测逻辑

4. 测试基础文件操作，排查文件系统异常 #

• 在.vscode-server目录下反复执行touch test.log && rm test.log，观察是否每次都能成功创建/删除文件。若存在失败情况，说明文件系统或安全策略存在限制，需联系运维进一步排查

内容的提问来源于stack exchange，提问作者Dream