Jump to content
  • 6.6.3 - Ongoing SFTP issues


    digitalformula
    • 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 root@192.168.1.85

    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 root@192.168.1.85
    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?

     

     

     

    • Like 1


    User Feedback

    Recommended Comments

    I have fixed being unable to SSH into the unRAID box by rolling back to OpenSSH-7.7.  However, this shouldn't have happened in the first place.

     

    The other SFTP issues remain as per the original post above.

     

    @limetech FYI, in particular.

    Edited by digitalformula

    Share this comment


    Link to comment
    Share on other sites

    You can simply reboot to get back to stock 6.6.3 with stock version of SSH.  The version of SSH you tried to upgrade to required a newer version of OpenSSL:

     

    wget https://mirrors.slackware.com/slackware/slackware64-current/slackware64/n/openssl-1.1.1-x86_64-1.txz

    upgradepkg openssl-1.1.1-x86_64-1.txz

     

    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

     

    • Like 1

    Share this comment


    Link to comment
    Share on other sites
    1 minute ago, eschultz said:

    You can simply reboot to get back to stock 6.6.3 with stock version of SSH.  The version of SSH you tried to upgrade to required a newer version of OpenSSL:

     

    wget https://mirrors.slackware.com/slackware/slackware64-current/slackware64/n/openssl-1.1.1-x86_64-1.txz

    upgradepkg openssl-1.1.1-x86_64-1.txz

     

    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

     

    Thanks @eschultz - good info.  I forgot unRAID does that sort of stuff in RAM.

    Share this comment


    Link to comment
    Share on other sites

    @limetech @eschultz

     

    Ok, check this out.

     

    - OpenSSH 7.7 wasn't working on unRAID 6.6.3 (for me)

    - OpenSSH-7.9 broke everything, as mentioned above.

     

    Rolling back to openssh-7.7p1-x86_64-1_slack14.2.txz has fixed it.  I can now backup using Duplicati and I can transfer files using FileZilla.

     

    I'm interested to hear your thoughts on this.

    Share this comment


    Link to comment
    Share on other sites
    12 minutes ago, eschultz said:

    You can simply reboot to get back to stock 6.6.3 with stock version of SSH.  The version of SSH you tried to upgrade to required a newer version of OpenSSL:

     

    wget https://mirrors.slackware.com/slackware/slackware64-current/slackware64/n/openssl-1.1.1-x86_64-1.txz

    upgradepkg openssl-1.1.1-x86_64-1.txz

     

    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

     

     

    This has allowed OpenSSH-7.9 to work.  Thanks @eschultz - this info should be posted to a knowledge base, or something similar.

    Share this comment


    Link to comment
    Share on other sites

    Thanks for testing.  It sounds like our version of OpenSSH 7.7 with the HPN patches are causing issues for certain users/apps.  We'll most likely upgrade OpenSSL and OpenSSH to the latest in the next release.

    Share this comment


    Link to comment
    Share on other sites
    3 minutes ago, eschultz said:

    Thanks for testing.  It sounds like our version of OpenSSH 7.7 with the HPN patches are causing issues for certain users/apps.  We'll most likely upgrade OpenSSL and OpenSSH to the latest in the next release.

    Sure, no problem.

     

    Fortunately the OpenSSH 7.7p1 rollback got me to a place where I could do this, otherwise I was heading for 6.5.3 rollback again.

    Share this comment


    Link to comment
    Share on other sites

    FYI: in upcoming 6.6.4 release we updated openssh and openssl:

     

    - openssh: version 7.9p1 [without HPN patches]
    - openssl: version 1.1.1
    - openssl-solibs: version 1.1.1

     

    Share this comment


    Link to comment
    Share on other sites

    Good work here @digitalformula  @eschultz

    Though I just wanna notice you that the OP on this issue below is not the same OP as here. So don't quite get it why you did close it, but I don't mind personally because as I see it these are related. @limetech

     

    Edited by truetype
    tagged limetech correctly

    Share this comment


    Link to comment
    Share on other sites


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.