Currently, establishing an SSH connection from Visual Studio fails with a key exchange error. The cause is an incompatibility between the SSH key exchange algorithms offered by the CF SSH proxy and the SSH client used by Visual Studio (SSH.NET).
Specifically:
The Diego SSH proxy currently appears to offer only Curve25519-based KEX algorithms.
Visual Studio (SSH.NET) does not support these algorithms.
As a result, there is no common key exchange algorithm, and the SSH handshake aborts.
OpenSSH clients work, but Visual Studio does not.
TAS 10.3.x
The Diego SSH proxy indeed only support the Curve25519-based KEX algorithms.
The algorithm is also outlined in the below document:
There is a tool specifically designed to debug the CF app from Visual studio available at
Also description on the how to use the tool is available here