Automatic backup via SFTP not working?
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Team,
Over the past few weeks I tried a couple of time to do an automatic backup via SFTP.
See also attached screenshots:
While I can browser on the SFTP-server and the controller accepts the config, the backup failes.
Any suggestion where to start troubleshooting? Or perhaps even a fix?
Thank you - Will
=====
=====
=====
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@ITV well, this confirms I was right. If you create a folder with sudo, the owner is root user and logicalky your user has no write permission. At the end, you did not have write permissions.
To resolve it, it should have been sufficient to run chown and make your user owner of that folder.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Assuming that either of the suggested would be true:
Would browsing through the files and folders work?
Would a wrong username and/or password be accepted?
Yes - I checked the log. It says:
Accepted password for will from 192.168.139.235 port 37884 ssh2
pam_unix(sshd:session): session opened for user will(uid=1000) by (uid=0)
The folder I'm writing to is: /home/will/omada.
Any other suggestions?
Cheers - Will
- Copy Link
- Report Inappropriate Content
We just had a test on our lab with controller version V5.6, and I did not see the same issue.
Could you please try the new version controller also?
- Copy Link
- Report Inappropriate Content
@ITV there is not much info about the error in screenshot, obviously it fails to save the archive. First on my mind would be permissions, are you sure that ssh user you are using has write access to the folder?
I do not understand why tplink still did not introduce authentification by ssh key instead of username and password, in fact its just one config line to be uncommented. That is main reason why I do not use it, on all my devices password authentication is disabled for security reasons.
- Copy Link
- Report Inappropriate Content
Just gave this another try and made it work.
The solution is a rather strange one:
The owner and rights of the Omada-folder matches the user logging in for the backup.
However, it seems not be enough to make it work.
When I deleted the Omada-folder and re-created it without sudo, it works.
While the owner and rights where the same as the original one.
Any ideas of a possible explenation?
Cheers - Will
- Copy Link
- Report Inappropriate Content
@ITV well, this confirms I was right. If you create a folder with sudo, the owner is root user and logicalky your user has no write permission. At the end, you did not have write permissions.
To resolve it, it should have been sufficient to run chown and make your user owner of that folder.
- Copy Link
- Report Inappropriate Content
@btx | it certainly looks that way - sorry for the mistake on my site... 
- Copy Link
- Report Inappropriate Content
@ITV no need for excuse ;), we all have to make mistakes for ability to learn something.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1311
Replies: 8
Voters 0
No one has voted for it yet.