通过VSCODE-SSH去连接堡垒机登录,通过LDAP方式创建的账号，发现报错

JumpServer
1

[09:50:12.401] Setting up SSH remote “jump-DashanDev”
[09:50:12.403] Using commit id “d045a5eda657f4d7b676dedbfa7aab8207f8a075” and quality “stable” for server
[09:50:12.406] Install and start server if needed
[09:50:17.860] getPlatformForHost was canceled[09:50:17.860] Resolver error:Error:Connecting was canceledat g.Canceled (c: \Users \Administrator\ .vscode \extensions \ms-vscode-remote ,remote-ssh-0.96.0 \out\extension.js:1:584343)at c: \Users \Administrator. vscode \extensions \ms-vscode-remote.remote-ssh-0.96.0\out \extension.js:1:643026at async t.withshowDetailsEvent (c: \Users\Administrator .vscode \extensions\ms-vscode-remote. remote-ssh-6,96. 0 out \extension.js:1:646432)at async t,resol ve (c:\Users \Administrator . vscode \extensions \ms-vscode-remote.remote-ssh-0.96,0\out\extension.js;1:644164)
at async c: \Users \Administrator.vscode \extensions \ms-vscode-remote.remote-ssh-0.96.0\out \extension.js:1:721750

2
  1. 确保 LDAP 用户已成功同步至 JumpServer，可在“用户管理”中确认该用户是否存在且状态正常。
  2. 用户通过 VS Code Remote-SSH 连接时，必须使用在 JumpServer 中托管的资产账号，且授权策略中账号类型需勾选“所有”，而非仅“手动输入账号”。
  3. 建议配置 SSH 公钥认证免密登录：在本地生成密钥对，将公钥添加至 JumpServer 用户的“SSH 公钥”中，并在 VS Code 的 SSH 配置中指定私钥路径（IdentityFile）。
  4. 检查 JumpServer 组件（如 Koko）是否正常运行，可通过 jmsctl status 查看服务状态。
  5. 查看日志 /data/jumpserver/core/data/logs/jumpserver.log 和 /data/jumpserver/koko/data/logs/koko.log 排查认证过程中的具体错误。
3

怎么解决呢,各位大佬

4

密钥登录是如何操作呢

5

发现能通过MFA认证可以正常登录,但是卡在了后面,[13:26:40.139] >
[13:26:41.326] > vscode-cli-8b3775030ed1a69b13e4f4c628c612102e30a681.tar.gz 0% 0 0.0KB/s --:-- ETA
[13:26:42.048] > vscode-cli-8b3775030ed1a69b13e4f4c628c612102e30a681.tar.gz 100% 8346KB 11.2MB/s 00:00

vscode-cli-8b3775030ed1a69b13e4f4c628c612102e30a681.tar.gz.done 0% 0 0.0KB/s --:-- ETA
[13:26:42.079] > vscode-cli-8b3775030ed1a69b13e4f4c628c612102e30a681.tar.gz.done 100% 9 0.4KB/s 00:00
[13:26:42.523] > Found flag and server on host
48903bd4754a%%2%%
tar --version:
[13:26:42.561] > tar (GNU tar) 1.23
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
这是自由软件：您可以自由地更改并重新发布它。
在法律所允许的范围内不含任何担保。

由 John Gilmore 和 Jay Fenlason 所写。
[13:26:42.877] > code 1.85.2 (commit 8b3775030ed1a69b13e4f4c628c612102e30a681)
[13:26:42.886] >
Running ssh connection command… /root/.vscode-server/code-8b3775030ed1a69b13e4f4c628c612102e30a681 command
d-shell --on-port --require-token 334ccabf279a &> “/root/.vscode-server/.cli.8b3775030ed1a69b13e4f4c628c61210
02e30a681.log” < /dev/null
printenv:
SELINUX_ROLE_REQUESTED=
SHELL=/bin/bash
SSH_CLIENT=10.99.102.232 35986 22
SELINUX_USE_CURRENT_RANGE=
QTDIR=/usr/lib64/qt-3.3
QTINC=/usr/lib64/qt-3.3/include
USER=root
VSCODE_AGENT_FOLDER=/root/.vscode-server
PATH=/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/dynar
rose/sbin
MAIL=/var/mail/root
PWD=/root
KDE_IS_PRELINKED=1
LANG=zh_CN.UTF-8
MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles
KDEDIRS=/usr
LOADEDMODULES=
SELINUX_LEVEL_REQUESTED=
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
HOME=/root
SHLVL=2
LOGNAME=root
CVS_RSH=ssh
QTLIB=/usr/lib64/qt-3.3/lib
SSH_CONNECTION=10.99.102.232 35986 10.99.102.124 22
MODULESHOME=/usr/share/Modules
LESSOPEN=|/usr/bin/lesspipe.sh %s
G_BROKEN_FILENAMES=1
module=() { eval /usr/bin/modulecmd bash $*
}
OLDPWD=/root/.vscode-server
_=/usr/bin/printenv
[13:26:42.892] >
Spawned remote CLI: 15347
[13:26:42.898] > Waiting for server log…
[13:26:42.917] > [13:26:57.583] Received install output:
SSH_AUTH_SOCK====
DISPLAY====
listeningOn====
osReleaseId==Linux==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/tmp==
platform==linux==
unpackResult==success==
didLocalDownload==1==
downloadTime====
installTime==329==
serverStartTime==14683==

[13:26:57.584] Failed to parse remote port from server output
[13:26:57.585] Resolver error: Error:
at m.Create (c:\Users\zyx.vscode\extensions\ms-vscode-remote.remote-ssh-0.105.0\out\extension.js:2:618542)
at t.handleInstallOutput (c:\Users\zyx.vscode\extensions\ms-vscode-remote.remote-ssh-0.105.0\out\extension.js:2:617353)
at t.tryInstall (c:\Users\zyx.vscode\extensions\ms-vscode-remote.remote-ssh-0.105.0\out\extension.js:2:737259)
at async c:\Users\zyx.vscode\extensions\ms-vscode-remote.remote-ssh-0.105.0\out\extension.js:2:698008
at async t.withShowDetailsEvent (c:\Users\zyx.vscode\extensions\ms-vscode-remote.remote-ssh-0.105.0\out\extension.js:2:701104)
at async A (c:\Users\zyx.vscode\extensions\ms-vscode-remote.remote-ssh-0.105.0\out\extension.js:2:694894)
at async t.resolve (c:\Users\zyx.vscode\extensions\ms-vscode-remote.remote-ssh-0.105.0\out\extension.js:2:698657)
at async c:\Users\zyx.vscode\extensions\ms-vscode-remote.remote-ssh-0.105.0\out\extension.js:2:881837
[13:26:57.590] ------请求指点

1 个赞
6

这边猜测问题可能是 VS Code 插件端口解析失败，非 JumpServer 认证故障，优先清理远程 vscode-server 缓存。版本兼容是次要诱因，升级 VS Code 及 Remote-SSH 插件可规避大部分兼容漏洞。若通过 JumpServer 连接，确保 koko 组件正常运行，无额外会话限制即可。

7

升级了就报错 VS Code 连接 SSH 报错 “The remote host may not meet VS Code Server’s prerequisites for glibc and libstdc++”

8

请问
远程的vscode-server是堡垒机上的还是要连接的资产上面的呢

9

根据这篇文档 使用 VSCode 工具连接 JumpServer 资产 - FIT2CLOUD 知识库 远程的 .vscode-server 部署在你要连接的「目标资产」上，而非 JumpServer 堡垒机（koko 所在服务器）。