entityMap|0|type|IMAGE|mutability|IMMUTABLE|data|imageUrl|https://ask.qcloudimg.com/http-save/actteam/8687ba5250e7c3efb30bda72398378e1.png|imageAlt|blocks|key|547n4|text|将绝对文件路径添加到自定义SSH配置文件(C：\Users{用户名}..。|unstyled|depth|inlineStyleRanges|entityRanges|dkb6r|ssh\config)，我的问题就解决了。​|9amj1|?|atomic|offset|length|deegd|​^0|0|0|0|1|0|0^^$0|$1|$2|3|4|5|6|$7|8|9|-4]]]|A|@$B|C|D|E|2|F|G|S|H|@]|I|@]|6|$]]|$B|J|D|K|2|F|G|T|H|@]|I|@]|6|$]]|$B|L|D|M|2|N|G|U|H|@]|I|@$O|V|P|W|B|X]]|6|$]]|$B|Q|D|R|2|F|G|Y|H|@]|I|@]|6|$]]]]

Add the absolute file path to a custom SSH config file(C:\Users\{USERNAME}\.ssh\config), and my problem is solved.

<a href="https://i.stack.imgur.com/AEpH1.png" rel="noreferrer"><img src="https://i.stack.imgur.com/AEpH1.png" alt="enter image description here"></a>

entityMap|blocks|key|6mc6v|text|对我来说起作用的是删除folder:+C:\Users\MYNAME.ssh中的所有内容，这意味着删除配置文件和已知主机。配置可能是要删除的最重要的配置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

What worked for me was to delete all of the contents of folder: C:\Users\MYNAME.ssh That meant to delete both the config file and known-hosts. The config was probably the most important one to delete.

entityMap|blocks|key|1r3s4|text|我有一个现有的(工作的)配置，当我添加一个新的配置时，也出现了同样的错误。对我起作用的是，我不仅添加了新的主机配置，还注释掉了第一个工作配置。不知道发生了什么，但它起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

Had an existing(working) configuration and had the same error when I added a new one. What worked for me is instead of just adding a new host configuration, I also commented out the first working config. Didn't know what happened but it worked.

entityMap|blocks|key|eifvo|text|如果格式化/重新安装服务器操作系统，但使用与以前相同的IP，则可能会遇到指纹不匹配的情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|bp059|您可能需要删除此文件中的旧指纹:+C:\Users\xxx.ssh\known_主机|2h869|和文件中的旧IP+:+C:\Users\xxx.ssh\config|boqvu|然后再次尝试添加主机。^0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|I|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|J|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|K|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|L|9|@]|A|@]|B|$]]]]

If you format/re-install Server OS, but use same IP as before,
you may encounter fingerprint mismatched.
You may need to delete old fingerprint in this file:
C:\Users\xxx.ssh\known_host
and old IP in the file:
C:\Users\xxx.ssh\config
Then try to add host again.

entityMap|blocks|key|frea2|text|在我的例子中，我有另一个设置：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|btou1|Windows中的Git+bash已配置，我正在使用此工具提供的ssh.exe|unordered-list-item|2fq8g|在VSCode的"Remote+SSH“扩展中，我指定了这个ssh.exe的完整路径|e6e6i|我正在使用多个服务器(通过ProxyJump)|jc2o|错误消息与OP相同，但在日志中记录了找不到ssh配置文件，其中所有文件夹名称已连接在一起(因为它无法识别windows路径分隔符)。|5d065|问题:与VSCode相比，ssh.exe使用了不同的路径约定。ssh.exe正在使用"/c/Users/...“模式，而VSCode正在使用"C:\Users...“模式。|7v4g8|解决方案：|1315m|确保SSH配置位于标准位置(C:\Users\LOGIN.ssh\配置)|ordered-list-item|25aqe|在VSCode的"Remote+SSH“设置中删除配置文件的绝对路径|sqvb|VSCode将仍然能够使用标准路径访问设置，并且ssh.exe配置仍将查看相同的标准路径，因此connexion仍在工作。|6h2o3|注意：|6jkda|只有在连接多个ssh服务器(使用ProxyJump)时才会出现此错误。当只连接到第一个服务器时，@pszrux的解决方案和这个解决方案都适用于我。^0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|10|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|11|9|@]|A|@]|B|$]]|$2|F|4|G|6|E|8|12|9|@]|A|@]|B|$]]|$2|H|4|I|6|E|8|13|9|@]|A|@]|B|$]]|$2|J|4|K|6|E|8|14|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|15|9|@]|A|@]|B|$]]|$2|N|4|O|6|7|8|16|9|@]|A|@]|B|$]]|$2|P|4|Q|6|R|8|17|9|@]|A|@]|B|$]]|$2|S|4|T|6|R|8|18|9|@]|A|@]|B|$]]|$2|U|4|V|6|7|8|19|9|@]|A|@]|B|$]]|$2|W|4|X|6|7|8|1A|9|@]|A|@]|B|$]]|$2|Y|4|Z|6|7|8|1B|9|@]|A|@]|B|$]]]]

In my case I had another setup:
<ul>
<li>Git bash in Windows was configured and I am using the ssh.exe provided by this tool</li>
<li>In the &quot;Remote SSH&quot; extension in VSCode, I specified the full path of this ssh.exe</li>
<li>I am using multiple servers (with ProxyJump)</li>
<li>The error message is the same as the OP but in the logs it was written that the ssh config file was not found, where all the folder names was concatenated (because it did not recognize the windows path separator)</li>
</ul>
Problem: the ssh.exe is using a different path convention thant VSCode. ssh.exe is using the &quot;/c/Users/...&quot; pattern and VSCode is using the &quot;C:\Users...&quot; pattern.
Solution:
<ol>
<li>Make sure the SSH config is at a standard place (C:\Users\LOGIN\.ssh\config)</li>
<li>Remove the absolute path of the config file in the &quot;Remote SSH&quot; settings in VSCode</li>
</ol>
VSCode will still be able to access the settings using the standard path, and the ssh.exe configuration will still look at the same standard path so the connexion is working.
Note:
I have the error only when connecting with multiple ssh servers (using ProxyJump). When connecting only to the first server, the solution of @pszrux and this one are both working for me.

entityMap|blocks|key|6j6fe|text|在我的例子中，这是我所知道的一个令人不快的关键字_windows中的主机(+Windows上的vscode，linux上通过ssh进行远程开发)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|dms02|vscode中返回的错误无法以任何方式解释。^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|E|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|F|9|@]|A|@]|B|$]]]]

In my case this was an offending key in my known_hosts in Windows (vscode on windows, remote developing via ssh on linux).
The error that comes back in vscode is not explaining in any way.

entityMap|blocks|key|b4pvu|text|对我有用的是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|ek3t5|删除ssh配置文件夹，这两个文件夹都在C:\Program+Data\ssh和C:\\.ssh|ordered-list-item|offset|length|style|CODE|9n6bj|在VS+Code中，按F1，选择Remote-SSH:+Connect+to+Host...|febng|不要在提示符中输入任何内容，而是选择%2B+Add+New+SSH+Host..|dphk8|输入完整的ssh命令，包括密钥(对于Windows，您可能需要用双引号将路径括起来)ssh+-i+"C:\path\to\key"+user@host..。(您需要确保密钥具有有限的权限。删除所有继承的权限，并仅将完全控制权授予所有者。)|5iai7|系统将要求您选择将在其中创建新配置文件的文件夹。选择两个选项中的任何一个。|587hd|将出现一个提示，通知已创建新的配置文件。点击connect^0|0|J|J|13|8|0|B|2|G|U|0|I|K|0|16|X|0|0|M|7^^$0|$]|1|@$2|3|4|5|6|7|8|T|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|U|9|@$F|V|G|W|H|I]|$F|X|G|Y|H|I]]|A|@]|B|$]]|$2|J|4|K|6|E|8|Z|9|@$F|10|G|11|H|I]|$F|12|G|13|H|I]]|A|@]|B|$]]|$2|L|4|M|6|E|8|14|9|@$F|15|G|16|H|I]]|A|@]|B|$]]|$2|N|4|O|6|E|8|17|9|@$F|18|G|19|H|I]]|A|@]|B|$]]|$2|P|4|Q|6|E|8|1A|9|@]|A|@]|B|$]]|$2|R|4|S|6|E|8|1B|9|@$F|1C|G|1D|H|I]]|A|@]|B|$]]]]

