Duplicati seemed okay for a while but now I wanted to verify a file discrepancy with what is backed up. In the WebUI if I try to look at the list of files by going to “Restore” it keeps giving me a “Missing XSRF token” error after a few minutes of waiting. This occurs after reloading or clearing the cache and restarting the web browser.
I thought it might be the fact I was accessing on LAN so I tried SSH forwarding the port and that didn’t work, same error.
Then I tried accessing locally using a VNC session and running firefox, same error.
It seems like I cannot access the restore functionality properly and I have no idea why.
Though the method varies by browser, you can usually see cookies. This cookie is called xsrf-token. Curious people can see the cookies go in on network requests, e.g. with developer tools, often on F12.
There are timestamps involved, so make sure that your system times are doing something reasonable.
Whether or not that is the case, the existing options for timeout are to handle slow destinations, e.g. http-operation-timeout to OneDrive is sometimes used. A 100 second default is sometimes too little.
Web browsers sometimes have response timeout settings (maybe hard to find), and sometimes not.
This one seems a little trickier because Duplicati got a request with a bad or no cookie, so said this:
You can probably keep an eye on that cookie (as mentioned using the browser facilities to watch the cookie either as it sits in the store or as it travels on the request) to see if it’s heading towards expire.
Instead of watching and forecasting, it might also be possible to capture the traffic, then look back at failure time to look for clues on what led to that. If it was an expired cookie, you’d probably see none.
I’d note that the command line client does nothing of this, so that’s a way out if you’re ever in a pinch.
I hope you set a large blocksize (maybe 5 MB) or things will be slow. How many files? It’s in your log.
The FIND command, which seems to have list as a synonym. It’s not as easy as ls because it’s not a standalone command, because to be GUI backup compatible you need to tell it where the GUI DB lives, and because it also wants to know the destination, but Export As Commandline gives necessary details.
Example, and I’m violating the documented order and getting away with it, so that’s apparently possible.