If your VS Code remotes stopped working, downgrade to v1.124.x

Published on , 170 words, 1 minutes to read

Quality software reigns again

Today I woke up and saw a brand new VS Code error when I remoted into my coding box:

A VS Code error saying that the remote SSH extension can't use the API terminalRemoteResolver and that I have to start VS Code with some weird command line flag or something.
A VS Code error saying that the remote SSH extension can't use the API terminalRemoteResolver and that I have to start VS Code with some weird command line flag or something.

Trying to update my extensions didn't work. I still got that error. The only thing that worked was to downgrade to VS Code v1.124.2. This also undid the redesign that I kinda hate.

The VS Code UI drafting an early version of this post.
The VS Code UI drafting an early version of this post.

Obviously keeping things at this older version of VS Code is not a viable strategy, so maybe this issue will actually be fixed instead of just being closed for no reason.

Numa is smug
Numa

Quality software reigns again!

Facts and circumstances may have changed since publication. Please contact me before jumping to conclusions if something seems wrong or unclear.

Tags: