tunnel can not connect to even though the tunnel status is running

microsoft / vscode-remote-release

Visual Studio Code Remote Development: Open any folder in WSL, in a Docker container, or on a remote machine using SSH and take advantage of VS Code's full feature set.

https://aka.ms/vscode-remote

Other

3.69k stars 297 forks source link

tunnel can not connect to even though the tunnel status is running #9757

Open habaohaba opened 7 months ago

habaohaba commented 7 months ago

VSCode Version: 1.88.0 (Universal)
Local OS Version: mac os 14.0 (23A344)
Remote OS Version: windows 11
Remote Extension/Connection Type: tunnel

Logs:

Steps to Reproduce:

open tunnel access on remote machine, connect to tunnel in local machine successfully
next day, when i reopen visual code in local machine, it just can not connect to remote machine, even though the tunnel status is running

connor4312 commented 7 months ago

Can you share the --verbose logs from the tunnel's host side as well?

habaohaba commented 7 months ago

How can i get a more verbose log in host side, it seems like there is no cli command to show log. This is the output in my host side tunnel service panel in visual code.

connor4312 commented 7 months ago

The CLI argument is --verbose, so code tunnel --verbose

habaohaba commented 7 months ago

connor4312 commented 7 months ago

It looks like your credential expired or was invalidated, you may need to run code tunnel user login again

habaohaba commented 7 months ago

Today, I restart the tunnel and it can only get started in visual code gui mode but not in cli way. I connect to this reopen tunnel and work a while, but suddenly it crash and the status panel in remote explorer say it is offline which I have no idea why. To be honest, visual code tunnel feature is such a unstable functionality for me, I basically need to restart it everyday and it still accidentally crash sometime.