A: When you open an issue in the support site for a problem with the flexVDI Desktop Client, always attach the log file of the session where the problem happened, and include the approximate date and time of the problem in the issue's message. The flexVDI Desktop Client writes all log messages to a file in the following path:
The amount of information that is logged depends on the log-level configuration option. Always use the following logging configuration to generate the log file that you attach to the issue:
The support team may request you a different configuration if more information is needed.
A: The connections between flexVDI Client and the flexVDI Hosts that serve the virtual desktops are encapsulated in websockets that use https. In the datacenter, it is common that these connections go through a reverse web proxy that can drop inactive connections. For instance, a nginx web proxy with default configuration closes connections that have not had traffic for more than 60 seconds. Firewalls can exhibit the same behavior.
If this is your case, you can configure your network infrastructure to stop dropping these connections.
Alternatively, you can configure flexvdi-gateway to periodically generate network traffic, avoiding the detection of inactivity, performing the following steps:
In every host executing flexvdi-gateway, edit file /etc/flexvdi/flexvdi-gateway.conf adding a line (beween the other options) with the following content to send a packet every 15 seconds:
Then restart the flexvdi-gateway with:
service flexvdi-gateway restart
The restart will drop the connections being served by the flexvdi-gateway, but does not affect the virtual machines.