Unable to find server after inactivity – 2.2.14
Hello, after upgrading to 2.2.14 on my spacedesk server machine, the viewer machine is unable to connect to the server machine after 5-10 minutes of inactivity. To be able to connect to the server, I have to first move the mouse or press a key on the server machine, then it appears as an option for the viewer machine to connect to. This behavior only started with the update to 2.2.14.
If this is intended behavior, could a setting be added to disable it or set a different time for the driver to go to sleep?
Hi @c-dot-gonz,
For further analysis of the issue, please send us the logs of your Primary PC by opening the spacedesk Driver console as administrator and clicking on Diagnostics then follow the steps below:
1. Download the DebugView.
2. Check the Diagnostic Collection box.
3. Reproduce the issue e.g. by connecting the spacedesk Viewer app.
4. Uncheck the Diagnostic Collection box.
5. Click “Save All Information” button (this might take a while to finish).
6. Compress/Zip the folder which contains the logs, then attach to your next reply to this post. If the folder exceeds 512kb, you may upload it to Dropbox or Google Drive then include the download link on your next reply.
Also, can you specify which viewer(s) you’re using where you encountered the issue?
Thank you.
Hello, attached are the requested logs.
The viewer I am using is v0.0.38.0 on Windows 10.
The driver I am using is 2.2.14 on Windows 11.
After about 5 minutes of inactivity, my computer automatically locks and turns off the display. When this happens, the Spacedesk server disconnects and it cannot be reconnected without going to the server and pressing a key or moving the mouse. Before installing 2.2.14, the server was always available to connect to, even after hours of inactivity.
Hochgeladene Dateien:- Du musst dich anmelden um auf Uploads zugreifen zu können.
Hi @c-dot-gonz,
To clarify, which PC sleeps after 5 minutes of inactivity, the Primary PC or the viewer?
The Primary PC is what locks and turns off the displays after 5 minutes of inactivity.
Hi @c-dot-gonz,
We analyzed your logs and there seems nothing wrong.
In the logs we saw Windows Primary machine going to sleep and Viewer reconnecting after wakeup.
This is the expected behaviour:
1. Windows Primary Machine goes to sleep
2. Windows Viewer goes to state „Disconnected Reconnecting“
3. Windows Primary Machine wakes up
4. Viewer automatically reconnects (because still in State „Disconnected Reconnecting“)
We are not sure if we understand you correctly:
a.) Did you observe problems with steps 1-4?
b.) Do you request different implementation of steps 1-4?
c.) Do you try to discuss other topic, different than steps 1-4?
The problem is between steps 2 and 3. Before 2.2.14, the Primary Machine would still appear in the Viewer’s server list and I could connect to it there without having to physically go to the Primary Machine and wake it up. Now, the Viewer only shows „Cannot detect Server!“ until I go to the Primary Machine and wake it up.