Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to connect to the remote extension host server (Error: Connection error: Unauthorized client refused.) #103

Open
wqfan opened this issue May 4, 2019 · 122 comments

Comments

@wqfan
Copy link

commented May 4, 2019

  • VSCode Version: Version 1.34.0-insider (1.34.0-insider)
  • Local OS Version: macOS 10.14.4 (18E226)
  • Remote OS Version: Amazon Linux Bare Metal release 2012.03
  • Remote Extension/Connection Type: SSH

Steps to Reproduce:

  1. Cmd-Shift-P, and choose Remote-SSH: Connect current window to host...
  2. Connection is successful. Remote tools are installed and server is running on remote
  3. VS Code shows an error at right-bottom: Failed to connect to the remote extension host server (Error: Connection error: Unauthorized client refused.)

AllowTcpForwarding is enabled on the remote server.

Here is the full output from "Remote - SSH" channel:

SSH Resolver called for "ssh-remote+dev-server"
SSH Resolver called for host: dev-server
Setting up SSH remote "dev-server"
Using commit id "473af338e1bd9ad4d9853933da1cd9d5d9e07dc9" and quality "insider" for server
Install and start server if needed
> bash: no job control in this shell
> Found existing installation...
> Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.8/FAQ
> Found running server...
>  
> *
> * Reminder: You may only use this software with Visual Studio family products,
> * as described in the license (https://go.microsoft.com/fwlink/?linkid=2077057)
> *
>  
> bb80525e-2122-4fa5-8e4a-9d91821eeb83==45539==
"install" terminal command done
Received install output: bb80525e-2122-4fa5-8e4a-9d91821eeb83==45539==
Server is listening on port 45539
Spawning tunnel with: ssh  dev-server -N -L localhost:32546:localhost:45539
Spawned SSH tunnel between local port 32546 and remote port 45539
Waiting for ssh tunnel to be ready
Tunneling remote port 45539 to local port 32546
Resolving "ssh-remote+dev-server" to "localhost:32546", attempt: 1

Logs from "Log (Window)" channel:

[2019-05-03 18:02:25.843] [renderer1] [error] Connection error: Unauthorized client refused.: Error: Connection error: Unauthorized client refused.
    at v (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:1544:9)
    at t.onControlMessage.o (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:1542:930)
    at d.fire (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:77:818)
    at a (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:321:48)
    at e (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:321:94)
    at d.fire (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:77:818)
    at S._receiveMessage (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:330:65)
    at S._socketDisposables.push._socketReader.onMessage.e (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:327:243)
    at d.fire (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:77:818)
    at g.acceptChunk (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:323:801)
    at _register._socket.onData.e (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:323:153)
    at Socket.t (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:332:235)
    at Socket.emit (events.js:182:13)
    at addChunk (_stream_readable.js:279:12)
    at readableAddChunk (_stream_readable.js:264:11)
    at Socket.Readable.push (_stream_readable.js:219:10)
    at TCP.onread (net.js:636:20)
[2019-05-03 18:02:25.844] [renderer1] [error] Cannot read property 'extensions' of null: TypeError: Cannot read property 'extensions' of null
    at e.<anonymous> (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3850:751)
    at Generator.next (<anonymous>)
    at r (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:34:454)
    at process._tickCallback (internal/process/next_tick.js:68:7)
[2019-05-03 18:02:25.844] [renderer1] [error] Connection error: Unauthorized client refused.: Error: Connection error: Unauthorized client refused.
    at v (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:1544:9)
    at t.onControlMessage.o (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:1542:930)
    at d.fire (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:77:818)
    at a (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:321:48)
    at e (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:321:94)
    at d.fire (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:77:818)
    at S._receiveMessage (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:330:65)
    at S._socketDisposables.push._socketReader.onMessage.e (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:327:243)
    at d.fire (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:77:818)
    at g.acceptChunk (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:323:801)
    at _register._socket.onData.e (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:323:153)
    at Socket.t (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:332:235)
    at Socket.emit (events.js:182:13)
    at addChunk (_stream_readable.js:279:12)
    at readableAddChunk (_stream_readable.js:264:11)
    at Socket.Readable.push (_stream_readable.js:219:10)
    at TCP.onread (net.js:636:20)
[2019-05-03 18:02:28.207] [renderer1] [error] Could not fetch environment: Error: Could not fetch environment
    at d.getEnvironment.then.e (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:3813:413)

Does this issue occur when you try this locally?: Yes
Does this issue occur when you try this locally and all extensions are disabled?: Yes

@roblourens

This comment has been minimized.

Copy link
Member

commented May 4, 2019

@alexandrudima Unauthorized client refused comes from some kind of auth failure, what does that imply?

@wqfan You could try reinstalling by deleting the folder ~/.vscode-remote from the remote machine

@wqfan

This comment has been minimized.

Copy link
Author

commented May 4, 2019

@roblourens Thanks for your follow up on this issue. I have tried deleting that folder a few times and it doesn't make any difference.

@lars18th

This comment has been minimized.

Copy link

commented May 4, 2019

Hi,

Identical problem.
Futhermore in the "new" VSCode window (when connecting with "Connect to host in new window") in the Terminal after all I see:

Connected to SSH Host - Please do not close this terminal

But the same error
Failed to connect to the remote extension host server (Error: Connection error: Unauthorized client refused.)

This doesn't have sense!

@lars18th

This comment has been minimized.

Copy link

commented May 4, 2019

Debug info:

This is my .vscode-remote/.473af338e1bd9ad4d9853933da1cd9d5d9e07dc9.log:

Remote configuration data at /root/.vscode-remote


*
* Visual Studio Code Server
*
* Reminder: You may only use this software with Visual Studio family products,
* as described in the license https://aka.ms/vscode-remote/license
*


Error: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.18' not found (required by /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/node_modules/spdlog/build/Release/spdlog.node)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:731:18)
    at Module.load (internal/modules/cjs/loader.js:612:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:551:12)
    at Function.Module._load (internal/modules/cjs/loader.js:543:3)
    at Module.require (internal/modules/cjs/loader.js:650:17)
    at Module.patchedRequire [as require] (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/node_modules/diagnostic-channel/dist/src/patchRequire.js:14:46)
    at require (internal/modules/cjs/helpers.js:20:18)
    at bindings (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/node_modules/bindings/bindings.js:81:44)
    at Object.<anonymous> (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/node_modules/spdlog/index.js:3:35)
    at Module._compile (internal/modules/cjs/loader.js:702:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:713:10)
    at Module.load (internal/modules/cjs/loader.js:612:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:551:12)
    at Function.Module._load (internal/modules/cjs/loader.js:543:3)
    at Module.require (internal/modules/cjs/loader.js:650:17)
    at Module.patchedRequire [as require] (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/node_modules/diagnostic-channel/dist/src/patchRequire.js:14:46)
    at require (internal/modules/cjs/helpers.js:20:18)
    at Function.i [as __$__nodeRequire] (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:31:542)
    at Object.t.createSpdLogService (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/agent/remoteExtensionHostAgent.js:213:301)
    at G.<anonymous> (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/agent/remoteExtensionHostAgent.js:363:833)
    at Generator.next (<anonymous>)
    at /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/agent/remoteExtensionHostAgent.js:16:388
    at new Promise (<anonymous>)
    at r (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/agent/remoteExtensionHostAgent.js:16:165)
    at G._createServices (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/agent/remoteExtensionHostAgent.js:363:624)
    at Function.create (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/agent/remoteExtensionHostAgent.js:363:554)
    at T.<anonymous> (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/agent/remoteExtensionHostAgent.js:370:597)
    at Generator.next (<anonymous>)
    at /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/agent/remoteExtensionHostAgent.js:16:388
    at new Promise (<anonymous>)
    at r (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/agent/remoteExtensionHostAgent.js:16:165)
    at T.start (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/agent/remoteExtensionHostAgent.js:370:516)
    at Object.<anonymous> (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/agent/remoteExtensionHostAgent.js:379:52)
    at Function.t._safeInvokeFunction (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:20:173)
    at Function.t._invokeFactory (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:20:420)
    at t.complete (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:20:657)
    at s._onModuleComplete (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:30:796)
    at s._onModuleComplete (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:31:41)
    at s._onModuleComplete (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:31:41)
    at s._onModuleComplete (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:31:41)
    at s._onModuleComplete (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:31:41)
    at s._onModuleComplete (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:31:41)
    at s._resolve (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:30:356)
    at s.defineModule (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:24:768)
    at r (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:28:919)
    at Object.l (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:36:405)
    at Function.t._safeInvokeFunction (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:20:173)
    at Function.t._invokeFactory (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:20:420)
    at t.complete (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:20:657)
    at s._onModuleComplete (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:30:796)
    at s._onModuleComplete (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:31:41)
    at s._resolve (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:30:356)
    at s.defineModule (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:24:768)
    at r (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:31:950)
    at f (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:17:524)
    at Object.<anonymous> (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/agent/remoteExtensionHostAgent.nls.js:4:1)
    at t._loadAndEvalScript (/root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:17:568)
    at /root/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/out/vs/loader.js:17:285
    at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:440:3)
