Closed spekulatius closed 4 years ago
Can you specify the config file too? And add the debug logs (via -vvv
) from a working SSH connect?
Hey @darthShadow,
while preparing the outputs I've stumbled upon the issue. The service uses a non-standard port and missed that in my config. Sorry! Thanks for replying and indirectly helping to resolve the issue!
Cheers, Peter
Sorry if that's a necro -- not sure if I should make a new issue. I have the same problem, the SSH config has been double-checked, including issuing the command I imagine rclone
would issue, and that one works. Port is standard 22, tried with the "include insecure ciphers" option as well, still can't connect.
This happened abruptly yesterday or the day before, and I can't seem to isolate the reason. My Linux server has been upgraded as well recently but since normal SSH succeeds just fine I don't think this is its fault.
rclone is at 1.56.2
currently.
Any pointers?
@dimitarvp probably best to make a new issue and fill in the details - thanks!
Hey,
I think I've found a bug with rclone using SFTP:
What is the problem you are having with rclone?
I've set up an account with a backup provider. The provider offers SSH/SFTP uploads. I've configured the SSH key and can connect with
ssh user@host
andsftp user@host
.The same with rclone doesn't work:
I've tried without
key_file
and with mykey_file
as an absolute path - both fail.What is your rclone version (output from
rclone version
)Which OS you are using and how many bits (eg Windows 7, 64 bit)
Elementary 5 (based on Ubuntu 18.04)
Which cloud storage system are you using? (eg Google Drive)
SFTP
The command you were trying to run (eg
rclone copy /tmp remote:tmp
)As to expect, other commands such as copy lead to the same issue.
A log from the command with the
-vv
flag (eg output fromrclone -vv copy /tmp remote:tmp
)Please let me know if you need any more information.