Stuck on Opening Remote - Invoking resolveAuthority(wsl)

[AnimeshRy]

• VSCode Version: 1.73.0
• Local OS Version: Windown 21H2 22000.978
• Remote OS Version: Ubuntu 20.04
• Remote Extension/Connection Type: WSL
• Logs:

2022-11-08 12:30:36.884 [info] [attempt 1] Invoking resolveAuthority(wsl)
2022-11-08 12:30:48.804 [warning] Settings pattern "keyboard.*" doesn't match any settings
2022-11-08 12:30:48.805 [warning] SettingsEditor2: Settings not included in settingsLayout.ts: application.experimental.rendererProfiling

Steps to Reproduce:

1. Just try opening any folder with code . and it will keep on going for opening remote.

This started happening last night and since yesterday, has been the same. I'm not sure what updated but I've tried removing WSL extension and installing older version. Also tried changing VScode versions. Still this has been happening and blocking my work.

I've tried most of the solutions on issues except reinstalling windows which I'm not gonna do.

The weird part is the folders in WSL do open up when you open them with the WSL extension removed the terminal doesn't

Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes

[AnimeshRy]

[chenyukang]

Get the same issue exactly!!
Restart WSL and even PC, reinstall VSCode also don't resolve this issue.

[chenyukang]

Logs in Main:

2022-11-09 14:52:26.018 [warning] Settings pattern "keyboard.*" doesn't match any settings
2022-11-09 14:52:26.018 [warning] SettingsEditor2: Settings not included in settingsLayout.ts: application.experimental.rendererProfiling
2022-11-09 14:52:26.965 [warning] Settings pattern "keyboard.*" doesn't match any settings
2022-11-09 14:52:27.041 [critical] Extension 'ms-toolsai.jupyter' wants API proposal 'notebookDebugOptions' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
2022-11-09 14:52:27.060 [info] Ignoring configured affinity for 'vscode.git' because the extension is unknown or cannot execute for extension host kind: LocalWebWorker.
2022-11-09 14:52:27.061 [info] Ignoring configured affinity for 'vscode.git-base' because the extension is unknown or cannot execute for extension host kind: LocalWebWorker.
2022-11-09 14:52:27.287 [info] [attempt 1] Invoking resolveAuthority(wsl)
2022-11-09 14:52:29.123 [info] [attempt 1] resolveAuthority(wsl) returned '127.0.0.1:62404' after 1837 ms

[chenyukang]

Logs in Remote Tunnel:

2022-11-09 14:15:17.905 [error] Missing 'tunnelApplicationConfig' or 'tunnelApplicationName' in product.json. Remote tunneling is not available.
2022-11-09 14:17:56.363 [error] Missing 'tunnelApplicationConfig' or 'tunnelApplicationName' in product.json. Remote tunneling is not available.
2022-11-09 14:19:18.969 [error] Missing 'tunnelApplicationConfig' or 'tunnelApplicationName' in product.json. Remote tunneling is not available.
2022-11-09 14:22:54.176 [error] Missing 'tunnelApplicationConfig' or 'tunnelApplicationName' in product.json. Remote tunneling is not available.
2022-11-09 14:23:08.125 [error] Missing 'tunnelApplicationConfig' or 'tunnelApplicationName' in product.json. Remote tunneling is not available.
2022-11-09 14:34:38.992 [error] Missing 'tunnelApplicationConfig' or 'tunnelApplicationName' in product.json. Remote tunneling is not available.
2022-11-09 14:35:57.490 [error] Missing 'tunnelApplicationConfig' or 'tunnelApplicationName' in product.json. Remote tunneling is not available.
2022-11-09 14:41:50.708 [error] Missing 'tunnelApplicationConfig' or 'tunnelApplicationName' in product.json. Remote tunneling is not available.
2022-11-09 14:49:00.169 [error] Missing 'tunnelApplicationConfig' or 'tunnelApplicationName' in product.json. Remote tunneling is not available.
2022-11-09 14:52:26.342 [error] Missing 'tunnelApplicationConfig' or 'tunnelApplicationName' in product.json. Remote tunneling is not available.

[AnimeshRy]

@chenyukang Same logs, Yep I think update to the extension probably caused the issue

[chenyukang]

@chenyukang Same logs, Yep I think update to the extension probably caused the issue

I think it's caused by new version of VSCode, I just updated to new version today.

[chenyukang]

But another of my PC don't have this issue.

[Jed-Salmon]

I was having this problem and resolved it by deleting bin and data from \home\<user>\.vscode-server. Then I uninstalled and reinstalled the VS-Code Remote Developer Pack extension.

