Gday epschmidt,
That is a Dropbox internal server error and as Dropbox does not support is Web API yet it will be very difficult for me to work out why it is happening.
What file is if failing on?
Cheers,
Mikey
It’s showing that error for a large number of files. I tried restarting the backup, and the SQL file gets updated but that’s it. The files it’s showing errors on are mostly Magento PHP files, but they’ve actually been backed up, they’re in the backup folder already. So I don’t know if the plugin is checking with Dropbox to see if those files have changed, and that’s triggering the error?
It appears that all the Magento files were backed up, and it made it through some of the wp-content folder where it is stuck now. But like I said, the errors are all related to Magento files that are already in the backup folder.
Gday epschmidt,
That is quite odd and it appears that you have exposed a bug at the Dropbox end. As a 500 is, to quote Dropbox, a “5xx Server error — our bad, we’ll fix it soon (ahem, very rare).”
The only thing I can suggest is wait until I release the next version of the plugin that will have the ability to exclude certain directories/files from the backup.
That way you can narrow down the exact file that is causing the problem and I can raise an issue with Dropbox.
Cheers,
Mikey