What worked for me:
<ol>
<li>delete ssh config folder both in <code>C:\Program Data\ssh</code> and <code>C:\&lt;user&gt;\.ssh</code></li>
<li>In VS Code, press <code>F1</code>, choose <code>Remote-SSH: Connect to Host...</code></li>
<li>Do NOT enter anything in the prompt, but instead choose <code>+ Add New SSH Host.. </code></li>
<li>Enter the full ssh command, including the key (in case of Windows,
you may want to enclose the path with double quote mark) <code>ssh -i &quot;C:\path\to\key&quot; user@host</code>. (you need to make sure the key has a limited permission. Remove all inherited permissions, and only give a full control to the owner.)</li>
<li>You will be asked to choose a folder in which a new config file will be created. Choose any of the two options.</li>
<li>There will a prompt notifying that the new config file
has been created. Click <code>connect</code></li>
</ol>

entityMap|0|type|IMAGE|mutability|IMMUTABLE|data|imageUrl|https://ask.qcloudimg.com/http-save/actteam/1e9ae25541dbf567310a78029653630b.png|imageAlt|blocks|key|djget|text|操作系统:+windows+10|unstyled|depth|inlineStyleRanges|entityRanges|71joo|在我的案例中，存在权限问题。在窗口中反复更改继承并没有解决这个问题。最后，这个方法起作用了。|bbo8g|更改存储配置文件的文件夹。来自C:/users/usr/.ssh/config至D:/config|offset|length|style|CODE|fe7su|并更改了配置|67mmg|?|atomic|98i14|vscode远程ssh设置中的路径。|629eq|这对我很有效。^0|0|0|F|O|14|9|0|0|0|1|0|0|0^^$0|$1|$2|3|4|5|6|$7|8|9|-4]]]|A|@$B|C|D|E|2|F|G|10|H|@]|I|@]|6|$]]|$B|J|D|K|2|F|G|11|H|@]|I|@]|6|$]]|$B|L|D|M|2|F|G|12|H|@$N|13|O|14|P|Q]|$N|15|O|16|P|Q]]|I|@]|6|$]]|$B|R|D|S|2|F|G|17|H|@]|I|@]|6|$]]|$B|T|D|U|2|V|G|18|H|@]|I|@$N|19|O|1A|B|1B]]|6|$]]|$B|W|D|X|2|F|G|1C|H|@]|I|@]|6|$]]|$B|Y|D|Z|2|F|G|1D|H|@]|I|@]|6|$]]]]

OS: windows 10
In my case there were permission issues. Repeatedly changing inheritance in windows did not solve the issue. Finally this worked
change the folder in which the config file is stored.
From <code>C:/users/usr/.ssh/config</code> to <code>D:/config</code>
and changed the config<a href="https://i.stack.imgur.com/ktvNX.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ktvNX.png" alt="enter image description here" /></a> path in vscode remote ssh settings.
This worked for me.

entityMap|blocks|key|dhsuh|text|这可能是每个人在看这里之前都尝试过的东西，但它对我很有效。我试图通过ssh进入的服务器没有响应，导致了不存在的管道错误。我重新启动了服务器，一切工作正常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

