vesta_mtl wrote:It is possible that there is no backup with the current date. The script needs to run on the same day that the backup is created, because it looks for a backup with the current date in its name.

I did the whole process again.
Even with a new backup, after doing the test the error appears.

I can send the file to the dropbox, but when I run the command the error appears.

I find it strange every time I type the command sh /usr/local/bin/send_site_backup_files_to_dropbox.sh it requests the token and after typing the token gives error.

ruinzaO wrote:Friend, thanks for the great work!
I noticed that my backups were added "admin.2018-01-15_05-10-12.tar" the time, so the file is not being renamed to admin.tar in the dropbox, could you add a fix in the script?

Many thanks and I'm sorry, I'm using google.

Yes, the script needed to be updated because Vesta now includes the time in the backup filename. I have updated my original post and the script should now work with the old Vesta (only yyyy-mm-dd in filename) and the new Vesta (yyyy-mm-dd_hh-mm-ss in the filename).

Let me know if you have any trouble. Your Google translation is excellent! :-)

Thanks for the answer!
Friend in setup this error appears.
/dropbox/dropbox_uploader.sh: line 1559: : No such file or directory

Am I doing something wrong?

There is an issue with the latest release of the Dropbox script. I have updated my instructions (the "curl" command above) to retrieve the older version of the script from github and it should work again.