You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
xpra 5.0-r32148-1 cannot connect via ssh anymore.
Downgrading to version 5.0-r32078-1 fixes the issue for me, so the change must be a regeression between these two version.
xpra probably confuses the local and the remote username.
System Information (please complete the following information):
Server OS: Debian stable
Client OS: Debian testing
Xpra Server Version 4.4-r0-1
Xpra Client Version 5.0-r32148-1
Additional context
2022-10-21 16:02:21,892 Error: SSH connection to the xpra server failed
2022-10-21 16:02:21,892 check your username, hostname, display number, firewall, etc
2022-10-21 16:02:21,892 for server: ssh://remoteuser@server:10
2022-10-21 16:02:21,893 the command line used was:
2022-10-21 16:02:21,893 /usr/bin/ssh -l localuser -p 10 -T server
The command line should contain -l remoteuser as parameter or remoteuser@server as connection string.
The text was updated successfully, but these errors were encountered:
FYI: the syntax ssh:remoteuser@server:10 is deprecated and may be removed in the future.
Please switch to a more standard URL syntax (#3599): ssh://user@host:port/
That's, that was a fast fix. I'll update when there are new debian packages. If the error persists, I'll reopen, otherwise you can assume it works for me again.
Describe the bug
xpra
5.0-r32148-1
cannot connect via ssh anymore.Downgrading to version
5.0-r32078-1
fixes the issue for me, so the change must be a regeression between these two version.xpra probably confuses the local and the remote username.
To Reproduce
Steps to reproduce the behavior:
server command
remoteuser@remotehost$ xpra start :10
client command
localuser@localhost$ xpra attach --ssh=/usr/bin/ssh ssh:remoteuser@server:10
specific action to trigger the bug
Trying to connect with the client
System Information (please complete the following information):
Additional context
The command line should contain
-l remoteuser
as parameter orremoteuser@server
as connection string.The text was updated successfully, but these errors were encountered: