Skip to content

Commit d9aa08a

Browse files
committed
feat(notes): add vscode remotes not working workaround post
Ref: microsoft/vscode#329735 Signed-off-by: Xe Iaso <me@xeiaso.net>
1 parent 8b8aca3 commit d9aa08a

1 file changed

Lines changed: 29 additions & 0 deletions

File tree

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
title: "If your VS Code remotes stopped working, downgrade to v1.124.x"
3+
desc: "Quality software reigns again"
4+
date: 2026-08-26
5+
---
6+
7+
Today I woke up and saw a brand new VS Code error when I remoted into my coding box:
8+
9+
<center>
10+
<Picture
11+
path="notes/2026/vscode-remotes-not-working-downgrade/vscode-error"
12+
desc="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."
13+
/>
14+
</center>
15+
16+
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.
17+
18+
<center>
19+
<Picture
20+
path="notes/2026/vscode-remotes-not-working-downgrade/vscode-back"
21+
desc="The VS Code UI drafting an early version of this post."
22+
/>
23+
</center>
24+
25+
Obviously keeping things at this older version of VS Code is not a viable strategy, so maybe [this issue will actually be fixed](https://github.com/microsoft/vscode/issues/329735) instead of just being closed for no reason.
26+
27+
<Conv name="Numa" mood="smug">
28+
Quality software reigns again!
29+
</Conv>

0 commit comments

Comments
 (0)