IP Address: 192.168.1.142
Extension host agent listening on 56216
{ [Error: ENOENT: no such file or directory, scandir '/root/.vscode-remote/data/logs']
  errno: -2,
  code: 'ENOENT',
  syscall: 'scandir',
  path: '/root/.vscode-remote/data/logs' }
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.

I hope it can be fixed soon. 😢

@u3u

This comment has been minimized.

Copy link

commented May 4, 2019

The same problem.
When I remove the ~/.vscode-remote directory reconnect prompts the following error:

> cat: ~/.vscode-remote/.473af338e1bd9ad4d9853933da1cd9d5d9e07dc9.log: No such file or directory
> Server did not start successfully. Full server log:
> cat: ~/.vscode-remote/.473af338e1bd9ad4d9853933da1cd9d5d9e07dc9.log411693af-6a8f-4de5-9053-7abf6ae26efe====
> : No such file or directory
"install" terminal command done
Received install output: : No such file or directory
Failed to parse remote port from server output: : No such file or directory

When I manually create the log file, connect the prompt again:
Could not establish connection to "server".

> Server did not start successfully. Full server log:
> 
> 127e184a-8aae-450a-9261-613691a553db====
"install" terminal command done
Received install output: 127e184a-8aae-450a-9261-613691a553db====
Failed to parse remote port from server output: 127e184a-8aae-450a-9261-613691a553db====
@kieferrm

