Closed mAAdhaTTah closed 9 years ago
Do you have a passphrase on your private key by any chance? Dropzone 3 doesn't currently handle this case correctly.
Otherwise - paste me the debug console output and I'll see what else it could be.
I do, though I added the key to they keychain so I'm not entering that in every time.
That passphrase will be the problem. I'm planning to fix this on the SCP action soon. If you want to have a hack around - the scp lib that Dropzone uses is at /Applications/Dropzone 3.app/Contents/Actions/lib/scp.rb I'm not exactly sure how this will be resolved. I guess I'll have to make it so you can enter your passphrase when configuring the SCP action initially. If you have any thoughts I'm all ears.
I'm still learning ruby, so I don't know how much help I can be, but is there some way to hook into the keychain?
(Unrelated aside, but TwicPic is no longer shutting down, so you can probably add that back in.)
Oh, neat will do - thanks! And regarding the passphrase - Yeah, I think Dropzone will have to save its own copy of the passphrase in the keychain to hand to the ruby SCP lib for use during uploading. It's definitely on my list of things to look at.
As @mAAdhaTTah I have a passphrase on my private keys and the keychain store passwords for them and Its work without problem. (maybe its could be a problem with the icon :D) You left the password field blank ? The remote folder is correctly set and the directory exists on the server ? Have you any error message (dropzone console and server) ?
@mAAdhaTTah Sorry I'm so late getting back about this. I've just updated the SCP action and it should now work with private keys that have a passphrase. If you wouldn't mind testing it works now, you can re-install the updated SCP action from https://aptonic.com/dropzone3/actions/install.php?bundle_name=SCP%20Upload
Make sure you test it with the latest version of Dropzone (currently 3.2.3). I'd love to hear if this fixes it for you :smile:
Yup, works. Thanks!
SCP is returning an authentication error, but ssh'ing in works fine:
ssh -p 2550 username@host.name.net
works fine, but doing the same with SCP fails.