On 17/07/2019 18:15, Evan Sarmiento via shifter-users wrote: > Hi, > > Is there a way to configure the HTML5 client to allow for socket timeouts of > greater than it's default value? It depends which timeout is being triggered. What is the server log saying? You may want to enable the HTML5 client's "network" debug logging to get more details.
> I am encountering sudden websocket disconnects every so often, which > automatically reloads / reconnects - works fine. Is there some configurable > value that would persist in attempting to maintain that connection on the > client side? Assuming that the disconnection is from ping timeouts, you can try setting: XPRA_PING_TIMEOUT=300 xpra start .. But the default is already 60 (seconds), and if ping packets take over a minute to do the roundtrip, then re-connecting is a reasonable thing to do to try to recover. Cheers, Antoine > Thanks > Evan > > _______________________________________________ > shifter-users mailing list > shifter-users@lists.devloop.org.uk > https://lists.devloop.org.uk/mailman/listinfo/shifter-users > _______________________________________________ shifter-users mailing list shifter-users@lists.devloop.org.uk https://lists.devloop.org.uk/mailman/listinfo/shifter-users
