Cannnot reconnect to WSL after Windows resumes

[chrisdias]

Version: 1.46.0-insider (user setup)
Commit: 9f89da69154ac6c99dfa7c82986e2df95b7bbe0b
Date: 2020-06-08T22:10:54.220Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19041

I think this is new behavior? If I have an instance of VS Code open on a Ubuntu instance and the computer goes to sleep, when i log back in again I get a reconnect prompt:

To repro

• ubuntu image on wsl
• open a folder on linux
• let the computer go to sleep
• wake, log back into comuter
• result: Reconnect Dialog

[andres-pcg]

This happens a lot to me.

[aeschli]

@chrisdias Can you run powercfg /a and let me know what sleep states are available on your machine?

[chrisdias]

This no longer happens for me all the time, only occasionally, but I can't identify exactly when.

d:\src>powercfg /a
The following sleep states are available on this system:
    Standby (S0 Low Power Idle) Network Connected
    Hibernate
    Fast Startup

The following sleep states are not available on this system:
    Standby (S1)
        The system firmware does not support this standby state.
        This standby state is disabled when S0 low power idle is supported.

    Standby (S2)
        The system firmware does not support this standby state.
        This standby state is disabled when S0 low power idle is supported.

    Standby (S3)
        The system firmware does not support this standby state.
        This standby state is disabled when S0 low power idle is supported.

    Hybrid Sleep
        Standby (S3) is not available.
        The hypervisor does not support this standby state.

[tristanbrown]

This has been happening to me too, starting sometime in 2020. When Windows resumes, I get the "Cannot reconnect. Please reload window" message. I used to be able to just click the "reload window" button, and everything would be fine after that. But starting about a month ago, after the window reloads, a message pops up giving a 5 second countdown before it tries to reconnect again. If I let it try to reconnect in that way, it always fails and gives the "Cannot reconnect. Please reload window" message again. The only way to break the cycle is to manually click the "reload window" button before the 5 second countdown expires. At that point it connects properly.

This has become incredibly annoying.

[ablankenship10]

I have this issue a lot after a windows reinstall that wasn't happening my first time using it. Before I had tweaked WSL with a few modifications to how the network was connected to host and a different systemd script I think which may have helped, but those were hacks at the time and now there I think was more official WSL support for those things that I didn't use random git users scripts to make those work.

Anyway, I don't only get this popup when it wont reconnect. Sometimes it just shows me a notification in the bottom right that it couldn't open my file in the remote. Using the bottom left button on the toolbar that says (WSL: Ubuntu) fails to reconnect as well. It seems as though this attempt to reconnect is failing to do the same flow as the initial connect for some reason.

[rekire]

I have the same problem, however I think this started when I changed my IP range of my home network. This might trigger this issue.

[aurisnoctis]

This is indeed very annoying. Pressing the "Reload Window" button usually works, but

• the terminal gets reloaded too and is then empty (past commands are in .bash_history, but I like to see what I did just before in that terminal)
• while the modal/banner is up, I can't interact with the window - neither minimize it nor drag it to another desktop so it's blocking my other work. I can only bring up another window in front of it, but I can't see/use my desktop for instance. When I hit Reload Window, the past terminal commands are gone ... 😞

I am on my employer's laptop with Microsoft Windows 10 Enterprise LTSC.

Edit: I am not using WSL, but connect to a Linux desktop via ssh.
Edit 2: It would help if the ssh connection could be reestablished by reconnecting the window again without reloading it. At the moment this doesn't work using the ssh interactions in the bottom left corner and trying to connect in the same window. Only reload helps with the contents of the terminal gone.

[aeschli]

Thanks @aurisnoctis. SSH and WSL are quite different regarding the way reconnection works.
This issue is about WSL. A while back we came up with a new connection method that fixed the reconnection issues that we suffered for a long time.

Therefore I'm closing this issue as fixed.

[aurisnoctis]

OK, is the "Reconnect. Please reload the window"-Issue also fixed for users connecting to a Linux machine via ssh? All issues about that seem to be closed but it's not solved (for me at least). Thank you for pointing me somewhere re my description above - either documentation or related issues are welcome. 🙏

[aeschli]

@aurisnoctis If there's no open issue about reconnect in SSH, please file a new issue that describes your setup and your steps.