3 ms·

Can’t connect unfortunately. debug1: Sending environment. debug1: channel 2: setting env LANG = "en_US.UTF-8" debug2: channel 2: request env confirm 0 debug1:

by Ocha 4mo ago

Can’t connect unfortunately. debug1: Sending environment. debug1: channel 2: setting env LANG = "en_US.UTF-8" debug2: channel 2: request env confirm 0 debug1: channel 2: setting env LC_TERMINAL = "iTerm2" debug2: channel 2: request env confirm 0 debug1: channel 2: setting env LC_TERMINAL_VERSION = "3.6.10" debug2: channel 2: request env confirm 0 debug1: channel 2: setting env LC_ALL = "en_US.UTF-8" debug2: channel 2: request env confirm 0 debug2: channel 2: request shell confirm 1 debug2: channel_input_open_confirmation: channel 2: callback done debug2: channel 2: open confirm rwindow 8388608 rmax 32768 debug1: mux_client_request_session: master session id: 2 debug2: channel_input_status_confirm: type 99 id 2 debug2: PTY allocation request accepted on channel 2 Connection to late.sh closed by remote host.

bl4ckbe4r 4mo ago
Can you try one more time? And if still failing, are you ok with trying the CLI? CLI is a little more bulletproof, have its own ssh client inside.
- Ocha 4mo ago
  Did some debugging. It works after I disabled compression and control master. I didn’t like CLI, since it didn’t pick up my default ssh key from the agent.
- bl4ckbe4r 4mo ago
  the CLI also have some args to use, like --key or --ssh-mode :)