- Retest
- Minor
Tagging @limetech because of recent discussions. With respect and no sarcasm (seriously) I request that you read this post, if you see your name tagged. I want to help fix this since unRAID is currently unusable for me. It's why I've tagged this as Urgent.
Upgraded to 6.6.3 to try and diagnose issues, if they came back.
The SFTP issues I logged in another post relating to 6.6.0 are still there (the other post is at the bottom of this one).
I use a variety of tools/utilities to carry out various things over SFTP.
- Backups with Duplicati. Connection is established, but all file transfers fail.
- File transfers with FileZilla. Connection is established and I can login and browse, but can't transfer anything. The transfer all sits there on 0% and never get any further.
- File transfers with gFTP. Works.
All 3 of the above methods were faultless on 6.5.3 and nothing has changed on the client ends. Logic dictates that it's something on the unRAID side.
That was before.
In the post linked further down, @limetech suggested to do the following:
wget http://slackware.cs.utah.edu/pub/slackware/slackware64-current/slackware64/n/openssh-7.9p1-x86_64-1.txz
upgradepkg openssh-7.9p1-x86_64-1.txz
I did that and now I can't login to my unRAID server *AT ALL* over SSH.
From the client perspective, this is what I got at first, when trying to SSH into the server.
~ » ssh [email protected]
ssh_exchange_identification: read: Connection reset by peer
I restarted sshd using the following, thinking that maybe something didn't get reloaded properly.
/etc/rc.d/rc.sshd restart
That didn't fix it.
So I then disabled SSH from the GUI, then re-enabled SSH from the GUI. Now I get this when I try to login via SSH:
~ » ssh [email protected]
ssh: connect to host 192.168.1.85 port 22: Connection refused
Looks to me like sshd isn't even listening anymore. It's worth nothing that SSH *excluding* SFTP was fine until I upgraded OpenSSH as per above.
I can still open a terminal from the GUI, however. Trying to restart sshd from the GU terminal, now, shows this:
OpenSSL version mismatch. Built against 1010100f, you have 1010009f
OpenSSL version mismatch. Built against 1010100f, you have 1010009f
I can Google and fix that, I'm sure, but why would that even happen?
Honestly, I'm at a bit of a loss here. I thought I was doing the right thing by upgrading to 6.6.3 in order to diagnose issues and provide feedback/logs, but now I have an unRAID system I can't use. I can't even login to it to get logs or diagnostics issues. It is a headless box that has no monitor or keyboard attached. I know that's nobody's problem but mine, but it is a problem, nonetheless.
Can anyone help? Please?
-
1
