this morning, my daily backup to my OneDrive gave this error message :
The remote server returned an error: (410) Gone.
Here the full last retry log message :
Operation List with file attempt 5 of 5 failed with message: The remote server returned an error: (410) Gone.
System.Net.WebException: The remote server returned an error: (410) Gone.
at Duplicati.Library.Main.Operation.FilelistProcessor.RemoteListAnalysis(BackendManager backend, Options options, LocalDatabase database, IBackendWriter log, String protectedfile)
at Duplicati.Library.Main.Operation.FilelistProcessor.VerifyRemoteList(BackendManager backend, Options options, LocalDatabase database, IBackendWriter log, String protectedfile)
at Duplicati.Library.Main.Operation.BackupHandler.PreBackupVerify(BackendManager backend, String protectedfile)
at Duplicati.Library.Main.Operation.BackupHandler.Run(String sources, IFilter filter)
In my OneDrive backup folder, I can see 3 files from yesterday and many more from the past 6 months, so everything looks normal.
Maybe it’s just a short outage ? Or OneDrive just changed its communication protocol ?
I just re-did the AuthID authorization but it didn’t change anything.
testing the connection in the configuration menu gives the same error.
I’m getting this as well. Started on the run from last night (Monday night, 1/7) and has just happened again this evening. The last files I’m seeing are from Saturday at 12am, which is when the backup runs (nightly at midnight). There’s less than 20% space used, so it’s not running out of space.
I to have the issue, on 1x PC and 2x MAC started at the same time too. Only OneDrive is affected my local backups are fine as is GoogleDrive. Duplicati version is “Duplicati - 126.96.36.199_beta_2018-11-28” and I have been running it successfully since release.
I’m running Duplicati - 188.8.131.52_beta_2018-11-28 on a PC and Duplicati - 184.108.40.206_beta_2018-04-02 on a Synology DiskStation device. Both of these are connected to OneDrive and both have started reporting the same error: The remote server returned an error: (410) Gone
It’s interesting to note that I haven’t changed any files or directories on OneDrive. Actually, this OneDrive is dedicated to Duplicati.
@samh I have the same question as @manu: How to configure Microsoft OneDrive v2, that you said is working OK for you.
these APIs are now end of life and will no longer be available after November 1, 2018 .
To switch, I think (besides editing the job to change the Storage type dropdown from Microsoft OneDrive to Microsoft OneDrive v2) you probably have to get a new AuthID but you can certainly “Test connection” first.
Migrating “should” just be a dropdown change and probably a new AuthID. The Duplicati screen is the same. Between its Storage Type and AuthID is a Path on server (still). If there’s something more, please say where.
Setting up OneDrive (personal) gives some information. Link goes to a post to address questions/concerns, however lack of OneDrive v2 in a beta release (as opposed to canary or experimental) was fixed by 220.127.116.11.
The above How-To is possibly a better place to document any information generally useful to setting this up.
I updated Duplicati this morning from the auto-update feature and then the version was
Clicking on “About -> Check for updates now” did nothing.
So I just manually downloaded and installed the version 18.104.22.168_beta_2018-11-28, which failed (on Windows 10) ; so I manually uninstalled it and reinstalled it, and then Duplicati launched normally again, but I still don’t have a correct support for OneDrive v2, as seen on this screenshot :
Probably the first thing to try when the web UI gets confused (as it might be here – did previous OneDrive look that way too, or is this coming from somewhere else?) is a hard refresh of the browser, sometimes Control-F5.
There is some hope that a change after 22.214.171.124 will avoid the need to deal with browser caching quite as often.
Duplicati.CommandLine.BackendTool.exe let me try out variations (and see errors) a bit more easily, and the suspect wound up being Percent-encoding in a URI which I’m not sure is being done correctly. You can follow that chart, converting a plus sign to the sequence %2b or %2B to see if it lets plus work. That’s a workaround, not a fix. For a code fix (if manual encoding actually helps), please file an issue to get the fix request queued.
This same issue possibly explains this problem found by @thepappaq where workaround was to do a folder rename. That one was a little murkier because the # (number sign or pound sign) is also an invalid character sometimes, so Microsoft Graph’s unifying things could maybe have unified restrictions, but plus is not invalid:
Thanks for testing out variations of names. If you would like, feel free to try other characters that should also be percent-encoded. The test data for the URL encoding theory so far is a little thin now, but could be better.