Failed to connect to remote extension host server

[wreiske]

Issue Type: Bug

Remote Development authenticates fine but shows an error and won't let me continue.

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

The remote server is CentOS release 6.10 (Final).

uname -a
Linux server.com 2.6.32-696.18.7.el6.x86_64 #1 SMP Thu Jan 4 17:31:22 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

bash --version
GNU bash, version 4.1.2(2)-release (x86_64-redhat-linux-gnu)

VS Code version: Code - Insiders 1.34.0-insider (daf71423252a707b8e396e8afa8102b717f8213b, 2019-05-06T22:07:35.830Z)
OS version: Darwin x64 18.5.0
Fetching remote diagnostics for 'SSH: server.com' failed: Connection error: Unauthorized client refused.

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz (8 x 2500)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: enabled rasterization: unavailable_off surface_synchronization: enabled_on video_decode: enabled webgl: enabled webgl2: enabled
Load (avg)	2, 3, 3
Memory (System)	16.00GB (0.27GB free)
Process Argv
Screen Reader	no
VM	0%

Fetching remote diagnostics for 'SSH: server.com' failed: Connection error: Unauthorized client refused.

Extensions: none

[wreiske]

Ahh, possibly a duplicate of #84 and should be moved there.

[thernstig]

@wreiske Try to check here https://code.visualstudio.com/docs/remote/troubleshooting#_enabling-alternate-ssh-authentication-methods if enabling remote.SSH.showLoginTerminal possibly gives you another hint why it fails.

[athaks]

uname -a
Linux 2.6.32-754.12.1.el6.x86_64 #1 SMP Tue Apr 9 14:52:26 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

bash --version
GNU bash, version 4.1.2(2)-release (x86_64-redhat-linux-gnu)

e23315f6-185a-4a99-baa5-e4110203513c==14385==

[Chuxel]

This is a dupe of #103 and occurs due to glibc being outdated on CentOS 6. See here for a workaround.