This is probably something everyone has tried before looking here, but it worked for me. The server I was trying to ssh into was not responding, leading to the nonexistant pipe error. I rebooted the server and everything worked fine.

entityMap|blocks|key|dk4f7|text|在我的例子中，密钥文件的路径是错误的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

In my case, the path to key file was wrong.

entityMap|blocks|key|9etln|text|对我来说，(windows)+.pem文件的权限是关键问题。我只在pem文件上有Administrator组，但它不工作。我还必须显式地添加Admin用户(即使admin当然属于管理员组)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

For me, (windows) the permissions on the .pem file were the Critical issue. I had Administrator group only on the pem file and it was not working. I had to explicitly add the Admin user as well (even though admin is of course in administrator group).

entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://stackoverflow.com/questions/60335069/vscode-remote-connection-error-the-process-tried-to-write-to-a-nonexistent-pipe/65566219#comment110186075_60336057|1|https://github.com/microsoft/vscode-remote-release/issues/2300#issue-560479572|blocks|key|6hoj|text|这似乎是一个有多种原因和相应补救措施的问题。在我的例子中，问题与我使用的ssh版本有关。在我的Windows+path中，有两个地方驻留着ssh.exe的实例：|unstyled|depth|inlineStyleRanges|entityRanges|bv0b4|C:\Program+Files+(x86)\OpenSSH\bin
C:\WINDOWS\System32\OpenSSH\|code-block|syntax|javascript|7lrk5|在使用两个路径设置"Remote.SSH:+Path"参数(位于"Remote.SSH:+Settings"[请参见here])，即第一个|offset|length|style|CODE|2ifto|C:\Program+Files+(x86)\OpenSSH\bin\ssh.exe然后|dpuc0|C:\WINDOWS\System32\OpenSSH\ssh.exe，这个问题仍然存在。|dc2m|然后我看着this并尝试了git提供的ssh.exe，我的系统上已经有了它(否则，只需安装git，无论如何它都是好东西:)|aplf0|使用设置SSH路径参数那个版本为我做了这件事，即将路径设置为：|7hgd9|C:\Program+Files\Git\usr\bin\ssh.exe^0|0|0|9|I|W|M|1M|4|0|0|0|16|0|0|Z|0|5|4|1|0|0|0|10^^$0|$1|$2|3|4|5|6|$7|8]]|9|$2|3|4|5|6|$7|A]]]|B|@$C|D|E|F|2|G|H|15|I|@]|J|@]|6|$]]|$C|K|E|L|2|M|H|16|I|@]|J|@]|6|$N|O]]|$C|P|E|Q|2|G|H|17|I|@$R|18|S|19|T|U]|$R|1A|S|1B|T|U]]|J|@$R|1C|S|1D|C|1E]]|6|$]]|$C|V|E|W|2|G|H|1F|I|@$R|1G|S|1H|T|U]]|J|@]|6|$]]|$C|X|E|Y|2|G|H|1I|I|@$R|1J|S|1K|T|U]]|J|@]|6|$]]|$C|Z|E|10|2|G|H|1L|I|@]|J|@$R|1M|S|1N|C|1O]]|6|$]]|$C|11|E|12|2|G|H|1P|I|@]|J|@]|6|$]]|$C|13|E|14|2|G|H|1Q|I|@$R|1R|S|1S|T|U]]|J|@]|6|$]]]]

This seems to be a problem with varied causes and corresponding remedies. In my case the problem had to do with the version of ssh I was using. In my Windows path there were two places were an instance of ssh.exe resided:
<pre><code>C:\Program Files (x86)\OpenSSH\bin
C:\WINDOWS\System32\OpenSSH\
</code></pre>
After using both paths to set the <code>&quot;Remote.SSH: Path&quot;</code> parameter (which is in <code>&quot;Remote.SSH: Settings&quot;</code> [see <a href="https://stackoverflow.com/questions/60335069/vscode-remote-connection-error-the-process-tried-to-write-to-a-nonexistent-pipe/65566219#comment110186075_60336057">here</a>]), i.e. first <code>C:\Program Files (x86)\OpenSSH\bin\ssh.exe</code> and then <code>C:\WINDOWS\System32\OpenSSH\ssh.exe</code>, the problem still persisted.
Then I looked at <a href="https://github.com/microsoft/vscode-remote-release/issues/2300#issue-560479572" rel="nofollow noreferrer">this</a> and tried the git-provided ssh.exe, which I already had on my system (otherwise, just install git, it's good stuff anyway :) )
Setting the SSH path parameter with that version did the trick for me, i.e. setting path to:
<code>C:\Program Files\Git\usr\bin\ssh.exe</code>

entityMap|blocks|key|812mu|text|尝试在"IdentityFile“中添加完整路径成功了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|37av3|“IdentityFile+C:\Users\xxx.ssh\xxx”^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|E|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|F|9|@]|A|@]|B|$]]]]

Trying to add the full path in &quot;IdentityFile&quot; made the trick
&quot; IdentityFile C:\Users\xxx.ssh\xxx&quot;

entityMap|blocks|key|49vr8|text|在我的情况下，我没有互联网连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|bcqds|我通过VPN连接到服务器，但远程配置不正确，无法访问服务器。(DNS相关问题)连接指示灯没有显示错误，所以我一开始没有想到这一点。|eq2dd|Oops+:)^0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|G|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|H|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|I|9|@]|A|@]|B|$]]]]

In my case, I had no internet connection.
I was connecting to the server via VPN but the remote configuration was incorrect and I couldn't access the server. (DNS related issues) The connection indicator was showing no errors, so I didn't think of that at first.
Oops :)

entityMap|blocks|key|f62tl|text|对于Windows：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|ec6i9|在私钥文件名之前添加转义字符&在路径两边使用引号解决了我的问题。|bd97s|//配置文件|ck86u|Host+12.12.12.12
++HostName+12.12.12.12
++IdentityFile+"C:\Users\USERNAME/\PRIVATEKEY"+<----Note+/\
++User+username```|code-block|syntax|javascript^0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|L|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|M|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|N|9|@]|A|@]|B|$]]|$2|G|4|H|6|I|8|O|9|@]|A|@]|B|$J|K]]]]

For Windows:
Adding the escape character before the private key file name &amp; using quotes around the path solved my issue.
//config file
<pre><code>Host 12.12.12.12
 HostName 12.12.12.12
 IdentityFile &quot;C:\Users\USERNAME/\PRIVATEKEY&quot; &lt;----Note /\
 User username
</code></pre>

entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://stackoverflow.com/users/3407424/dalilander|blocks|key|43k63|text|在我的例子中，我做了什么dalilander说，但不是删除整个'.ssh‘文件夹，我只需要删除文件’已知_然后它就起作用了。所以我保存的服务器没有被删除。|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|bkkdh|该文件夹的路径为C:\Users**您的用户名**.ssh^0|C|A|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|M|G|@]|H|@$I|N|J|O|A|P]]|6|$]]|$A|K|C|L|2|E|F|Q|G|@]|H|@]|6|$]]]]

In my case, I did what <a href="https://stackoverflow.com/users/3407424/dalilander">dalilander</a> said, but instead of deleting the entire '.ssh' folder, I just needed to delete the file 'known_hosts' and then it worked. So the servers I had saved were not deleted.
The path of that folder is C:\Users\yourUsername\.ssh

entityMap|blocks|key|5f9e1|text|我真的不想删除我的C:Users\valo\.ssh\config，所以我使用了一些不同的条目。事实证明，对我来说，选择IdentitiesOnly+yes才是问题所在。中的所有密钥文件上禁用安全性继承。.ssh文件夹，只留下我自己，Full+Rights..。这是我的C:Users\valo\.ssh\config现在看起来是这样的：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|crm0u|CanonicalizeHostname+yes

Host+aws.r3
++HostName+3.31.45.216
++ForwardAgent+yes
++User+ubuntu
++IdentityFile+C:Users\valo\.ssh\u1-client-20210203-090555.pem
++#+IdentitiesOnly+yes++++#+VSCode+Remote+doesn't+like+this+flag...?

Host+github
++HostName+github.com
++User+git
++IdentityFile+~/.ssh/id_val_ed25519

Host+github.vm
++HostName+github.com
++User+git
++IdentityFile+~/.ssh/id_valo_ed25519

Host+*
++ForwardAgent+yes
++AddKeysToAgent+yes
++LogLevel+FATAL
++ChallengeResponseAuthentication+no|code-block|syntax|javascript|fjp28|现在我可以连接到aws.r3使用VSCode+Remote。^0|9|O|1O|I|2U|4|39|B|3R|O|0|0|8|6^^$0|$]|1|@$2|3|4|5|6|7|8|N|9|@$A|O|B|P|C|D]|$A|Q|B|R|C|D]|$A|S|B|T|C|D]|$A|U|B|V|C|D]|$A|W|B|X|C|D]]|E|@]|F|$]]|$2|G|4|H|6|I|8|Y|9|@]|E|@]|F|$J|K]]|$2|L|4|M|6|7|8|Z|9|@$A|10|B|11|C|D]]|E|@]|F|$]]]]

I really didn't want to delete my <code>C:Users\valo\.ssh\config</code>, so I played a little with the various entries. It turned out that for me the option <code>IdentitiesOnly yes</code> was the problem. I also disabled security inheritance on all key files in the <code>.ssh</code> folder and left only myself, with <code>Full Rights</code>. Here is what my <code>C:Users\valo\.ssh\config</code> looks like now:
<pre><code>CanonicalizeHostname yes

Host aws.r3
 HostName 3.31.45.216
 ForwardAgent yes
 User ubuntu
 IdentityFile C:Users\valo\.ssh\u1-client-20210203-090555.pem
 # IdentitiesOnly yes # VSCode Remote doesn't like this flag...?

Host github
 HostName github.com
 User git
 IdentityFile ~/.ssh/id_val_ed25519

Host github.vm
 HostName github.com
 User git
 IdentityFile ~/.ssh/id_valo_ed25519

Host *
 ForwardAgent yes
 AddKeysToAgent yes
 LogLevel FATAL
 ChallengeResponseAuthentication no
</code></pre>
Now I can connect to <code>aws.r3</code> with VSCode Remote.

entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://code.visualstudio.com/docs/remote/troubleshooting#_troubleshooting-hanging-or-failing-connections|blocks|key|8vqhi|text|在我的案例中，解决方案是编辑VSC的json设置文件，如下所示：https://code.visualstudio.com/docs/remote/troubleshooting#\_troubleshooting-hanging-or-failing-connections在VSC中，转到“文件”、“首选项”、“设置”，然后单击右上角的图标(打开设置，JSON)。将这两行添加到settings.json并重试连接：|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|au3bj|"remote.SSH.showLoginTerminal":+true,
"remote.SSH.useLocalServer":+false|code-block|syntax|javascript^0|W|2Y|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|P|G|@]|H|@$I|Q|J|R|A|S]]|6|$]]|$A|K|C|L|2|M|F|T|G|@]|H|@]|6|$N|O]]]]

The solution in my case was editing the json settings file for VSC as shown here: <a href="https://code.visualstudio.com/docs/remote/troubleshooting#_troubleshooting-hanging-or-failing-connections" rel="nofollow noreferrer">https://code.visualstudio.com/docs/remote/troubleshooting#_troubleshooting-hanging-or-failing-connections</a>
In VSC go to File, Preferences, Setting and click on the upper right hand icon (Open Settings, JSON). Add these two lines to settings.json and retry connecting:
<pre><code>&quot;remote.SSH.showLoginTerminal&quot;: true,
&quot;remote.SSH.useLocalServer&quot;: false
</code></pre>

entityMap|blocks|key|a552r|text|一种可能的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|re72|第一次运行cat+$HOME/.ssh/id_rsa.pub在你的电脑上。这会给你一把钥匙。把这个钥匙保存在某个地方。|offset|length|style|CODE|3ppcv|然后通过运行以下命令打开此文件vim+$HOME/.ssh/authorized_keys在你要连接的电脑上。然后将密钥复制到此文件的新行中，并通过键入以下命令关闭它:wq..。|b7oa7|你已经准备好了。^0|0|5|P|0|F|U|2B|3|0^^$0|$]|1|@$2|3|4|5|6|7|8|M|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|N|9|@$E|O|F|P|G|H]]|A|@]|B|$]]|$2|I|4|J|6|7|8|Q|9|@$E|R|F|S|G|H]|$E|T|F|U|G|H]]|A|@]|B|$]]|$2|K|4|L|6|7|8|V|9|@]|A|@]|B|$]]]]

A possible solution:
First run <code>cat $HOME/.ssh/id_rsa.pub</code> on your computer. That will get you a key. Save this key somewhere.
Then open this file by running <code>vim $HOME/.ssh/authorized_keys</code> on the computer that you're are ssh'ing to. Then copy the key in a new line of this file and close it by typing <code>:wq</code>.
You are all set.

I use vscode with remote-ssh to connect my server, after configuring, I want to connect my host, but it failed, the dialog box display:&quot;could not establish connection to XX, The process tried to write to a nonexistent pipe.&quot;
output:
<pre><code>[16:45:20.916] Log Level: 3
[16:45:20.936] remote-ssh@0.49.0
[16:45:20.936] win32 x64
[16:45:20.944] SSH Resolver called for &quot;ssh-remote+aliyun&quot;, attempt 1
[16:45:20.945] SSH Resolver called for host: aliyun
[16:45:20.945] Setting up SSH remote &quot;aliyun&quot;
[16:45:21.012] Using commit id &quot;c47d83b293181d9be64f27ff093689e8e7aed054&quot; and quality &quot;stable&quot; for server
[16:45:21.014] Install and start server if needed
[16:45:21.019] Checking ssh with &quot;ssh -V&quot;
[16:45:21.144] &gt; OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
[16:45:21.214] Running script with connection command: ssh -T -D 5023 aliyun bash
[16:45:21.221] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[16:45:21.504] &gt; 
&gt; 
&gt;
&gt; ]0;C:\WINDOWS\System32\cmd.exe
[16:45:21.505] Got some output, clearing connection timeout
[16:45:21.577] &gt; 
&gt; 
&gt;
&gt; 
[16:45:21.592] &gt; Bad owner or permissions on C:\\Users\\DY/.ssh/config
&gt; 
[16:45:21.689] &gt; The process tried to write to a nonexistent pipe.
&gt; 
[16:45:22.091] &quot;install&quot; terminal command done
[16:45:22.092] Install terminal quit with output: The process tried to write to a nonexistent pipe.
[16:45:22.093] Received install output: The process tried to write to a nonexistent pipe.
[16:45:22.096] Resolver error: The process tried to write to a nonexistent pipe
[16:45:22.107] ------

</code></pre>

VScode remote connection error: The process tried to write to a nonexistent pipe

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

 我使用vscode和remote-ssh来连接我的服务器，在配置之后，我想连接我的主机，但它失败了，对话框显示：“无法建立到XX的连接，进程试图写入不存在的管道。” 输出： [16:45:20.916] Log Level: 3[16:45:20.936] remote-ssh@0.49.0[16:45:20.936...

问VScode远程连接错误:进程试图写入不存在的管道
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问VScode远程连接错误:进程试图写入不存在的管道EN