Cannot connect to JumpServer

[acracker]

I think the reason might be this: Jumpserver acts as an SSH proxy. When users connect, they're actually connecting to Jumpserver first, which then forwards the connection to the target server. Because of this, the returned information might be processed by Jumpserver, making it different from directly connecting to sshd.

[crschnick]

To get the original JumpServer functionality of SSH, you can also try to create a Custom SSH Connection in XPipe. There you can specify all necessary SSH config options, e.g. ProxyJump to use jump servers as you would with the SSH CLI.

[acracker]

Still report an error.

This configuration is available on other linux machines.

The local computer is windows.

[acracker]

I upgraded openssh in windows by running ssh config_xpipe and it worked

But the xipe is still not connected properly

[crschnick]

Weird, it should at least print why it was unsuccessful.

Does the log at Settings -> Troubleshoot -> Show log files say anything?

[acracker]

Only one error log

15:53:06:330 - info: Command finished {
    command=(call echo ^%DISPLAY^%)
    finishReason=NORMAL_FINISH
    exitCode=0
}
15:53:06:337 - info: Starting sub shell ... {
    manageParent=true
    command=set "BEACON_PORT=21721"&set "ASKPASS_SECRET=7e50a9fe-adf7-4fb7-9186-71xxxe3"&set "ASKPASS_REQUEST=d95ac4bc-ca6f-4628-8ffd-69xxxx"&set "ASKPASS_PREFIX=[ssh]"&set "SSH_ASKPASS=E:\software\xpipe-15.8\bin\xpipe.exe"&set "SSH_ASKPASS_REQUIRE=force"&set "DISPLAY=localhost:0.0"&ssh -oNumberOfPasswordPrompts=3 "test_xpipe" -F "C:\Users\admin\AppData\Local\Temp\config_-1510100210" -oStrictHostKeyChecking=accept-new -oIgnoreUnknown=RemoteCommand -oRemoteCommand=none -T -oNoHostAuthenticationForLocalhost=yes -oIdentitiesOnly=yes
    elevated=false
}
15:53:09:221 - error: Shell opener command was unsuccessful
io.xpipe.core.process.ProcessOutputException: Shell opener command was unsuccessful
	at io.xpipe.core.process.ProcessOutputException.withPrefix(ProcessOutputException.java:29)
	at io.xpipe.ext.proc.util.e.cf(SourceFile:192)
	at io.xpipe.ext.proc.n.p(SourceFile:1689)
	at io.xpipe.ext.proc.ssh.o.p(SourceFile:113)
	at io.xpipe.ext.proc.n.D(SourceFile:587)
	at io.xpipe.ext.proc.n.start(SourceFile:276)
	at io.xpipe.ext.proc.n.a(SourceFile:384)
	at io.xpipe.ext.proc.n.prepareIntermediateTerminalOpen(SourceFile:292)
	at io.xpipe.ext.proc.j.prepareTerminalOpen(SourceFile:121)
	at io.xpipe.app.terminal.TerminalLaunchRequest.setupRequest(TerminalLaunchRequest.java:97)
	at io.xpipe.app.terminal.TerminalLaunchRequest.lambda$setupRequestAsync$0(TerminalLaunchRequest.java:64)
	at io.xpipe.app.util.ThreadHelper.lambda$wrap$0(ThreadHelper.java:22)
	at java.lang.VirtualThread.run(VirtualThread.java:329)

[crschnick]

That is weird that it doesn't print anything about the failure cause, I will have to look into that.

Is this Windows 10 or 11?