Well, I was getting the same false http status (401) except mine was 401 instead of 404, but I imagine it’s a similar issue. I had the wrong credentials entered in the Settings/Network page for the plugin. The author “could” be a little more explicit in what is required, since the only instruction I read said “Blog” authentication…so I kept trying the WordPress admin username and password…but that’s not it. Try the main FTP username and password for your domain. If you don’t have one set up, then set one up through your host, however you do that. (I have GoDaddy/Windows hosting…so mine is through my hosting account control / management panel under FTP accounts. ) I got a valid “manual” backup, AND I got a WordPress _cron scheduled backup, though my times are not jiving, and I need to fix that. If you set up a phpinfo.php file and view it, you should see that all the required software and extensions ARE there (if you have GoDaddy, now, in 7-2013)
Thanks, I’ve given that a try but still with no luck unfortunately!
Reliable backup plugins are so hard to come by
okay after upgrading to 3.0.13 aswell as WP 3.6, the error has now gone.
This is good news however going by my previous experience of this plugin it is just a matter of time until everything breaks again with no explanation
I had the cron disabled and I had as the date 1/1/1970. I went there, fixed the date to the today’s date and that fixed the problem.
The author needs to add some more descriptive error messages.
Overall, great plugin
