You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 27, 2024. It is now read-only.
I receive this issue/error in the Diagnostics window, it is apparent that the bundled SSH executables are trying to write/read to Unix file paths, and there is no documentation or configuration to modify this behavior.
I reviewed several issues that appeared similar, one mentioning that a system restart resolved the problem, but that did not remediate my issue.
Can't connect to remote machine!
Exception was: There was a problem with SshConnection! Failed to create SSH master socket!
Diagnostic info: Starting process 'ssh.exe -M -f -N -o ServerAliveInterval=60 -o ControlPath=C:/Users/REDACTED~1/AppData/Local/Temp/ci3k1z/ssh_socket -p 22 REDACTED@REDACTED'
Starting process 'ssh.exe -M -f -N -o ServerAliveInterval=60 -o ControlPath=C:/Users/REDACTED~1/AppData/Local/Temp/ci3k1z/ssh_socket -p 22 azureuser@REDACTED'
stdout:
=============================== stderr: ===============================
Could not create directory '/home/REDACTED/.ssh'. Failed to add the host to the list of known hosts (/home/REDACTED/.ssh/known_hosts). \S Kernel \r on an \m Permission denied (publickey).
Working in a classified environment so the remote system IP and my Azure AD/Windows User Name are redacted accordingly.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I receive this issue/error in the Diagnostics window, it is apparent that the bundled SSH executables are trying to write/read to Unix file paths, and there is no documentation or configuration to modify this behavior.
I reviewed several issues that appeared similar, one mentioning that a system restart resolved the problem, but that did not remediate my issue.
Working in a classified environment so the remote system IP and my Azure AD/Windows User Name are redacted accordingly.
The text was updated successfully, but these errors were encountered: