witwiki
commented
1 year ago The first thing I did today was run a script which worked perfectly fine yesterday before my last commit for the day. The script didn't run and gave me the error:
httpx.ConnectError: [Errno -3] Temporary failure in name resolution
The only change I made in between those times was to update my VS Code via settings. My remote connection is automatically established as per the above-reproduced steps when I open VS Code.
I can't perform a basic git pull or git push on any of my repos inside my WSL instance inside the integrated terminal on vs-code.
Did the recent update mess up the remote-ssh login? If so, is there a fix for this?
Would appreciate a quick resolution.
p1gd0g
hongwen000
fadialzammar
alexAtQuanos
roblourens
MichealPearce
mo29cg
raphaelcarlosr
meganrogge
github-actions[bot]
windzhu0514
amunger
Is there an existing issue for this bug?
Required Troubleshooting Steps
remote.SSH.useLocalServersettingConnect Locally
It connects successfully
->
No response
Expected Behavior
A workspace that was created in VSCode 1.78 or below opens in VSCode 1.79
Steps To Reproduce
> Remote-SSH: Connect to Host...command.code-workspacefileRemote-SSH Log
Remote-SSH Log
``` [17:28:51.144] Log Level: 2 [17:28:51.147] VS Code version: 1.79.0 [17:28:51.147] Remote-SSH version: remote-ssh@0.102.0 [17:28:51.147] win32 x64 [17:28:51.155] SSH Resolver called for "ssh-remote+dev", attempt 1 [17:28:51.156] "remote.SSH.useLocalServer": false [17:28:51.156] "remote.SSH.showLoginTerminal": false [17:28:51.156] "remote.SSH.remotePlatform": {"REDACTED"} [17:28:51.156] "remote.SSH.path": undefined [17:28:51.156] "remote.SSH.configFile": undefined [17:28:51.156] "remote.SSH.useFlock": true [17:28:51.156] "remote.SSH.lockfilesInTmp": false [17:28:51.156] "remote.SSH.localServerDownload": auto [17:28:51.157] "remote.SSH.remoteServerListenOnSocket": false [17:28:51.158] "remote.SSH.showLoginTerminal": false [17:28:51.158] "remote.SSH.defaultExtensions": [] [17:28:51.158] "remote.SSH.loglevel": 2 [17:28:51.158] "remote.SSH.enableDynamicForwarding": true [17:28:51.158] "remote.SSH.enableRemoteCommand": false [17:28:51.158] "remote.SSH.serverPickPortsFromRange": {} [17:28:51.158] "remote.SSH.serverInstallPath": {} [17:28:51.162] SSH Resolver called for host: dev [17:28:51.162] Setting up SSH remote "dev" [17:28:51.164] Using commit id "b380da4ef1ee00e224a15c1d4d9793e27c2b6302" and quality "stable" for server [17:28:51.166] Install and start server if needed [17:28:51.170] Checking ssh with "C:\Program Files (x86)\VMware\VMware Player\bin\ssh.exe -V" [17:28:51.173] Got error from ssh: spawn C:\Program Files (x86)\VMware\VMware Player\bin\ssh.exe ENOENT [17:28:51.173] Checking ssh with "C:\WINDOWS\system32\ssh.exe -V" [17:28:51.174] Got error from ssh: spawn C:\WINDOWS\system32\ssh.exe ENOENT [17:28:51.174] Checking ssh with "C:\WINDOWS\ssh.exe -V" [17:28:51.175] Got error from ssh: spawn C:\WINDOWS\ssh.exe ENOENT [17:28:51.175] Checking ssh with "C:\WINDOWS\System32\Wbem\ssh.exe -V" [17:28:51.176] Got error from ssh: spawn C:\WINDOWS\System32\Wbem\ssh.exe ENOENT [17:28:51.176] Checking ssh with "C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe -V" [17:28:51.177] Got error from ssh: spawn C:\WINDOWS\System32\WindowsPowerShell\v1.0\ssh.exe ENOENT [17:28:51.178] Checking ssh with "C:\WINDOWS\System32\OpenSSH\ssh.exe -V" [17:28:51.210] > OpenSSH_for_Windows_8.6p1, LibreSSL 3.4.3 [17:28:51.214] Running script with connection command: "C:\WINDOWS\System32\OpenSSH\ssh.exe" -T -D 60350 dev bash [17:28:51.216] Terminal shell path: C:\WINDOWS\System32\cmd.exe [17:29:08.225] Resolver error: Error: Connecting with SSH timed out at m.Timeout (c:\Users\Fadi\.vscode\extensions\ms-vscode-remote.remote-ssh-0.102.0\out\extension.js:1:584271) at Timeout._onTimeout (c:\Users\Fadi\.vscode\extensions\ms-vscode-remote.remote-ssh-0.102.0\out\extension.js:1:680601) at listOnTimeout (node:internal/timers:559:17) at process.processTimers (node:internal/timers:502:7) [17:29:08.228] ------ [17:29:08.930] > Warning: No xauth data; using fake authentication data for X11 forwarding. > e18443b60912: running > ]0;C:\WINDOWS\System32\cmd.exe [17:29:08.931] Got some output, clearing connection timeout [17:29:08.944] > Acquiring lock on /home/fadi/.vscode-server/bin/b380da4ef1ee00e224a15c1d4d9793e27c2b6302/vscode-remote-lock.fadi.b380da4ef1ee00e224a15c1d4d9793e27c2b6302 > Found existing installation at /home/fadi/.vscode-server/bin/b380da4ef1ee00e224a15c1d4d9793e27c2b6302... > Checking /home/fadi/.vscode-server/.b380da4ef1ee00e224a15c1d4d9793e27c2b6302.log and /home/fadi/.vscode-server/.b380da4ef1ee00e224a15c1d4d9793e27c2b6302.pid for a running server [17:29:08.965] > Looking for server with pid: 2205 > Found running server... > > * > * Visual Studio Code Server > * > * By using the software, you agree to > * the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and > * the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement). > * > > Checking server status on port 40433 with wget > e18443b60912: start > SSH_AUTH_SOCK==== > DISPLAY==dev:11.0== > webUiAccessToken==== > listeningOn==40433== > osReleaseId==ubuntu== > arch==x86_64== > vscodeArch==x64== > bitness==64== > tmpDir==/run/user/1000== > platform==linux== > unpackResult==== > didLocalDownload==0== > downloadTime==== > installTime==== > extInstallTime==== > serverStartTime==== > connectionToken==a1111111-1a11-1aa1-a111-111aaa11111a== > e18443b60912: end [17:29:08.981] > ```
Anything else?
If I connect without a workspace and create a new one, I am able to open that without issue. Downgrading to VSCode 1.78 fixes this issue.