I confirm that the problem is still present.
The other problems do not know if they are caused by the Missing XSRF token, stadiums made that are bought at the same time.
Before the beta version i had no problem.

I add an information, the backup works correctly only the first time, then it no longer works until you restart the PC (but the data in Home is not changed and no e-mail messages are sent).

I, too, can confirm the “Missing XSRF token” problem still exists on my (admittedly underpowered) Windows 10 box running 2.0.2.9_canary_2017-10-01 NOT as a service. (Is that called “client mode”?)

I can also confirm that a page refresh (without the XSRF error) resolves any GUI oddities. I believe it was mentioned elsewhere but I think clicking “OK” on the XSRF error message should automatically reload the page.

I don’t see any “beta” or “canary” text under the Duplicati icon in the upper left of the screenshot…what version are you running?

In my experience this happens more frequently when the GUI is opened with the browser (as in the tab was open when I closed the browser, so it opens again as soon as I restart the browser) and on my lower end (5+ year old) machines.

Installer was duplicati-2.0.2.1_beta_2017-08-01-x64.msi which is also what About reports. I think you don’t see the word Beta because it is gray, and the dialog box greys out the background to the same shade of gray!

I think you don’t see the word Beta because it is gray, and the dialog box greys out the background to the same shade of gray!

D’Oh! That makes sense.

The XSRF issue was address in the code just after your version, but it is still canary (not even beta) so I understand if you don’t want to update to it. For the record, the error is just GUI related and refreshing the browser window (ctrl-r or F5) should “make it go away”.Duplicati

I see it as well for the latest stable version on Win10. No under-power issue here either. When this error shows up, I can click ok and everything “appears” to be ok, but if you try to edit a backup, you’ll find that the source is empty and can’t be browsed, and drop-down menus don’t work. You have to refresh the tab. I can’t see a pattern for how long it takes to re-appear, but everything will seem to work fine until you close it for some indeterminate time.

We know 2.0.2.1_beta had issues with the XSRF error even when used locally (which is why that part of the code was rewritten in later canary / experimental versions) but I’m not sure why F5 isn’t clearing it for you. If you’re using Chrome, try Ctrl-F5.

If you update to a newer version (canary, experimental, beta, etc.) and still get it, please come back and let us know.