[chenyukang]

@Jed-Salmon You are my hero!
I also resolved this issue by deleting bin and data from \home\<user>\.vscode-server, without reinstall the extension.

[Jed-Salmon]

@Jed-Salmon You are my hero!
I also resolved this issue by deleting bin and data from \home\<user>\.vscode-server, without reinstall the extension.

That's great to hear, glad that did the trick 🙌

[bamurtaugh]

Thanks all for reporting! Has anyone experienced this issue since finding the workaround a few weeks ago?

[slcbear]

tl;dr I experienced an issue that seems identical to this one. By deleting extension files manually and force-killing some weirdly persistent WSL sessions, I was able to reinstall extensions and now VSCode seems to work from WSL sessions normally, although the Remote Tunnel tab is still logging errors saying "Remote tunneling not available." Also, I'm a huge fan, so I leapt at the opportunity to respond to that "info-needed" tag, and I hope this is useful.

Long version follows:
I experienced it this morning: One moment it was working normally, and the next, when I typed code . in a WSL folder, VSCode would open, but would sit there slack-jawed and drooling saying, "Opening remote." The output in the Log (Remote Tunnel) tab has several iterations of the following:
2022-11-29 03:21:29.904 [error] Missing 'tunnelApplicationConfig' or 'tunnelApplicationName' in product.json. Remote tunneling is not available.
I deleted bin and data from ~/<username>/.vscode-server, which had the satisfying effect of causing it to automatically be reinstalled on the occasion of the following launch. However, even after that, it still remained in its slack-jawed state, and would not allow me to uninstall the WSL extension or the Remote Development extension pack (i.e., clicking on the "Uninstall" button had no effect), until I reopened it from the regular Windows filesystem.
Then I was able to uninstall all extensions related to WSL, and the Remote Development extension pack, close the app, and reopen it from a WSL session in hopes of reinstalling the extension pack.
Those hopes were thwarted by a file-permission issue on the Windows filesystem side of things, and it was unable to reinstall the extensions properly. wsl --shutdown simply would not terminate and had no effect. So I forcibly killed all process that seemed related to WSL; then, in an elevated Terminal session, I was able to delete several ms-vscode-remote* directories from within $env:USERPROFILE/.vscode/extensions/.
This took care of the file permissions issue, so I was able to reinstall the excellent Remote Development extension pack.
At this point, I am able to code . from a WSL directory and open VSCode, which seems to function normally.
However, I was surprised to see that the messages saying Missing 'tunnelApplicationConfig' or 'tunnelApplicationName' in product.json. Remote tunneling is not available are continuing unabated in the Remote Tunnel log.
On the other hand, I doubt I would have noticed that had I not been looking for clues regarding the original WSL problem, so I'm not very upset about it; I think it must be describing some setting in a config file that it wants me to look at, and I will probably try to figure out what it wants. Eventually.
Anyway, this is a response to the "info-needed" tag; otherwise I would not have darkened your door; I hope it's enough info; please do ask if you want any more.
I'm a huge fan of both WSL and VSCode, and I imagine its developers must get a great deal of satisfaction being able to work on a project that is both overwhelmingly popular and almost perversely useful.
Cheers!

[bamurtaugh]

Thank you for the details and kind words @slcbear!

cc @aeschli and @connor4312 for the combination of WSL issue and Remote Tunnels prompting.

[connor4312]

The "Remote Tunnel" output channel is not related to WSL, and that message is expected in the current stable release which does not include tunneling functionality.

[slcbear]

The "Remote Tunnel" output channel is not related to WSL, and that message is expected in the current stable release which does not include tunneling functionality.

Thank you for taking the time to let me know, connor4312. Obviously, I jumped in before I knew what I was doing. I'm grateful that you clued me in instead of just letting me continue on like a madman. Output channels, eh? Who knew? Sorry for the disruption, Cheers!

[TonyTheFerg]

@chenyukang

I also resolved this issue by deleting bin and data from \home<user>.vscode-server, without reinstall the extension.

So did you delete those entire folders?
Also, do they get recreated when you load vscode again through code .?

I recently encountered this by moving to a new computer, but i migrated my vscode settings through the settings sync feature.

[mdpung]

This is the method that helped me fix the issue.
It seemed to have been an issue with WSL and not VSCode.

1. I still uninstalled the extesion in VSCode
2. Verify WSL works alone. Go to Command Prompt and type wsl
3. If nothing happens and you get no response, follow the instructions here to disable and re-enable the "Control Flow Guard" security settings on Windows.
4. Reboot computer
5. Open VSCode and reinstall WSL extenstion
6. Things working again...