Loading Profile...
No SFTP connection after upgrade to ExpanDrive 2.0
ExpanDrive 1.3.4 : everything ok. ExpanDrive 2.0 can’t access (same) SFTP Server, asks for password again and again. No Connection.
Tried following steps:
- tried ExpanDrive 1.3.4 = working
- Edited "/Users/USERNAME/.ssh/known_hosts" = no connection (asked for password)
- deleted drive and added again = no connection (asked for password)
- reboot of system = no connection (asked for password)
- ExpanDrive 2.0 still refuses to connect, asks for password again and again
- ExpanDrive 1.3.4 = working
Please help.
Tried following steps:
- tried ExpanDrive 1.3.4 = working
- Edited "/Users/USERNAME/.ssh/known_hosts" = no connection (asked for password)
- deleted drive and added again = no connection (asked for password)
- reboot of system = no connection (asked for password)
- ExpanDrive 2.0 still refuses to connect, asks for password again and again
- ExpanDrive 1.3.4 = working
Please help.
I’m frustrated
4
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The best solution from the company
-
Blumenberg, I understand that you’re frustrated. I promise we’re going to do everything we can to fix things, and it’s very unlikely that it will take us even a single week to do so. ExpanDrive 2.0 has been very heavily tested. ExpanDrive bridges two application layers, a filesystem and a file transfer client, that are impossible to test completely. We don’t have access to every SFTP server that’s ever been deployed, and we don’t have every program that might try to do crazy or nonsensical things to our filesystem.
Now, about the issue you’re seeing. It looks like OpenSSH is unhappy about your known_hosts file. It’s saying that you have two different signatures saved for the same server, one saved by the server’s hostname, and another saved by the server’s IP address. If you open ~/.ssh/known_hosts in a text editor and delete line 1 and line 12 I think it will fix this problem. That will remove both signatures, and OpenSSH will automatically add the server’s correct signature next time you connect.
It may not seem like it, but this is actually a feature improvement in ExpanDrive 2.0. This is an important warning. The hostkey is what lets ssh know that it’s really connecting to the correct server, and that no one is listening to or messing with the connection. Obviously we need to make ExpanDrive do a better job explaining what is going on when this situation comes up.
Paul and Edwin, there are two things that you can do to help us help you. First, check to see if ExpanDrive printed anything in Console.app. Second, try to connect to your servers using the sftp command line tool (sftp username@host). If you email us that information at support@expandrive.com we’ll get back to you right away.
I’m confident
The company says
this solves the problem
-
Inappropriate?I had a similar problem, but with a twist - I've installed 2.0 on two different systems.
One of them exhibited this problem - password over and over - the other one - with an identical setup - connected. (But then I got into the problem where I could not list anything below the root level.)
In my case, both connections were as root connecting to the / level. -
Inappropriate?Blumenberg -
any trouble connecting from the commandline using sftp username@host ? Are you using keys or passwords for auth? Do you know if keys have been set up? Anything interesting happening in Console.app?
We'll get this fixed, might take a minor rev. We'll likely have a couple bumps in the next week or two sorting out issues we haven't been able to fully test.
-Jeff1 Comment Add a comment
This solves the problem
-
"Any" trouble connecting from terminal? well, kind of... I got :"Warning: the RSA host key for 'HOSTNAME' differs from the key for the IP address 'x.x.x.x'
Offending key for IP in /Users/USERNAME/.ssh/known_hosts:1
Matching host key in /Users/USERNAME/.ssh/known_hosts:12
Are you sure you want to continue connecting (yes/no)? yes
Password: PASSWORD
sftp> "
So it’s working from the terminal AND ExpanDrive 1.3.4 but not w/ ExpanDrive 2.0 — or should I say ExpanDrive-Early-Alpha-Not-Very-Close-To-Final? That sounds to me more realistic when you say:
"We'll likely have a couple bumps in the next week or two sorting out issues we haven't been able to fully test."
If I sound frustrated and sarcastic you’re right; I immediately shelled out the money for the upgrade to get a speed bump and a (little) change of the -- not really important, because you don’t "need" it -- UI, and all you get is a "broken" app and support saying we need more week(s) to fix the problem because we haven’t test the app fully (yet).
And remember: ExpanDrive 1.3.4 IS still working (no connection problems at all). -
Inappropriate?I have the same issue. Drive fails to mount - no error reported. ExpanDrive 1.3.4 works fine. I'm now an unhappy customer :-(
-
Inappropriate?Blumenberg, I understand that you’re frustrated. I promise we’re going to do everything we can to fix things, and it’s very unlikely that it will take us even a single week to do so. ExpanDrive 2.0 has been very heavily tested. ExpanDrive bridges two application layers, a filesystem and a file transfer client, that are impossible to test completely. We don’t have access to every SFTP server that’s ever been deployed, and we don’t have every program that might try to do crazy or nonsensical things to our filesystem.
Now, about the issue you’re seeing. It looks like OpenSSH is unhappy about your known_hosts file. It’s saying that you have two different signatures saved for the same server, one saved by the server’s hostname, and another saved by the server’s IP address. If you open ~/.ssh/known_hosts in a text editor and delete line 1 and line 12 I think it will fix this problem. That will remove both signatures, and OpenSSH will automatically add the server’s correct signature next time you connect.
It may not seem like it, but this is actually a feature improvement in ExpanDrive 2.0. This is an important warning. The hostkey is what lets ssh know that it’s really connecting to the correct server, and that no one is listening to or messing with the connection. Obviously we need to make ExpanDrive do a better job explaining what is going on when this situation comes up.
Paul and Edwin, there are two things that you can do to help us help you. First, check to see if ExpanDrive printed anything in Console.app. Second, try to connect to your servers using the sftp command line tool (sftp username@host). If you email us that information at support@expandrive.com we’ll get back to you right away.
I’m confident
The company says
this solves the problem
-
Inappropriate?Jon, first of all thanks for the really fast and detailed response.
After I wrote my last complain I talked to my webhoster and explained them my ssh-keys problem and they asked for a screenshot which I send them...
Anyway, you asked for deleting Lines #1 and #12 -- and I was a bit more for: I deleted all the lines (did a backup to be sure) -- and for now it seems ExpanDrive 2.0 IS working.
If I gonna stumble upon more "difficulties" or "bugs" I’ll let you know.1 Comment Add a comment
This solves the problem
-
I’m really glad you got things working. We’re definitely going to try to make the hostkey behavior more user friendly. I’m sorry you had to be the first to run into this issue.
-
Inappropriate?Well sounds like my problem is perhaps different to Blumenberg's. Mine works fine from terminal
> sftp edwin@ssh7.ukshells.co.uk
Connecting to ssh7.ukshells.co.uk...
Password:
sftp>
And as well as this sftp, I use ssh shell sessions regularly and there are no issues. I've now downgraded to ExpanDrive 1.3.4, but I'm a bit annoyed that I've paid money for nothing (yet).
Guess I have to be patient for the team to fix bugs......
I’m annoyed
1 Comment Add a comment
This solves the problem
-
I'm experiencing the same problem. Both sftp and shell access work fine via Terminal, but attempts to connect through ExpanDrive pop up an error window with no explanation. I don't see anything in Console.app filtering on 'Expan'. Fortunately, I haven't paid anything for this yet. (Evaluating 2.0, never tried 1.3.4.)
-
Inappropriate?add me to the list......
-
Inappropriate?Add me to the list of people having problems connecting to servers via SFTP after upgrading to 2.0.1. I'm fairly certain I wasn't having this problem at the 2.0 level. I've since downgraded to 1.3.4 and connect with no problems. I've e-mailed support@expandrive.com with a log of what Expandrive says is happening, but haven't heard back in a couple of days. Hopefully it'll get sorted out soonish.
I’m unsure
-
Inappropriate?Try this and it should fix it:
Download macfuse and just do a install right over the top of the old one.. aka just install it again and it should work. I don't know why but the update to 2.0 and then to 2.1 hoses macfuse1 Comment Add a comment
This solves the problem
-
Completely removing MacFUSE and reinstalling it did not resolve my issue. I even tried using the beta 2.1.5 of MacFUSE and still nothing. Guess I'll go back to 1.3.4 for the time being.
-
Inappropriate?maybe try cleaning caches, repairing permissions then updating the macfuse install.
-
Inappropriate?Version 2.0.2 seems to have fixed my issues - on both different servers that I connect to.
Yay!
If you are still having trouble, I recommend trying 2.0.2.
I’m relieved
EMPLOYEE
EMPLOYEE
