microsoft / microsoft/vscode-remote-release

Tunnels stuck in "Starting Remote tunnel" and not installed as service

Open
#11,713 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ssh
Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

Is there an existing issue for this bug?
  • I have searched the existing open issues and found none that apply.
  • If I find any issue of interest that is related or closed, I will included a link to it in this issue.
Required Troubleshooting Steps
  • I have read and performed the troubleshooting steps
  • I have tried both values of the remote.SSH.useLocalServer setting
  • My issue was not covered in the Tips and Tricks linked from the Troubleshooting Wiki.
  • I will include a complete copy of my Remote - SSH logs by running Remote-SSH: Show Log in the command palette or from View > Output in the menu bar
[Optional] Diagnose with Copilot

I did not ask the @remote-ssh participant for help

In step 2 of the troubleshooting wiki, what was the result of running the generated SSH command verbatim outside of VS Code?

I did not try step 2 of the troubleshooting steps

Remote-SSH Log
  • VS Code Version: 1.125.1 (edit, just updated to 1.126.0 and the same issue persists)
  • OS Version: Archlinux fully updated, and also Windows 11

Output from tunnels:

2026-06-23 16:50:02.702 [info] No other tunnel running
2026-06-23 16:50:31.588 [info] Session updated: MYACCOUNT (github) (service=true)
2026-06-23 16:50:31.588 [info] Session token updated: MYACCOUNT (github)
2026-06-23 16:50:31.725 [info] No other tunnel running
2026-06-23 16:50:31.818 [info] Running tunnel CLI

2026-06-23 16:50:31.819 [info] serviceInstall Spawning: /usr/share/code/bin/code-tunnel tunnel service install --accept-server-license-terms --log info --name MYCOMPUTER

2026-06-23 16:50:32.661 [info] *

2026-06-23 16:50:32.661 [info] * Visual Studio Code Server

2026-06-23 16:50:32.661 [info] *

2026-06-23 16:50:32.661 [info] * By using the software, you agree to

2026-06-23 16:50:32.662 [info] * the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and

2026-06-23 16:50:32.662 [info] * the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement).

2026-06-23 16:50:32.662 [info] *

2026-06-23 16:50:32.663 [info] [2026-06-23 15:50:32] info Successfully registered service...

2026-06-23 16:50:32.912 [info] [2026-06-23 15:50:32] info Successfully enabled unit files...

2026-06-23 16:50:32.915 [info] [2026-06-23 15:50:32] info Tunnel service successfully started

2026-06-23 16:50:32.915 [info] Service successfully installed! You can use `code tunnel service log` to monitor it, and `code tunnel service uninstall` to remove it.

2026-06-23 16:50:32.929 [info] serviceInstall exit(836549): + 0 
2026-06-23 16:50:32.929 [info] Running tunnel CLI

2026-06-23 16:50:32.930 [info] tunnel Spawning: /usr/share/code/bin/code-tunnel tunnel --accept-server-license-terms --log info --name MYCOMPUTER --parent-process-id 834012

2026-06-23 16:50:32.951 [info] *

2026-06-23 16:50:32.951 [info] * Visual Studio Code Server

2026-06-23 16:50:32.952 [info] *

2026-06-23 16:50:32.952 [info] * By using the software, you agree to

2026-06-23 16:50:32.952 [info] * the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and

2026-06-23 16:50:32.952 [info] * the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement).

2026-06-23 16:50:32.952 [info] *

2026-06-23 16:50:34.864 [info] 

2026-06-23 16:50:34.864 [info]   Visual Studio Code Tunnel v1.125.1

2026-06-23 16:50:34.864 [info] 

2026-06-23 16:50:34.864 [info]   ➜  Tunnel:   MYCOMPUTER

2026-06-23 16:50:34.865 [info]   ➜  Open:  https://vscode.dev/tunnel/MYCOMPUTER

2026-06-23 16:50:34.865 [info] 

Even though it gets stuck in the pop up I showed, I can connect remotely from another computer. The issue is that if I reboot the host computer, it doesn't create the tunnel automatically and VSCode starts (Vscode is set to start as the computer reboots).

In the host computer, after reboot it says:

[info] Session reset
[info] No other tunnel running

But there are no tunnels at all, and I have to start one, click start as service, but it gets stuck in said steps as I showed before.

Trying with 1.126.0:

2026-06-24 13:45:17.135 [info] No other tunnel running
2026-06-24 13:45:34.255 [info] Session updated: thephet (github) (service=true)
2026-06-24 13:45:34.255 [info] Session token updated: thephet (github)
2026-06-24 13:45:34.383 [info] No other tunnel running
2026-06-24 13:45:34.430 [info] Running tunnel CLI

2026-06-24 13:45:34.430 [info] serviceInstall Spawning: /usr/share/code/bin/code-tunnel tunnel service install --accept-server-license-terms --log info --name desktop

2026-06-24 13:45:35.448 [info] [2026-06-24 12:45:35] info Creating tunnel with the name: desktop

2026-06-24 13:45:39.972 [info] *

2026-06-24 13:45:39.972 [info] * Visual Studio Code Server

2026-06-24 13:45:39.973 [info] *

2026-06-24 13:45:39.973 [info] * By using the software, you agree to

2026-06-24 13:45:39.973 [info] * the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and

2026-06-24 13:45:39.973 [info] * the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement).

2026-06-24 13:45:39.974 [info] *

2026-06-24 13:45:39.974 [info] [2026-06-24 12:45:39] info Successfully registered service...

2026-06-24 13:45:40.165 [info] [2026-06-24 12:45:40] info Successfully enabled unit files...

2026-06-24 13:45:40.166 [info] [2026-06-24 12:45:40] info Tunnel service successfully started

2026-06-24 13:45:40.166 [info] Service successfully installed! You can use `code tunnel service log` to monitor it, and `code tunnel service uninstall` to remove it.

2026-06-24 13:45:40.170 [info] serviceInstall exit(38529): + 0 
2026-06-24 13:45:40.171 [info] Running tunnel CLI

2026-06-24 13:45:40.171 [info] tunnel Spawning: /usr/share/code/bin/code-tunnel tunnel --accept-server-license-terms --log info --name desktop --parent-process-id 38322

2026-06-24 13:45:40.185 [info] *

2026-06-24 13:45:40.185 [info] * Visual Studio Code Server

2026-06-24 13:45:40.185 [info] *

2026-06-24 13:45:40.185 [info] * By using the software, you agree to

2026-06-24 13:45:40.185 [info] * the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and

2026-06-24 13:45:40.185 [info] * the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement).

2026-06-24 13:45:40.185 [info] *

2026-06-24 13:45:41.428 [info] 

2026-06-24 13:45:41.428 [info]   Visual Studio Code Tunnel v1.126.0

2026-06-24 13:45:41.428 [info] 

2026-06-24 13:45:41.428 [info]   ➜  Tunnel:   desktop

2026-06-24 13:45:41.428 [info]   ➜  Open:  https://vscode.dev/tunnel/desktop

2026-06-24 13:45:41.428 [info] 

2026-06-24 13:45:43.162 [info] [2026-06-24 12:45:43] info No agent host supervisor running; starting one in the background
Expected Behavior

the tunnel should be created, the pop up dissappears. If I restart the computer, it automatically creates the tunnel.

Actual Behavior

The connection seems to never be fully done, although I can connect. But if I reboot, it doesn't automatically connect.

Steps To Reproduce

Steps to Reproduce:

  1. Open VSCode
  2. Click on the bottom left "Accounts" icon.
  3. Select "Turn on Remote tunnel access".
  4. Select "Install as service"
  5. Choose your account, in my case GitHub.

After this, it gets stuck on "Starting remote tunnel". The pop up never disappears:

Image
Anything else?

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the flow through Accounts > Turn on Remote tunnel access > Install as service, then inspect the Remote-SSH/tunnel output and the service log after reboot. Done means the “Starting remote tunnel” prompt closes, the service remains active, and the tunnel reconnects automatically after restarting the host.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, linux, vscode
Domain
devtools, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.