-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot connect to JumpServer #494
Comments
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. |
I upgraded openssh in windows by running But the xipe is still not connected properly |
Weird, it should at least print why it was unsuccessful. Does the log at Settings -> Troubleshoot -> Show log files say anything? |
Only one error log
|
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? |
windows 11 |
Can you try whether https://github.com/xpipe-io/xpipe-ptb makes a difference |
After running the PTB version with administrator, I couldn't click any buttons.
|
uhh, that is not good. Not sure what is happening there. From the log, you can try to run |
|
And this still freezes? |
yes |
Alright, I will try to figure out what went wrong and come back to you. Because I did rework jumpservers in xpipe 16 |
So I looked into this and I don't think it is a freezing problem. If I look closely at the screenshot, the content is rendered but is very transparent for some reason. There is a dialog being shown that you probably can't see, that is why you can't click on anything. I think this is a rendering issue. I tried to fix it in the latest version of https://github.com/xpipe-io/xpipe-ptb, maybe that works. If that has the same issue, then I'm honestly not sure what broke. Because I didn't change anything rendering related in these builds compared to v15. |
I was able to reproduce this, will look into it as it's still not fixed |
https://github.com/xpipe-io/xpipe-ptb/releases/tag/16.0-10 should work now |
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.
The text was updated successfully, but these errors were encountered: