Remote not working after upgrading to win11 #5290
Assignees
Comments
|
Can you please post the full logs? And did you update the local machine to Windows 11? What remote OS are you connecting to? |
I'm not sure if this is the log you want, hope it helps. |
|
I installed the insiders version and it works well. But I still don’t know why the stable version cannot connect to the server |
|
Thanks for the update @Dradows. If Insiders works, there may be new fixes/features in Remote-SSH Insiders and/or VS Code Insiders that enable this, so perhaps that could explain it. If you're able to consistently use Insiders, I suspect that could be the case? |
|
I can confirm having the same issue with a freshly installed Windows 11 installation (build 10.0.22000.194). Remote machine runnning on CentOS 7.
Extension version: 0.65.8 |
|
If this is still happening, could you share the log from the Remote-SSH output channel? |
|
I have the exact same problem. Can we reopen this issue ? |
Sorry for the late reply. The log does not seem to be informative imo, but here is it:
What I find weird is that it works every few tries (of ~5 failed attempts the ~6th works). |
|
it happened again tonight. from remote-ssh output channel: (also see console log with the developer tools console log: |
|
Hm does anything here help? #103 Such as deleting the |
No. I've been there several times, removed .vscode-server, no impact. I once suspected the extensions and chmod'ed 400 the extensions subdir, no more success.
This is an Amazon Linux 2 box: some more facts:
thanks ! |
|
another information: tried to remote connect to an ubuntu host and got the exact same error.
This looks like a client side problem to me |
|
sorry about the spam, but now suddenly it works... |
|
I am still suffering from this problem. Is there any further solution?I have exactly the same problem, and I have also tried using the preview version of vscode or the plug-in but it does not solve the problem. |
|
I also tried to delete the .vscode-server on the server side, but it didn't work. My other win10 computer has exactly the same configuration as my win11 computer. The vscode of the win10 computer can work normally, but the vscode of win11 cannot work. |
|
Hm @BlackHalo-Drake do you also get Also to verify are you able to connect to the same host through PowerShell? Such as |
|
I do get Unauthorized client refused: auth mismatch errors and I can connect to the same host through PowerShell. Amd here is my log : |
and here is the server log: |
|
This seems similar to errors found here: #4087 @deepak1556 do you have any idea about any updates to win11 and electron that could cause this? My assumption based on the other issue was that being up to date on the extension and VS Code would have had the electron updates to not see this error? |
Deleting the Meanwhile I'm having a windows 10 backup system - there everything still works.
Yeah, works well. Powershell, Putty, ... |
|
@alexdima and @deepak1556 are you aware of any |
|
@tanhakabir The error comes from here. This indicates that the server is started with I am hesitant to add more logging on the server side because I don't want to log the actual secrets. I see that the SSH extension is logging sometimes the secrets ( Regarding #4087: I have improved the error messages slightly since #4087 . I believe #4087 was failing in a different check, most likely because |
tanhakabir
added
bug
|
This has just started happening to me today with the Remote - Containers extension (Windows 10). I managed to make it work by downgrading the extension to v0.224.3. Neither the next most recent version (v0.231.2) nor insiders (v0.232.3) worked for me. |
|
I had this same issue come up today (Ubuntu 18.04), and downgrading to v0.231.1 worked but the most recent version (v0.231.2) failed. |
|
Same issue suddenly started happening to me today (Error message "auth mismatch") after using the extension for months without problems. I can also confirm that the issue is fixed by downgrading the extension to v0.231.1 and deleting the .vscode-server folder on the remote. |
|
I was able to connect fine several days ago, and suddenly ran into this error when I attempted to connect this morning. Downgrading to v0.224.3 fixed it for me. |
|
Still having that issue since official release of windows 11 in october 2021 (see my comments above).
This error just pops up completely randomly. Sometimes it works, sometimes not. Sometimes it only works after a restart, sometimes without a restart. I am sure that this is not a problem with the server, since I have this problem with all SSH servers that I connect to with this plugin in between (Debian 9, 10, Ubuntu, ...) This problem never existed with Windows 10 with given servers. |
|
I`m on a Ubuntu 20.04 host. Seems to not being specific to the OS Version. Probably the updates rolled out at different times. Also in my case it`s not a ssh connection but attaching to Pods in a Kubernetes Cluster. |
|
@Boca13 Downgrading to v0.231.1 fix this issue for me. Thanks! @Sacerdoss I'm also connecting to a k8s pod. Downgrading the |
|
I checked the commits from v0.231.1 to current master. It seems that the main difference is adding a condition in |
|
cc @chrmarti |
|
I had to downgrade to v0.224.3 in order to resolve the issue. |
This was referenced Apr 8, 2022
|
I had the same issue with Windows11 21H2 22000.856. Remote SSH version: v0.85.2022071315 But I found a MAJIC way to connnet to the remote successfully:
vscode-server logs: Remote SSH logs |
|
Lots has changed, is anyone still seeing this? If so, it seems like it's affecting both SSH and Containers |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Type: Bug
Everything was normal before, but after upgrading to win11, I can’t connect to the remote server.
Only show “cannot fetch remote environment” “connection error: unauthorized client refused: auth mismatch”.
This problem appeared on both of my two computers that were just updated to win11.
Extension version: 0.21.0
VS Code version: Code 1.57.1 (507ce72a4466fbb27b715c3722558bb15afa9f48, 2021-06-17T13:28:07.755Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No
Fetching remote diagnostics for 'SSH: 123.56.44.42' failed: Connection error: Unauthorized client refused: auth mismatch
System Info
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Fetching remote diagnostics for 'SSH: 123.56.44.42' failed: Connection error: Unauthorized client refused: auth mismatch
A/B Experiments
The text was updated successfully, but these errors were encountered: