starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 07:54:35 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows terminal tab freezes when ssh is disconnected within WSL #13907

New Issue
Closed
opened 2026-01-31 03:55:26 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 03:55:26 +00:00
Owner
Copy Link

Originally created by @ismailhkose on GitHub (May 25, 2021).

Windows Terminal version (or Windows build number)

10.0.19043.985, 1.7.1033.0

Other Software

Windows 10 21H1 (OS Build 19043.985)
Windows Terminal Version: 1.7.1033.0

Cygwin64
Cygwin mintty 3.4.2 (x86_64-pc-cygwin) [Windows 19043]
OpenSSH_8.4p1, OpenSSL 1.1.1f 31 Mar 2020

WSL
OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017
Linux -T480 5.4.72-microsoft-standard-WSL2 #1 SMP Wed Oct 28 23:40:43 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Ubuntu Workstation
OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017
tmux 3.2

Steps to reproduce

1 - VPN is connected to corporate network.
2 - Open Windows Terminal and start Ubuntu 18.04 WSL2
3 - SSH to remote machine within WSL2. I ssh to my Ubuntu 18.04 workstation in corporate network.
4 - Create a new tmux session session. tmux new -s test
5 - Disconnect VPN (Uncheck connect automatically)

At this step, terminal freeze should be reproduced, and it should not be responding to any keys, which is a bug 1. I have to close the terminal tab, and open another one to continue.

Expected Behavior

1- When VPN is disconnected, and ssh should be disconnected within the terminal as Cygwin does. However, Windows terminal gets stuck though.

Actual Behavior

1 - Windows Terminal has a blinking cursor, however; it doesn't response to any key ctrl+c or any other keys.
2 - It doesn't seem to try disconnects after connection timeout. Terminal hangs. The only way is to close the terminal tab.

Originally created by @ismailhkose on GitHub (May 25, 2021). ### Windows Terminal version (or Windows build number) 10.0.19043.985, 1.7.1033.0 ### Other Software Windows 10 21H1 (OS Build 19043.985) Windows Terminal Version: 1.7.1033.0 **Cygwin64** Cygwin mintty 3.4.2 (x86_64-pc-cygwin) [Windows 19043] OpenSSH_8.4p1, OpenSSL 1.1.1f 31 Mar 2020 **WSL** OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 Linux <USERNAME>-T480 5.4.72-microsoft-standard-WSL2 #1 SMP Wed Oct 28 23:40:43 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux **Ubuntu Workstation** OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 tmux 3.2 ### Steps to reproduce 1 - VPN is connected to corporate network. 2 - Open Windows Terminal and start Ubuntu 18.04 WSL2 3 - SSH to remote machine within WSL2. I ssh to my Ubuntu 18.04 workstation in corporate network. 4 - Create a new tmux session session. tmux new -s test 5 - Disconnect VPN (Uncheck connect automatically) At this step, terminal freeze should be reproduced, and it should not be responding to any keys, which is a bug 1. I have to close the terminal tab, and open another one to continue. ### Expected Behavior 1- When VPN is disconnected, and ssh should be disconnected within the terminal as Cygwin does. However, Windows terminal gets stuck though. ### Actual Behavior 1 - Windows Terminal has a blinking cursor, however; it doesn't response to any key ctrl+c or any other keys. 2 - It doesn't seem to try disconnects after connection timeout. Terminal hangs. The only way is to close the terminal tab.
claunia added the Resolution-By-DesignNeeds-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 03:55:26 +00:00
claunia commented 2026-01-31 03:55:28 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 25, 2021):

Thanks for filing this! Terminal doesn't actually control what happens here -- its job is to get characters out of SSH on to the screen, and from your keyboard back into SSH... or whatever application is connected. How a process handles the socket dropping, or SIGINT (from Ctrl+C), or user input is up to that process, at the end of the day.

When you get it into this state, if you press the following:

ENTER ~ .

what happens?

@DHowett commented on GitHub (May 25, 2021): Thanks for filing this! Terminal doesn't actually control what happens here -- its job is to get characters out of SSH on to the screen, and from your keyboard back into SSH... or whatever application is connected. How a process handles the socket dropping, or SIGINT (from <kbd>Ctrl+C</kbd>), or user input is up to that process, at the end of the day. When you get it into this state, if you press the following: <kbd>ENTER</kbd> <kbd>~</kbd> <kbd>.</kbd> what happens?
claunia commented 2026-01-31 03:55:28 +00:00
Author
Owner
Copy Link

@ismailhkose commented on GitHub (May 26, 2021):

I get the following message.
Connection to <IP> closed.

@ismailhkose commented on GitHub (May 26, 2021): I get the following message. ```Connection to <IP> closed.```
claunia commented 2026-01-31 03:55:28 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 26, 2021):

It looks like Terminal is still passing input to the SSH process, as the SSH "session break" key combo continues to work. 😄

At the end of the day... if an application inside Terminal isn't responding normally it's much more likely to be the application's fault rather than Terminal's. You'd probably observe the same behavior if you used wsl inside the console host.

There's a chance, of course, that it's a WSL issue. Given though that it's WSL2, that's also unlikely. Sometimes SSH just thinks it's still connected.

