NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Rsync over SSH to Digital Ocean Droplet
Hi, when stting up a backup job I am struggling to get my Ultra6 to connect to my remote Digital Ocean Droplet , so it can download ald locally store backups from there. I have added the SSH publ...
ArchPrime wrote:
I can see my connection attempts, but that a different port is being tried each time, and none of these are the port 22 I actually set in ReadyNAS.
I think you are seeing the source port in the status, and not the destination port.
ArchPrime wrote:
I have added the SSH public key given to me by ReadyNAS to Digital Ocean SSH keys (copy-pasting in to the 'add new SSH key dialog in Digital Ocean Dashboard from the public key txt file that ReadyNAS generated) and have given that key the name 'ReadyNAS' (just for originality)
Perhaps try running rsync manually from the NAS using ssh. Log in as root on the NAS. DigitalOcean does have a tutorial here: https://www.digitalocean.com/community/tutorials/how-to-copy-files-with-rsync-over-ssh but it runs in the other direction (assuming you are logged into the origin server, and you are logging into the destination server).
FWIW, it appears that you might not have an account with the username ReadyNAS set up on the DigitialOcean server.
Hi thanks - looks like you were on to something with missing 'ReadyNAS' account.
I tried and apparently succeeded in adding an account by this name in Linux, but still no luck - but when I tried logging in as 'root' instead from ReadyNAS, the connection tested as ok. However I was not able to browse for the source directory (browse button was greyed out)
Manually enetering the source path, then running a backup it looks like remote directory and contents were found, but copying failed; giving 'Disk quota exceeded (122)' error.
The selected directory to sync contains only 90mb, and to my knowledge I have not set any quotas at source or destination.
Where is this error likely comming from?
One possibly relevent clue - when I use PuTTY to acess the Digital Ocean droplet server as root, I have to supply a pass phrase related to my root SSH key to log in . Supplying of passphrases does not even seem to be an option from ReadyNAS. Does this sound relevent?
ArchPrime wrote:
Hi thanks - looks like you were on to something with missing 'ReadyNAS' account.
I tried and apparently succeeded in adding an account by this name in Linux, but still no luck - but when I tried logging in as 'root' instead from ReadyNAS, the connection tested as ok. However I was not able to browse for the source directory (browse button was greyed out)
To be clear, I think this account is needed on the Digital Ocean server, not the NAS. The key also needs to be connected to this account. (that is, placed into the account's ~/.ssh/authorized_keys).
ArchPrime wrote:
One possibly relevent clue - when I use PuTTY to acess the Digital Ocean droplet server as root, I have to supply a pass phrase related to my root SSH key to log in . Supplying of passphrases does not even seem to be an option from ReadyNAS. Does this sound relevant?
Could be. Have you checked the service status on the server when you are using root?
sudo service ssh status
ArchPrime wrote:
Manually entering the source path, then running a backup it looks like remote directory and contents were found, but copying failed; giving 'Disk quota exceeded (122)' error.
The selected directory to sync contains only 90mb, and to my knowledge I have not set any quotas at source or destination.
Where is this error likely coming from?
You were copying to the ReadyNAS? If so, what was the destination path?
Thanks Stephen
I set up 'ReadNAS' as a username on the Digital Ocean Server (I think) but may not have pulled this off correctly - certianly did not manage to connect to the server from the ReadyNAS device using this user name. (I should probably have picked a different name to avoid confusion!). Not all of the instructions for adding a new user account that I found online worked as describedI gave up on that and ended up adding the ReadyNAS device's ssh public key to the authorized_keys file on the Digital Ocean server for my root account - which at least now allows me to connect as as user 'root' from my ReadyNAS device, Even if I can get no further.
Yes, I am trying to initiate a connection from ReadyNAS device, in order to retrieve the contents of a folder on the Digital Ocean server and save a copy of these to ReadyNAS shared folder
*** EDIT ***
While I was typing this response, it seems the problem has somehow self corrected - I had set up backup interval to once per day, and it so happened that this backup just executed itself automatically, and succeeded! I have no idea why it failed when initiated manually before.
I wonder if being simultaneously logged in as root from my PC via PuTTY helped in some way, or issuing that check status command you suggested somehow shook something loose?:
sudo service ssh status
Either way, much appreciate your help!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
