2.1.2.0 (Beta) 2025-08-20: local restore failure

[ts678]

@CasualCopier

Thanks a lot for the useful hints. Simply changing the notation did the job.

I’m glad it worked, but it could work better. Thanks for helping Beta test find this one.

I ran some Duplicati.CommandLine.BackendTool list tests, and these work on previous Stable 2.1.0.5 and current Beta 2.1.2.0:

"\\localhost\Shared"
"file://\\localhost\Shared"
"file:////localhost/Shared"
"file:////localhost/Shared/test 1"

"file:////localhost/Shared/test%201" worked on 2.1.2.0 but not on 2.1.0.5.
This supports the idea that 2.1.2.0 will accept both stricter and looser URL syntax:

@kenkendk

The way it works now is that it accepts the legacy odd input, but “prefers” the correct encoded versions. This is being affected a bit by the secret manager that does a encode/decode cycle on each URL (even if it is not used), so the URL you pass in to Duplicati gets converted in the escaped strict RFC 3986 format before being passed to the backend.

Testing in old GUI with \\localhost\Shared\test 1 worked but 2.1.2.0 got odd.

Switch to new UI worked, meaning backup run worked.
Edit, click to Options, Submit worked.
Edit, click to Destination, click to Options, Submit failed.

As soon as the Destination screen gets the URL, it seems to do the extra slash insertion.

New UI view of that is /\\localhost\Shared\test 1
Old UI view of that is /%5C%5Clocalhost%5CShared%5Ctest%201
You can see the new leading slash that ngclient (wrongly?) added.
Deleting it in old UI and doing Save gets the backup working again.

Before I open new ngclient UI issue, let’s see if dev has comments.