Xpra: Ticket #2102: sharing, "new connection from same uuid"

I'm trying to share a connection and I'm getting the error message, "new connection from the same uuid". I'm using "ssh".

How do I make this work? I have sharing enabled on the both the client and the server.

If it is not supported with ssh, I offer to update the man page to note this.

Fri, 11 Jan 2019 04:37:04 GMT - Antoine Martin: owner changed

This is meant to prevent the same user from connecting more than once from the same machine. See get_user_uuid() ie: if the connection is dead, the user might re-connect before the server has had a chance to drop the old connection and we don't want to use sharing in this case (it limits some features).

You can workaround it by specifying XPRA_USER_UUID=whatever xpra attach.

Are you connecting from the same machine?

Sun, 13 Jan 2019 13:58:44 GMT - Nathan Hallquist:

I'm connecting from behind a NAT to a proxy to the server. I'm going to guess either the NAT or the proxy alone would be enough to confuse the server into thinking that both sessions are from the same computer.

I'm going to look at how that UUID is calculated and think about how to make sure that both of my clients get a unique UUID from behind a proxy or NAT.

Tue, 15 Jan 2019 17:56:13 GMT - Nathan Hallquist:

The two items (HOME and machine_id) going into UUID on windows are empty when run from command prompt in windows. I will fix.

Tue, 15 Jan 2019 21:50:49 GMT - Nathan Hallquist:

I found that in win32 get_machine_id was returning blank as was HOME. I believe I have fixed it in r21372. I'm a little new to this. I am requesting that somebody more expert than I inspects the commit.

With this patch I have been able to get screen sharing to work, before this patch I could not get it work (as all my clients are windows).

Wed, 16 Jan 2019 04:20:00 GMT - Antoine Martin: status changed; resolution set

Looks good, r21373 just simplifies it a bit.

Sat, 23 Jan 2021 05:42:16 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2102