Duplicati: Failed to Get Nonce
Maybe you’re like me and you use Duplicati to target cloud and local storage for backups.
However, you attempted to login to Duplicati through the interactive stub in the Systems Tray and attempted to login, only to receive a cryptic error: Failed to Get Nonce.
The error indicates that the browser is using a cached version of the login page. The nonce system was used up until 2.0.8.1, but is not used in 2.1.0.1+. It should be easy to resolve with a forced reload (Shift+F5) in Chrome, or, dump the cache. Try again.
But let’s say you’re still experiencing the problem and can’t login to your localhost:8200 (http://localhost:8200/ngax/index.html). Drop to DOS with an elevated command prompt and try this command:
"C:\Program Files\Duplicati 2\Duplicati.Server.exe" --webservice-password=1234 --server-datafolder "C:\Windows\System32\config\systemprofile\AppData\Local\Duplicati"Then try to login to the localhost:8200 with 1234. You can change the password again once you’re in.
But let’s say you’re still encountering problems with its access token, and you’ve got the Windows service for Duplicati loaded. Try this:
Clear/preserve your Application Log in Event Viewer.
Go into services.msc and stop the Duplicati Server service.
Start the Duplicati Server service.
Go into the Application Log.
You might see events entered by Duplicati that it was unable to start the 8200 instance because of a problem with its keys. It will provide a link to reset those keys within the event details.
Click on that and you’ll be walked through a reset.
Now, maybe you’re playing with multiple instances. Look closely. If you accessed Duplicati’s web-based UI from the stub, you might be in the localhost:8300 instance of Duplicati. Yes, confusing; the Windows Service, by default, only works against the 8200 instance, so if you ever wondered why your backups configured in the 8300 instance aren’t automated and working — that’s why. So how do you fix that? Try this:
Access the 8300 instance.
Export your backup configs to a *.json file.
Log out of the 8300 instance.
Access the 8200 instance using that localhost:8200 command from earlier.
Import your backup config.
When it runs for the first time, it’ll report a problem with the database. Run the repair option. It’ll rebuild your local database.
After, you’ll be ready to run your backups again under the 8200 instance which is processed by the Windows service.
Delete the backup in the 8300 instance.
R