This comment has been minimized.

Copy link
Member

commented May 4, 2019

@wqfan it looks like you're running Amazon Linux Bare Metal release 2012.03. I'm guessing that's causing your issue. If possible, please try a Ubuntu 18.04.

@lars18th what server OS are you running.

@wqfan

This comment has been minimized.

Copy link
Author

commented May 4, 2019

@kieferrm It can be a problem of the OS. Does the remote extension only work with Ubuntu? Unfortunately, this is the only development server I have and I can't change the OS.

My ~/.vscode-remote/.473af338e1bd9ad4d9853933da1cd9d5d9e07dc9.log is a bit different from @lars18th:

Remote configuration data at /home/qingfanw/.vscode-remote


*
* Visual Studio Code Server
*
* Reminder: You may only use this software with Visual Studio family products,
* as described in the license https://aka.ms/vscode-remote/license
*


IP Address: 172.22.135.15
Extension host agent listening on 38337
Unauthorized client refused.
Unauthorized client refused.
@wqfan

This comment has been minimized.

Copy link
Author

commented May 4, 2019

@u3u I think you shouldn't remove the folder directly.

Try the Remote SSH: Uninstall VS Code Server from Host... command and then reinstall it with Remote-SSH: Connect current window to host....

@khuongduybui

This comment has been minimized.

Copy link

commented May 4, 2019

@wqfan I am not sure it's the OS. I just tried a public AL2012 EC2 instance (not AL2) and it worked just fine. (Of course it's named 2018.03 but we all know it's AL2012.)

So the first thing I checked is sshd version.
AL2012: OpenSSH_7.4p1, OpenSSL 1.0.1k-fips 8 Jan 2015
AL2018: OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017

Are we screwed because our super-legacy dev desktops still use OpenSSL 1.0.1 for sshd?

@wqfan

This comment has been minimized.

Copy link
Author

commented May 4, 2019

@khuongduybui Thanks for your information. I have upgraded OpenSSL and been using OpenSSH:

$ openssl version                                                                                                                                    255 ↵
OpenSSL 1.0.2r  26 Feb 2019

$ sshd -V                                                                                                                                             1 ↵
OpenSSH_8.0p1, OpenSSL 1.0.2r  26 Feb 2019

The problem still exists.

@singerb

This comment has been minimized.

Copy link

commented May 4, 2019

