Hello Richard,
You don’t need to compress the file, just upload it as is to the /var/www/html/wp-content/darwin-backup and go to the Darwin Backup / All Backups – it should appear in the list, then click Restore.
Please let me know how it worked. Then I will tell you a simpler way to do a restore )
Dear Alex
I had to Tar/UnTar the file as wget does not support transfer of a .php file. Tried renaming the file and copying it which was much faster. Access denied problem has gone, but using default settings, nothing happens when I press “Restore Now”
Ok, I will get back to you soon.
Sorry for late answer, I was in transit today. So my bet is that you trying to wget the archive by the link you’ve got in the email directly from the remote host. It should not and will not work like that – it is insecure to allow to download archives of your site, because wget is not authorized in wordpress, or please correct me if I am wrong in my suppositions. The process should be as follows:
1. Download archive to your computer
2. Upload the file to remote server
3. Point your browser to it, you don’t even need WordPress installed
WBR,
Alex
Sorry Alex, I was in meetings all yesterday. The reason I am using WGet is because the backup files are around 1.7Gb and to copy them to my local PC and upload them again would take around 1 day with my current internet connection. WGet takes less than 10 seconds to move form server to server.
I am not sure that changing the suffix to enable the copy and then renaming the file once copied should make any difference to it. I ensure that I chown the file to www-data:www-data, but nothing happens when I press restore.
I can try and set up an FTP server between the two and move files that way.
The matter is becoming more urgent as the test server keeps getting database connection errors which is causing delays in deployment.
All the best
Richard
Can you please contact me privately at aguidrevitch at gmail.com ?
The problem was in broken CloudFlare javascript minifier, reproducible only over HTTPS. Addressed in 1.1.23
Thank you, @lorddunvegan, for reporting this one and helping me investigate. Really appreciated