xpra icon
Bug tracker and wiki

This bug tracker and wiki are being discontinued
please use https://github.com/Xpra-org/xpra instead.


Opened 8 months ago

Closed 7 months ago

Last modified 6 months ago

#2934 closed defect (needinfo)

Lost connection

Reported by: louis-mulder Owned by: louis-mulder
Priority: major Milestone: 4.1
Component: android Version: 4.0.x
Keywords: Cc:

Description

Hi All

For some time I am running Xpra v3 in a Kubernetes cluster. The Xpra proxy is running as ingress-controller and creates or ee-connect the Xpra pods. I had no lost-connections with this version however I am testing V4 on the same way. When I switch the speaker to off it seemed to more stable but it has not the same stability as under V3. A v4 client to a v3 xpra-proxy and session has no problems so far I now can see.
Any ideas ????

Regards Louis

Change History (4)

comment:1 Changed 8 months ago by Antoine Martin

Owner: changed from Antoine Martin to louis-mulder

Please specify the exact versions used, OS, etc

Any ideas ????

What do the proxy logs show?

comment:2 Changed 8 months ago by Antoine Martin

This may have been caused by r28042, please try the latest version of the HTML5 client, which you can find in svn or here: https://xpra.org/html5.

If you still have problems, please paste the javascript console log and the server log.

comment:3 Changed 7 months ago by Antoine Martin

Resolution: needinfo
Status: newclosed

comment:4 Changed 6 months ago by migration script

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

Note: See TracTickets for help on using tickets.