The host '...' was not found in the list of allowed hosts. Do you want to open it anyway?

Question

Since updating to Visual Studio Code v. 1.78.2 this warning has been popping up. It is appearing because the folder I am working out of is using a UNC path. I rely on this path.

The VS help page states:

configure the host to be allowed via the security.allowedUNCHosts setting (for example add server-a when you open a path such as \server-a\path)

Where is this setting?

score 18 · Accepted Answer · answered May 12 '23 at 15:08

18

Go to preferences Ctrl + , and search for 'allowedUNCHosts'. You'll find it under Security.

answered May 12 '23 at 15:08

Sean O

2,276
1
21
24

Thanks. In the settings I added the UNC path ```\\gisfile``` and restarted. Same warning. – Pfalbaum May 12 '23 at 15:23
2

Try adding just the server name (sans slashes). – Sean O May 12 '23 at 15:24
4

It worked without the slashes (i.e. ```gisfile```). No more warning. – Pfalbaum May 12 '23 at 15:26
same for me: for wsl.localhost – jrdunson May 19 '23 at 13:21
not worked for me with `wsl.localhost`, `wsl` and `localhost` as separated entries. When I drag a file from WSL folder to open with vscode, the warning appears. When I click to open with vscode by window's context it works, but open a separated VSCode instance. – Giovan Cruz May 23 '23 at 14:10
@GiovanCruz Have you tried `wsl$`, per @wrrnlim above? – Sean O May 23 '23 at 17:36
@SeanO @wrrnlim thnks, replacing by `wsl$` worked – Giovan Cruz May 24 '23 at 13:21
For me, adding the WSL extension in the local VScode solved in. – Jelmer Mulder Jun 14 '23 at 19:16

Daniela Wuerich · Answer 2 · 2023-05-17T16:35:44.510

3

To those looking for a solution when using \\wsl$, adding wsl.localhost to the allowedUNCHHosts option worked for me. This source indicates that it can be changed in JSON settings as well.

edited May 17 '23 at 16:35

answered May 17 '23 at 16:35

Daniela Wuerich

31
3

Adding `wsl$` to allowedUNCHosts fixed it for me – wrrnlim May 22 '23 at 18:27
1

In my case, adding wsl.localhost to the allowedUNCHosts worked as well – Kristina May 26 '23 at 05:43
This worked for me too. VS Code 1.78.2 running on Windows 11 and accessing WSL hosted Debian 11. Thank you @Daniela. – Energetic Pixels May 30 '23 at 21:08
Adding wsl.localhost to security.allowedUNCHosts in the json settings file worked for me, this should be the accepted answer imo – reggaeguitar Jun 05 '23 at 19:11

score 1 · Answer 3 · answered Jun 11 '23 at 18:47

The May 2023 VSCode 1.79 can also update that setting for you through a confirmation dialog.

See "Windows UNC host allowlist improvements":

As part of an important security fix, VS Code introduced an allowlist for UNC hosts.
In this milestone, we addressed many of the usability problems reported by Windows users when they have UNC paths in their day-to-day work with VS Code.

Dialog improvements

The confirmation dialog to allow a UNC host on startup now updates the security.allowedUNCHosts setting and adds the host when you select the checkbox.

In addition, clicking the Learn More button no longer closes the dialog.

New security.restrictUNCAccess setting

A new setting security.restrictUNCAccess lets you disable the UNC allowlist for hosts and restore the behavior to how it was before this security fix.

We strongly advise against changing this setting, as it makes your system vulnerable again to the Information Disclosure Vulnerability.

score 0 · Answer 4 · answered May 23 '23 at 04:19

0

Map your WSL host to your network (by right clicking on the WSL host in windows explorer and add a drive letter i.e Z), after that you can add any folder in your WSL to your VSCode workspace

answered May 23 '23 at 04:19

Erwin Kurnia

27
2

This does work for getting rid of the message however it also means that VSCode won't open in a WSL window with all the advantages that come with that – ChrisM May 25 '23 at 03:16

The host '...' was not found in the list of allowed hosts. Do you want to open it anyway?

4 Answers4

Dialog improvements

New `security.restrictUNCAccess` setting

Linked

The host '...' was not found in the list of allowed hosts. Do you want to open it anyway?

4 Answers4

Dialog improvements

New security.restrictUNCAccess setting

Linked

New `security.restrictUNCAccess` setting