Which makes me think those error/warning messages are my issue, and to continue troubleshooting from there.
Received disconnect from 10.0.1.42 port 63866:11: disconnected by userĭisconnected from user capin 10.0.1.42 port 63866 Starting session: subsystem 'sftp' for capin from 10.0.1.42 port 63866 id 0ĭebug1: session_exit_message: session 0 channel ĭebug1: session_exit_message: release channel 0 scping a file to ssh server of some sort is to stop the currently running server and start it in debug mode from a terminal in a foreground process (it may be possible start another ssh server to prevent stopping the existing one if an ssh config file is set properly (not something i've looked into)), but for my use, stopping the existing server and launching a new instance of it in debug works wonders ?♀️, so running sshd -dĪnd then attempting to send a file to the server i see the following lines in STDOUT debug1: server_input_channel_req: channel 0 request subsystem reply 1ĭebug1: session_by_channel: session 0 channel 0ĭebug1: session_input_channel_req: session 0 req subsystemĭebug1: subsystem: cannot stat /usr/local/Cellar/openssh/8.8p1/libexec/sftp-server: No such file or directoryĭebug1: subsystem: exec() /usr/local/Cellar/openssh/8.8p1/libexec/sftp-server So where to go from here, fortunately i've experienced issues with ssh in the past, and IMHO the easiest way to get a sane message on why a certain ssh related task ie. That didn't really give me much to work with and adding -VVVV didn't show any glaring issues, though using -VVVV when stuff like this isn't working is not something that i look at everyday (may have missed something).Īll that said, the above commands of sudo sshd -t printed nothing to STDOUT. I got bit ? by this issue today trying to scp a file from one computer on my LAN to my macbook, and got presented with the lovely message to STDOUT scp: Connection closed I'll throw my hat in the ring on this one. I tried looking in the various host, config, ssh files but I didn't mange to solve much. Ssh_exchange_identification: Connection closed by remote host If I do a verobse scp, it gives me this: Executing: program /usr/bin/ssh host xx.xx.xx.x, user User, command scp -v -t /Users/Userĭebug1: Reading configuration data /etc/ssh/ssh_configĭebug1: Connecting to xx.xx.xx.x port 22.ĭebug1: identity file /home/user/.ssh/identity type -1ĭebug1: identity file /home/user/.ssh/identity-cert type -1ĭebug1: identity file /home/user/.ssh/id_rsa type -1ĭebug1: identity file /home/user/.ssh/id_rsa-cert type -1ĭebug1: identity file /home/user/.ssh/id_dsa type -1ĭebug1: identity file /home/user/.ssh/id_dsa-cert type -1ĭebug1: identity file /home/user/.ssh/id_ecdsa type -1ĭebug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
If I perform scp backwards (copying from mac to server) it works just fine, and it works fine if I do it form another mac.
We focus on putting the right people in the right places by pairing you with a position that fits your needs, offers competitive compensation, and supports your growth as a health care leader. I'm working on a remote server through Mac terminal, since I updated it to OSX 10.10 from 10.5 I started receiving this message every time I try to scp from the server to my computer: ssh_exchange_identification: Connection closed by remote host At SCP Health, we empower physicians, nurse practitioners, and physician assistants like you to pursue a career that aligns with your long-term goals.