@DHowett commented on GitHub (May 26, 2021): It looks like Terminal is still passing input to the SSH process, as the SSH "session break" key combo continues to work. :smile: At the end of the day... if an application inside Terminal isn't responding normally it's much more likely to be the application's fault rather than Terminal's. You'd probably observe the same behavior if you used wsl inside the console host. There's a chance, of course, that it's a _WSL_ issue. Given though that it's WSL2, that's also unlikely. Sometimes SSH just thinks it's still connected.
claunia commented 2026-01-31 03:55:28 +00:00
Author
Owner
Copy Link

@ismailhkose commented on GitHub (Jun 1, 2021):

I don't get this error when I use Cygwin as a terminal. Please see the openssh and terminal versions in the first message. Any idea?

@ismailhkose commented on GitHub (Jun 1, 2021): I don't get this error when I use Cygwin as a terminal. Please see the openssh and terminal versions in the first message. Any idea?
claunia commented 2026-01-31 03:55:28 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 1, 2021):

The Cygwin runtime handles the "link disappeared while we were using it" state better than what you're seeing in WSL. This is probably because the Cygwin runtime is using Windows sockets natively, whereas WSL is running in a hypervisor with some network forwarding and stuff so it's missing the connection drop event.

If you run WSL outside of Windows Terminal, it's going to behave the same way.

@DHowett commented on GitHub (Jun 1, 2021): The Cygwin runtime handles the "link disappeared while we were using it" state better than what you're seeing in WSL. This is probably because the Cygwin runtime is using Windows sockets natively, whereas WSL is running in a hypervisor with some network forwarding and stuff so it's missing the connection drop event. If you run WSL _outside of Windows Terminal_, it's going to behave the same way.
claunia commented 2026-01-31 03:55:29 +00:00
Author
Owner
Copy Link

@ismailhkose commented on GitHub (Jun 15, 2021):

So, where should I file this bug to?

@ismailhkose commented on GitHub (Jun 15, 2021): So, where should I file this bug to?
claunia commented 2026-01-31 03:55:29 +00:00
Author
Owner
Copy Link

@ismailhkose commented on GitHub (Jun 15, 2021):

I created a networking related issue in WSL, but I am not sure how relevant it is.
https://github.com/microsoft/WSL/issues/7030

@ismailhkose commented on GitHub (Jun 15, 2021): I created a networking related issue in WSL, but I am not sure how relevant it is. https://github.com/microsoft/WSL/issues/7030
claunia commented 2026-01-31 03:55:29 +00:00
Author
Owner
Copy Link

@Petros626 commented on GitHub (Sep 19, 2024):

I did the following, which worked for me (Windows 10 & WSL2):

  1. sudo nano /etc/ssh/ssh_config
  2. Under section Host* add ServerAliveInterval 5 (I guess any value is okay?)
  3. sudo nano /etc/ssh/sshd_config
  4. Near the end of the file search for: ClientAliveInterval 60; TCPKeepAlive yes; ClientAliveCountMax 10000
  5. service ssh restart
  6. ssh nameofmachine@xxx.xxx.xxx.xx
@Petros626 commented on GitHub (Sep 19, 2024): I did the following, which worked for me (Windows 10 & WSL2): 1. `sudo nano /etc/ssh/ssh_config` 2. Under section **Host*** add **ServerAliveInterval 5** (I guess any value is okay?) 3. `sudo nano /etc/ssh/sshd_config` 4. Near the end of the file search for: **ClientAliveInterval 60**; **TCPKeepAlive yes**; **ClientAliveCountMax 10000** 5. `service ssh restart` 6. `ssh nameofmachine@xxx.xxx.xxx.xx`
claunia commented 2026-01-31 03:55:29 +00:00
Author
Owner
Copy Link

@nishaalnaseer commented on GitHub (Nov 18, 2024):

Putting the PC to sleeps breaks SSH connection and i cant get the terminal tab to work again.

Steps to reproduce:

  1. Start SSH connection with terminal
  2. put the pc to sleep
  3. Come back after an hour or two
  4. Login to PC
  5. Unresponsive ssh connection

ENTER ~ . doesnt work.
The connection automatically closes but its taking too long. I think this takes around 15 minutes
Using ctrl D on responsive connection works but not on an unresponsive connection.

Im not on WSL, just windows preview build on terminal
Any tips to fix? should i create a new issue?

I personally think a way to force restart a tab no matter the circumstances would be good. Right now i can close a tab... but doing so would make me lose any split tabs i have open.

@nishaalnaseer commented on GitHub (Nov 18, 2024): Putting the PC to sleeps breaks SSH connection and i cant get the terminal tab to work again. Steps to reproduce: 1. Start SSH connection with terminal 2. put the pc to sleep 3. Come back after an hour or two 4. Login to PC 5. Unresponsive ssh connection ENTER ~ . doesnt work. The connection automatically closes but its taking too long. I think this takes around 15 minutes Using ctrl D on responsive connection works but not on an unresponsive connection. Im not on WSL, just windows preview build on terminal Any tips to fix? should i create a new issue? I personally think a way to force restart a tab no matter the circumstances would be good. Right now i can close a tab... but doing so would make me lose any split tabs i have open.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-By-Design
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13907
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?