Same version `GLIBCXX_3.4.18' not found issue, same unable to connect (this is after replacing the realpath with readlink -f in server.sh to allow the server to start). strings /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | grep GLIBC lists up to GLIBCXX_3.4.17, cat /etc/debian_version -> 7.9. Like many people, this is a sandbox environment and I don't have access to mess with the software on it. Perhaps a statically compiled node-spdlog would work?

@lars18th

This comment has been minimized.

Copy link

commented May 5, 2019

@lars18th what server OS are you running.

Debian 7 x64 sandbox. No other alternative.

Please, think on compile dependencies STATICALLY to resolve these problems.
Note too that I feel this issue is related to #84 .

@egamma egamma added the remote label May 6, 2019

@alexandrudima

This comment has been minimized.

Copy link
Member

commented May 6, 2019

@joaomoreno @sandy081

Would you know what we need to do to make node-spdlog work on these environments? See #103 (comment)

@lars18th

This comment has been minimized.

Copy link

commented May 6, 2019

@joaomoreno @sandy081

Would you know what we need to do to make node-spdlog work on these environments? See #103 (comment)

Sorry! I don't want to offend anyone. My objective is provide feedback and ideas. 😉

@iamatypeofwalrus

This comment has been minimized.

Copy link

commented May 6, 2019

Debug info:

This is my .vscode-remote/.473af338e1bd9ad4d9853933da1cd9d5d9e07dc9.log:

 ...

I hope it can be fixed soon. 😢

The spdlog issue seems different than the error op is seeing but manifests as the same unauthorized error. @lars18th can you create a separate issue for the spdlog issue you're seeing?

For what it's worth I'm seeing the exact same issue as op (not surprising given our mutual employer).

@alexandrudima

This comment has been minimized.

Copy link
Member

commented May 7, 2019

Can I download Amazon Linux Bare Metal release 2012.03 and run it locally in a VM to investigate what's going on ? i.e. how could I investigate?

@lars18th

This comment has been minimized.

Copy link

commented May 7, 2019

@lars18th can you create a separate issue for the spdlog issue you're seeing?

Hi @iamatypeofwalrus ,

Three comments:

  1. I'm testing on Debian 7 x64 (where the error of spdlog appears) and in a CHROOT environment with Debian 9.9 x64 (in this case the error log is different). However, in booth cases I get the same error Unauthorized client refused.
  2. As I commented before in another thread/issue every time the client can't connect over the tunnel, it prints the same in the log: Unauthorized client refused. The code really needs to be improved to distinguish the different causes.
  3. And as for the bug with Debian 9.9 I identified it with that the server closes a few seconds after the tunnel has been set up. But I don't know why, because the server log doesn't indicate anything.

Regards.

@azjps

This comment has been minimized.

Copy link

commented May 7, 2019

Just for another data point, I encounter the same backtrace attempting to connect to a remote server running RHEL6:

$ grep -i error ~/.vscode-remote/.473af338e1bd9ad4d9853933da1cd9d5d9e07dc9.log 
Error: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.18' not found (required by ~/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/node_modules/spdlog/build/Release/spdlog.node)

$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.10 (Santiago)

The same issue presumably occurs with CentOS 6.10: https://github.com/microsoft/vscode/issues/73427.

@khuongduybui

This comment has been minimized.

Copy link

commented May 7, 2019

Can I download Amazon Linux Bare Metal release 2012.03 and run it locally in a VM to investigate what's going on ? i.e. how could I investigate?

Unfortunately I can't find the image to download anymore.
However, it's basically just RHEL5 modded to run with Kernel 4.9.

@dsych

This comment has been minimized.

Copy link

commented May 8, 2019

Just for another data point, I encounter the same backtrace attempting to connect to a remote server running RHEL6:

$ grep -i error ~/.vscode-remote/.473af338e1bd9ad4d9853933da1cd9d5d9e07dc9.log 
Error: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.18' not found (required by ~/.vscode-remote/bin/473af338e1bd9ad4d9853933da1cd9d5d9e07dc9/node_modules/spdlog/build/Release/spdlog.node)

$ cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.10 (Santiago)

The same issue presumably occurs with CentOS 6.10: microsoft/vscode#73427.

Just download a newer version of libstdc++ and add it to the LD_LIBRARY_PATH link

@achhabr1

This comment has been minimized.

Copy link

commented May 8, 2019

Getting the same issue with RHEL6

[ac043s@SDNAUTOS02 .vscode-remote]$ uname -a
Linux SDNAUTOS02 2.6.32-754.6.3.el6.x86_64 #1 SMP Tue Sep 18 10:29:08 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux
[ac043s@SDNAUTOS02 .vscode-remote]$

[ac043s@SDNAUTOS02 .vscode-remote]$ grep -i error ~/.vscode-remote/.daf71423252a707b8e396e8afa8102b717f8213b.log
Error: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.18' not found (required by /home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/node_modules/spdlog/build/Release/spdlog.node)
{ [Error: ENOENT: no such file or directory, scandir '/home/ac043s/.vscode-remote/data/logs']
[ac043s@SDNAUTOS02 .vscode-remote]$

Remote configuration data at /home/ac043s/.vscode-remote

Error: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.18' not found (required by /home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/node_modules/spdlog/build/Release/spdlog.node)
at Object.Module._extensions..node (internal/modules/cjs/loader.js:731:18)
at Module.load (internal/modules/cjs/loader.js:612:32)
at tryModuleLoad (internal/modules/cjs/loader.js:551:12)
at Function.Module._load (internal/modules/cjs/loader.js:543:3)
at Module.require (internal/modules/cjs/loader.js:650:17)
at Module.patchedRequire [as require] (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/node_modules/diagnostic-channel/dist/src/patchRequire.js:14:46)
at require (internal/modules/cjs/helpers.js:20:18)
at bindings (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/node_modules/bindings/bindings.js:81:44)
at Object. (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/node_modules/spdlog/index.js:3:35)
at Module._compile (internal/modules/cjs/loader.js:702:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:713:10)
at Module.load (internal/modules/cjs/loader.js:612:32)
at tryModuleLoad (internal/modules/cjs/loader.js:551:12)
at Function.Module._load (internal/modules/cjs/loader.js:543:3)
at Module.require (internal/modules/cjs/loader.js:650:17)
at Module.patchedRequire [as require] (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/node_modules/diagnostic-channel/dist/src/patchRequire.js:14:46)
at require (internal/modules/cjs/helpers.js:20:18)
at Function.i [as __$__nodeRequire] (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:31:542)
at Object.t.createSpdLogService (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/agent/remoteExtensionHostAgent.js:213:301)
at G. (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/agent/remoteExtensionHostAgent.js:363:833)
at Generator.next ()
at /home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/agent/remoteExtensionHostAgent.js:16:388
at new Promise ()
at r (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/agent/remoteExtensionHostAgent.js:16:165)
at G._createServices (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/agent/remoteExtensionHostAgent.js:363:624)
at Function.create (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/agent/remoteExtensionHostAgent.js:363:554)
at T. (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/agent/remoteExtensionHostAgent.js:370:597)
at Generator.next ()
at /home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/agent/remoteExtensionHostAgent.js:16:388
at new Promise ()
at r (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/agent/remoteExtensionHostAgent.js:16:165)
at T.start (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/agent/remoteExtensionHostAgent.js:370:516)
at Object. (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/agent/remoteExtensionHostAgent.js:379:52)
at Function.t._safeInvokeFunction (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:20:173)
at Function.t._invokeFactory (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:20:420)
at t.complete (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:20:657)
at s._onModuleComplete (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:30:796)
at s._onModuleComplete (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:31:41)
at s._onModuleComplete (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:31:41)
at s._onModuleComplete (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:31:41)
at s._onModuleComplete (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:31:41)
at s._onModuleComplete (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:31:41)
at s._resolve (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:30:356)
at s.defineModule (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:24:768)
at r (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:28:919)
at Object.l (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:36:405)
at Function.t._safeInvokeFunction (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:20:173)
at Function.t._invokeFactory (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:20:420)
at t.complete (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:20:657)
at s._onModuleComplete (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:30:796)
at s._onModuleComplete (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:31:41)
at s._resolve (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:30:356)
at s.defineModule (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:24:768)
at r (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:31:950)
at f (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:17:524)
at Object. (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/agent/remoteExtensionHostAgent.nls.js:4:1)
at t._loadAndEvalScript (/home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:17:568)
at /home/ac043s/.vscode-remote/bin/daf71423252a707b8e396e8afa8102b717f8213b/out/vs/loader.js:17:285
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:440:3)
IP Address: 10.10.57.179
IP Address: 192.168.53.4
IP Address: 192.168.54.4
IP Address: 192.168.55.4
IP Address: 192.168.59.4
IP Address: 192.168.56.4
IP Address: 192.168.132.4
IP Address: 192.168.72.4
IP Address: 192.168.71.4
IP Address: 192.168.64.4
IP Address: 172.30.7.212
IP Address: 192.168.165.4
Extension host agent listening on 33377
{ [Error: ENOENT: no such file or directory, scandir '/home/ac043s/.vscode-remote/data/logs']
errno: -2,
code: 'ENOENT',
syscall: 'scandir',
path: '/home/ac043s/.vscode-remote/data/logs' }
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.

@MarkDHarris

This comment has been minimized.

Copy link

commented May 9, 2019

Did you modify anything to get this additional information in the log? I get this exact behavior but my log only contains (below the IP and visual studio code server banner):

Extension host agent listening on 45799
Unauthorized client refused.

and I get a new "Unauthorized client refused." entry every time I attempt to establish a connection.

I would like to enable additional diagnostics but have not found anything to help. (already enabled the remote.SSH.showLoginTerminal: true)

@lars18th

This comment has been minimized.

Copy link

commented May 10, 2019

Getting the same issue with RHEL6
....
Extension host agent listening on 33377
....
Unauthorized client refused.

Hi @achhabr1 ,
Read this: #84 (comment)
The cause is that the server is closed after it has started and it lists the listening port. However, no information about the cause it's printed at time.

@lars18th

This comment has been minimized.

Copy link

commented May 11, 2019

Hi,

Regarding this bug I discovered:

    yargs@~3.10.0:
    version "3.10.0"
    resolved "https://registry.yarnpkg.com/yargs/-/yargs-3.10.0.tgz#f7ee7bd857dd7c1d2d38c0e74efbd681d1431fd1"
    dependencies:
      camelcase "^1.0.2"
      cliui "^2.1.0"
      decamelize "^1.0.0"
      window-size "0.1.0"

Trace:
  Error: Command failed.
  Exit code: 1
  Command: sh
  Arguments: -c mocha --require coffeescript/register
  Directory: /src/qix-/node-is-arrayish
  Output:

      at ProcessTermError.MessageError (/Users/junon/.yarn/lib/cli.js:186:110)
      at new ProcessTermError (/Users/junon/.yarn/lib/cli.js:226:113)
      at ChildProcess.<anonymous> (/Users/junon/.yarn/lib/cli.js:30281:17)
      at ChildProcess.emit (events.js:127:13)
      at maybeClose (internal/child_process.js:933:16)
      at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
  • But the origin of the problem can be an incorrect detection of the platform. The same log shows at start:
Arguments:
  /Users/junon/n/bin/node /Users/junon/.yarn/bin/yarn.js test

PATH:
  /Users/junon/.yarn/bin:/Users/junon/.config/yarn/global/node_modules/.bin:/Users/junon/perl5/bin:/Users/junon/google-cloud-sdk/bi
n:/usr/local/sbin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Users/junon/bin:/Users/junon/.local/bin
:/src/.go/bin:/src/llvm/llvm/build/bin:/Users/junon/Library/Android/sdk/platform-tools:/Users/junon/n/bin:/usr/local/texlive/2017/b
in/x86_64-darwin/

Yarn version:
  1.5.1

Node version:
  9.6.1

Platform:
  darwin x64

-- Note the "Platform" value of darwin x64, as the real platform is Debian 9.9 x64.

  • Futhermore at the start of run the Remote-SSH plugin you can see this on the Output log:
> mesg: ttyname failed: Invalid argument
> 
> bash: cannot set terminal process group (3210): Invalid argument
> bash: no job control in this shell
> mesg: ttyname failed: Invalid argument

-- And note here the error about the detection of the tty.

So, here my conclusion:

  • The current code fails detecting the target platform.
  • I suggest to improve this detection, and printing a MORE CLEAR DATA ABOUT THE TARGET PLATFORM
    detected.
  • And in any case, provide a configuration tool to ENFORCE to use one specific platform, even if the detection scripts indicates a different one.

I feel a lot of errors are caused because this bug.
Regards.

@roblourens roblourens removed this from the June 2019 milestone Jun 27, 2019

@lars18th

This comment has been minimized.

Copy link

commented Jun 29, 2019

Hi @roblourens ,

By far this is the most commented topic of all the bugs in this plugin! That's why I was very surprised that it was finally eliminated from the June Milestone.

Please, note this:

  • Not in all cases, but in most cases, the problem is related to the system libraries.
  • You cannot compile statically due to the licenses of some of the tools used.
  • But... there's one thing you can do:
  1. Instead of distributing only one version of the server process, you can compile two versions. The regular version uses the system libraries, and the alternative version will use the libraries from a custom path.
  2. Then you provide a script that downloads the source of the necessary libraries (all of them) and compiles them into the target device and installs them in some custom path (i.e. /opt/vscode-ssh/libs/).
  3. In this environment, the alternative server process can be run using the custom build libraries and you do not need to redistribute any static compiled binaries.

What do you think of this idea?
Regards.

@lars18th

This comment has been minimized.

Copy link

commented Jul 3, 2019

Hi,

Will this issue be added to the JULY MILESTONE?

@loftusa

This comment has been minimized.

Copy link

commented Jul 4, 2019

Hi,

Getting this error when trying to connect to a remote container on the newest vscode-insiders.
Works fine on vscode stable.

@nhorlock

This comment has been minimized.

Copy link

commented Jul 4, 2019

Hi,

Getting this error when trying to connect to a remote container on the newest vscode-insiders.
Works fine on vscode stable.

Same here. was working completely fine until I updated today. My remote host is Ubuntu 18.04. It now fails with the connection refused error and nothing obvious in the log files. Good to hear that code stable is working though it looks like I might have to switch until this gets resolved

@emaballarin

This comment has been minimized.

Copy link

commented Jul 4, 2019

@loftusa @nhorlock
I have (I had, hopefully) the same problem, too. Exactly the same situation, both with Docker containers and other "full-fledged" hosts via ssh. Now the problem seems to be solved in the latest Insider build, which is just a downgrade of the faulty one (i.e. it's now at version 1562142486, that is the same as non-Insiders version 1.36).

@joaomoreno

This comment has been minimized.

Copy link
Member

commented Jul 4, 2019

Today's issue is microsoft/vscode#76631

@trekimann

This comment has been minimized.

Copy link

commented Jul 4, 2019

I'm having this error when trying to connect to my pi3. It was working a few days ago. I'm pretty new to all this so I'm not sure where to get the appropriate logs. I am using the latest version of insiders and have updated my pi to the latest.
image
image
image

I have tried on the non-insiders and I cant connect there but its my understanding that the pi debugging only works on the insiders at the moment.

@ataiya

This comment has been minimized.

Copy link

commented Jul 5, 2019

Just run into the problem, and this fixed it immediately:

Try the Remote SSH: Uninstall VS Code Server from Host... command and then reinstall it with Remote-SSH: Connect current window to host....

(UPDATE: using 64 bits vscode-insiders for macOS)

@roblourens

This comment has been minimized.

Copy link
Member

commented Jul 5, 2019

If you just started seeing this issue, and you are using the 32 bit VS Code build for windows, then that is microsoft/vscode#76740 and will be fixed in the next update. You can use the 64 bit build for Windows or downgrade to 1.35 to work around it. Sorry for the trouble!

@bitmonk

This comment has been minimized.

Copy link

commented Jul 7, 2019

@roblourens - thanks for the heads-up, it is unclear how to download a win32 build of 1.35.1 - I'm able to find x64 builds, MacOS and Linux builds at https://code.visualstudio.com/updates/v1_35, but no ia32 for win32, even if I manipulate the x64 download urls. :/

Update - was able to get a system installer via https://update.code.visualstudio.com/1.35.1/win32/stable.

FWIW, the win32 build is necessary until further notice on ARM64 devices like the Samsung Galaxy Book2, it sounds like once ARM64 Windows is officially supported for Chromium and Chrome, Electron, Edge, VSCode will follow.

@NomadJohn

This comment has been minimized.

Copy link

commented Jul 8, 2019

@bitmonk @roblourens thanks a lot, after switch to 1.35.1 on my Win7 x86, problem sloved.

@lars18th

This comment has been minimized.

Copy link

commented Jul 10, 2019

Hi @roblourens ,

I understand the complexity of fixing this bug. However, after using the last snapshots, I see this in the server logs:

*
* Visual Studio Code Server
*
* Reminder: You may only use this software with Visual Studio family products,
* as described in the license https://aka.ms/vscode-remote/license
*


{ errorCode: 'load',
  moduleId: 'spdlog',
  neededBy: [ '===anonymous3===' ],
  detail:
   Error: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.18' not found ...

...

IP Address: 192.168.1.32
webview server listening on 50162
Extension host agent listening on 38104
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.
Unauthorized client refused.

So, in order to send to the VSCode client a more detailed (and useful for processing) information, I suggest to change the welcome server agent message to something like:

> 
> f4eb2a0d-ddcf-45f7-99eb-afd558e9fda3==60493==48514==ERROR:"/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.18' not found"
> 

Then the client can see that the agent has an error, and it can process this error. Futhermore, if you pass the description of the error, then you can warn to the user inside the VS Code client.

What do you think?

@volvofixthis

This comment has been minimized.

Copy link

commented Jul 16, 2019

This can be used as temporarily solution for this problem. Replace this "0f3794b38477eea13fb47fbe15a42798e6129338" with your commit and add this in your .devcontainer.json:
"postCreateCommand": "sed -i 's/a.isBuilt/false/g' ~/.vscode-server-oss/bin/0f3794b38477eea13fb47fbe15a42798e6129338/out/vs/server/remoteExtensionHostAgent.js"

This helped me with Arch host and vscode 1.36.0 and custom image built from python:3 with all dependencies.

@pwwang

This comment has been minimized.

Copy link

commented Jul 16, 2019

This can be used as temporarily solution for this problem. Replace this "0f3794b38477eea13fb47fbe15a42798e6129338" with your commit and add this in your .devcontainer.json:
"postCreateCommand": "sed -i 's/a.isBuilt/false/g' /root/.vscode-server-oss/bin/0f3794b38477eea13fb47fbe15a42798e6129338/out/vs/server/remoteExtensionHostAgent.js"

This helped me with Arch host and vscode 1.36.0 and custom image built from python:3 with all dependencies.

Requires root?

@volvofixthis

This comment has been minimized.

Copy link

commented Jul 16, 2019

Requires root?

Fixed my answer.

@lars18th

This comment has been minimized.

Copy link

commented Jul 16, 2019

Hi @roblourens ,

Regarding this issue: please check my workaround described at #982.

@pwwang

This comment has been minimized.

Copy link

commented Jul 17, 2019

@volvofixthis Are you talking about container? I think this thread is about Remote-SSH that lacks old GLIBC support.

@lars18th

This comment has been minimized.

Copy link

commented Jul 17, 2019

Hi @pwwang ,

I think this thread is about Remote-SSH that lacks old GLIBC support.

Yes, this thread is about the error caused by old GLIBC libraries. And a workaround is now described: #982.

@coupfourre

This comment has been minimized.

Copy link

commented Jul 24, 2019

Looks like the vscode repo experienced a similar issue due to the use of newer OS build environments: vscode: #46193. See also: vscode: #46193. Would compiling on a system with an older version of GLIBC+ resolve this issue? Apologies if this has already been mentioned, considered, or if I have no clue what I'm talking about :P

@lars18th

This comment has been minimized.

Copy link

commented Jul 24, 2019

Hi @coupfourre ,

Would compiling on a system with an older version of GLIBC+ resolve this issue? Apologies if this has already been mentioned, considered, or if I have no clue what I'm talking about :P

Try this workaround #982 !

@peteboothroyd

This comment has been minimized.

Copy link

commented Aug 1, 2019

any update on a solution which does not require root?

@lars18th

This comment has been minimized.

Copy link

commented Aug 2, 2019

any update on a solution which does not require root?

Read this: #982 (comment)

The developers of this great extension only need to meet two requirements. When it's done we can use it in any Linux machine even without recent system GLIBC++ libraries.

@ganezdragon

This comment has been minimized.

Copy link

commented Aug 16, 2019

Has anyone had any luck installing the necessary gcc libraries via linuxbrew (which doesn't need root) ?

@JackED42

This comment has been minimized.

Copy link

commented Sep 2, 2019

I get this same problem. However it isn't the glibc issue. On OSX I can connect without any issues. From Ubuntu, I get this error message. Nothing I can see gives any more information other than unauthorized client.

Is there anything I can do to get more information on exactly what is causing it?

@boumanb

This comment has been minimized.

Copy link

commented Sep 8, 2019

Running into the same problem. See log below.
OS: Manjaro, Linux 5.1.21-1

Setting up container for folder: /home/billy/dev/laravel/first-project
Run: docker exec 636a7079f70ddb5bd40d7baabda6cdf8e430d985dd161983b28700fc0fc625db /bin/sh -c (cat /etc/os-release || cat /usr/lib/os-release) 2>/dev/null
NAME="Ubuntu"
VERSION="16.04.6 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.6 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
Run: docker cp 636a7079f70ddb5bd40d7baabda6cdf8e430d985dd161983b28700fc0fc625db:/etc/passwd -
Run: docker exec 636a7079f70ddb5bd40d7baabda6cdf8e430d985dd161983b28700fc0fc625db test -d /root/.vscode-server-oss
Run: docker exec 636a7079f70ddb5bd40d7baabda6cdf8e430d985dd161983b28700fc0fc625db /bin/sh -c set -o noclobber ; mkdir -p '/root/.vscode-server-oss/data/Machine' && { > '/root/.vscode-server-oss/data/Machine/.writeMachineSettingsMarker' ; } 2> /dev/null
Run: docker exec 636a7079f70ddb5bd40d7baabda6cdf8e430d985dd161983b28700fc0fc625db /bin/sh -c set -o noclobber ; mkdir -p '/root/.vscode-server-oss/data/Machine' && { > '/root/.vscode-server-oss/data/Machine/.copyGitConfigMarker' ; } 2> /dev/null
Run: docker exec 636a7079f70ddb5bd40d7baabda6cdf8e430d985dd161983b28700fc0fc625db test -d /root/.vscode-server-oss/bin/f06011ac164ae4dc8e753a3fe7f9549844d15e35
Run: docker exec 636a7079f70ddb5bd40d7baabda6cdf8e430d985dd161983b28700fc0fc625db test -d /root/.vscode-server-oss/extensions
Run: docker exec 636a7079f70ddb5bd40d7baabda6cdf8e430d985dd161983b28700fc0fc625db /bin/sh -c set -o noclobber ; mkdir -p '/root/.vscode-server-oss/data/Machine' && { > '/root/.vscode-server-oss/data/Machine/.postCreateCommandMarker' ; } 2> /dev/null
Run: docker exec -w / -u 0 636a7079f70ddb5bd40d7baabda6cdf8e430d985dd161983b28700fc0fc625db /bin/sh -c command -v git >/dev/null 2>&1 && git config --system credential.helper '!f() { command -v code-oss >/dev/null 2>&1 && code-oss --gitCredential $*; }; f' || true
Run: docker exec -w /root/.vscode-server-oss/bin/f06011ac164ae4dc8e753a3fe7f9549844d15e35 -e SHELL=/bin/bash -e VSCODE_AGENT_FOLDER=/root/.vscode-server-oss 636a7079f70ddb5bd40d7baabda6cdf8e430d985dd161983b28700fc0fc625db /root/.vscode-server-oss/bin/f06011ac164ae4dc8e753a3fe7f9549844d15e35/server.sh --disable-user-env-probe --port 0


*
* Visual Studio Code Server
*
* Reminder: You may only use this software with Visual Studio family products,
* as described in the license https://aka.ms/vscode-remote/license
*


IP Address: 172.20.0.4
IP Address: 172.19.0.2
webview server listening on 45423
Extension host agent listening on 33031
Run: docker exec -w /root/.vscode-server-oss/bin/f06011ac164ae4dc8e753a3fe7f9549844d15e35 636a7079f70ddb5bd40d7baabda6cdf8e430d985dd161983b28700fc0fc625db /bin/sh -c echo 33031 >.devport


----------------------
Published Ports:
22/tcp -> 0.0.0.0:2222
----------------------

Unauthorized client refused.
Unauthorized client refused.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.