Xpra Client not reconnecting after Update to Version 12 about xpra HOT 7 OPEN

The message connection failed, invalid address? comes from:
https://github.com/Xpra-org/xpra-html5/blob/aad8e6c116089180eee60f200b11e8301a5cd915/html5/js/Client.js#L2431-L2435
And is called from only two places:

• a close packet is received:
  https://github.com/Xpra-org/xpra-html5/blob/aad8e6c116089180eee60f200b11e8301a5cd915/html5/js/Client.js#L2470-L2479
• a disconnect packet is received:
  https://github.com/Xpra-org/xpra-html5/blob/aad8e6c116089180eee60f200b11e8301a5cd915/html5/js/Client.js#L2504-L2510

In both cases, there should be a message in your javascript console preceding this - you may need to enable main debug logging to see the one from the disconnect handler.
If the authentication went as far as the server, there should also be a message in your server log (add -d auth there to see more details).

It is possible that the problem comes from the authentication and only shows up as a more general connection failure.

Issues that may be (distantly?) related:
Xpra-org/xpra-html5#278
Xpra-org/xpra-html5#262
Xpra-org/xpra-html5#260
And this one has caused us pain a number of times:
Xpra-org/xpra-html5#292

from xpra.

Can you reproduce this with the 5.x LTS branch? (this should narrow things down somewhat)
When I tested with a simple:

xpra start --bind-tcp=0.0.0.0:10000,auth=sys --no-daemon  --start=xterm :6

Closed the tab in Chrome, waited a few seconds and then restored it.
The automatic re-connection failed to prompt me for a password and I was sent back to the connect dialog. But clicking connect from there worked as expected.
I am moving this issue to: Xpra-org/xpra-html5#308

Is your issue the same?
Does the bug occur if you just open the URL again, without restoring the tab?

from xpra.

Some findings from today:

• I can not reproduce the error with Version 5.0.8-r0-1 (same Client Version 12)
• I'm not using Xpra for Authentication but an OAuth2 Proxy
• The issue differs from https://github.com/Xpra-org/xpra-html5/issues/308, the bug also occurs when I open the URL directly or Reload the Page.

from xpra.

I don't think that it will fix things, but worth a try:
https://github.com/Xpra-org/xpra-html5/releases/tag/v13

from xpra.

Updating to Xpra 6.1-r35816-1 and Client Version 13 did not have any effect on the issue. But it's interesting that 5.0.8-r0-1 works fine.

from xpra.