Yes and I see it’s getting checkboxes set as it goes. Maybe I’ll look through those as well.
ngax defaults to a working setting, although it’s a hazard for infinite version buildup:
If the change is intentional, then new plan will be nicer when error message is fixed.
Continuing …
ngax Source Data screen tree has Source data tree of selections. Difficult otherwise.
Scratch that. I see Show selected paths in Source like ngax #158
ngax Source Data screen gives User data and Computer trees, sometimes confusing.
ngclient even more confusingly seems to jump the whole tree between different views.
Example:
Start with tree with Computer at top, which actually has my special folders then drives.
Expand into C:\Users\Public without surprise. Test my own profile, and view collapses:
and C: drive has gone away, even though I might want to pick some more files from it.
It looks like the Source Filters still interact with the tree, but it’s less clearly visible than previous scheme of red x compared to various green boxes for full or partial selection. Actually that last part has vanished, even in 2.0.8.1 – now it’s just a green checkmark.
Frustration might also ensue when someone tries to click something and it won’t react.
A subtle point is that if it’s filtered out, clicked, then filter removed, it’s still not selected.
Possibly this is the right behavior. ngclient is also instantly responsive to filter changes.
ngax filter (e.g. on extension of txt) may need reopening folder, or might never show.
Presumably ngax issue of exotic RE differences between JavaScript and C# still holds.
This might be the same issue I (and few others…) notice on ngax – the flaky status bar.
Sometimes nothing changes and I have to check logs. Sometimes “Loading” gets stuck.
As with ngax, the way out of a long-term lack of information is to try the browser refresh.
Source Data Filters delete button is lost or cut on a narrow window. Here’s half a button:
Source Data Filters delete (e.g. exclude extension tmp) adds empty source, Submit fails.
Before delete, Submit sends in
[
"C:\\backup source\\short.txt"
]
after delete, there is an empty second path added, which I would guess is why it gets
{"Error":"Invalid source list","Code":400}
to
[
"C:\\backup source\\short.txt",
""
]
Commandline shows far fewer of actually configured job options than ngax. Intended?
Commandline does not seem to provide the delete button for option that it does show.
Test for this was Source Data filter for extension tmp, to do a list-broken-files run.
list-broken-files in ngclient seems to get confused even without any special help.
Under ngax, one keeps target URL and deletes Commandline arguments box content.
Under ngclient, this gets
Found 2 commands but expected 1, commands:
"file://C:\Duplicati\duplicati-2.1.0.115_canary_2025-04-14-win-x64-gui\RUN\test 1\"
""
Return code: 200
I can’t see the empty path even in ngax three dot menu. Maybe it sent my empty value?
Similar issue with ngclient list command. In ngax, no arguments should show filesets:
Listing filesets:
0 : 4/15/2025 10:01:17 AM (2 files, 2.21 KiB)
Return code: 0
In ngclient, this is not possible. Interestingly, whatever is sent in seems to show all files.
Export As command line in ngclient does nothing
Export To file in ngclient doesn’t add -duplicati-config after job name, just name.zip.
Export To file in ngclient with Export passwords set doesn’t, e.g. no Name: Passphrase:
Export To file in ngclient with Export passwords and no Encrypt passwords doesn’t warn.
Probably doesn’t matter now since it doesn’t add them, but should it give ngax-like warn?
Export to file in ngclient with Encrypt passwords exports anyway if Password and Repeat password are blank (one or both) or inconsistent, however in some cases the name.aes exported file is not actually encrypted – it’s clear text. I’m not certain which setups do that.
EDIT 1:
Commandline in ngclient can’t seem to get any help by specific name, e.g. help backup.
What returns is the front-page summary from the help command. The request asked this:
[
"help",
"",
"backup",
...
If I switch blank TargetUrl and backup in Commandline arguments to the opposite, I see
[
"help",
"backup",
"",
...
which supports the theory that it sends both boxes. I haven’t looked at ngax, but it works.
If I run backup which actually wants both boxes, then it works. Some commands differ…
For Commandline enhancement, button to copy output would be nice. Not in ngax either (unless I missed it), which is surprising because outputs can be long and Ctrl-A too wide.
During pause, ngclient (e.g. Start backup, or same in Commandline) just sits there, while ngax gives either a popup or a Commandline message saying what’s up and your option.
In ngax, About → System information has hard-to-decipher Server State Properties area including schedulerQueueIds which might have shown pause queue. Is that in ngclient?
Attempting to decipher lastPgEvent when work seemed hung was another hard option.
proposedSchedule has gotten feature requests even in ngax for a better UI plus editing.
The ngclient job edit isn’t showing the schedule that I set up, ran, and is in the status bar:
Interestingly, switching to ngax edit doesn’t show it either, but proposedSchedule does.
Export to file in ngax shows "Schedule": null,. Something’s out of line. Unsure what.
Job 4 is test 1, but in trying to see if I can influence status bar (I can), how to remove?
- proposedSchedule : [{“Item1”:“4”,“Item2”:“2025-04-15T17:30:00Z”},{“Item1”:“4”,“Item2”:“2025-04-15T18:10:00Z”},{“Item1”:“4”,“Item2”:“2025-04-16T17:00:00Z”},{“Item1”:“4”,“Item2”:“2025-04-16T17:00:00Z”},{“Item1”:“4”,“Item2”:“2025-04-22T17:30:00Z”}]
Schedule screen in ngax for test 1:
Failed ngclient backup doesn’t give the dreaded red popup error, or much of any signal.
“Server errors are not visible to users #161” might be different, as that got an http error.
I don’t know the usual flow here, but the ngclient start got a 200 OK. Job’s log shows
failure from the missing file I referenced in Source, but I have to check the logs to see it.
Settings in ngclient is (if you look in developer tools) looping on settings and backups (alternating) probably as fast as it can go. Is this doing something, or is it wasted action?
Returning to Home stops the querying, going back into Settings starts it back up again.
Home screen in ngclient and ngax have forgotten it has two backups. Thinks it has none.
Restore shows the correct data, and the destination has two dlist. Is server DB confused?
Since I’m going in anyway, let’s look at the schedule for GUI-unschduled job 4 (test 1).
Comparing to job 5 (test 2), looks like something wiped out the stats for job 4 (test 1):
EDIT 2:
I let the scheduled-backup-I-don’t-want run at 2:10, and it filled out the metadata again.
Before that, I deleted the missing file reference because I wanted a successful backup.
Surprisingly, going to Source Data screen to Add Path of C:\missingfile and Submit
Duplicati-server.sqlite metadata for backup 4 is entirely gone now, without even a job run.
EDIT 3:
Seems like many changes (but not none) wipe metadata, e.g. set Remote volume size 51.
I thought maybe I could deschdule jobs by deleting them. It sort of works, but winds up:
and
In the database, the Schedule table references nonexistent Backups, but at the run time, profiling log shows nothing happens, which is better than if it got confused and fouled up.
It’s looking like I’ll have to delete the server database to get rid of these bogus schedules.
