'Commandline' commands not running at all

1

Hi. I used to run Duplicati on a docker on OMV, and it’s awesome. I switched to ZimaOS for my NAS recently, which just incoroporates Docker as well, so I installed Duplicati again, currently 2.3.0.1. I didn’t bother importing my old backups, and created a new ‘full’ backup again. I forgot to deselect some unneeded folders, so did that later on, made new backups.

Then I wanted to delete the versions with ‘delete –version 3,4’ or whatever versions it where. When clicking the blue ‘start command’ button, it keeps spinning but doesn’t seem to initiate anything. No space was reclaimed from my backend either. Then I tried several other commands, but they all did the same, no output, no log, no response. I’ve enabled verbose logging through settings, as well as logging to a file, but nothing is logged at all when I start a command.
Then I tried the other way around by just limiting the number of kept backups until the ones I wanted, ran a new backup and that worked just fine.

As said, verbose logging is enabled. When I start a backup or it’s triggered by schedule, the log is filled up fine.

What could be the reason for custom commands not running at all?

2

If there are no logs, then I am guessing something is breaking in the UI.
Can you try with developer tools and see what request is sent when clicking the button?

3

Maybe I’m doing things wrong, but when I enable network monitoring, and press the button, nothing happens at all. Should I capture that another way?

4

That indicates that the error is in the frontend (webpage) instead.
What do you see in the “Console” tab?

5

After clicking the button, the lowest error message appears. The other are already there when opening the page.

By the way, if possible, can you delete the screenshot from my previous post? I can only delete the whole post. I forgot to scramble it, I don’t want unnescessary things happen :slight_smile:

Clipboard_05-04-2026_02
Clipboard_05-04-2026_021920×1170 174 KB

6

Arh, that one makes sense to me. It is a browser version issue we have seen before. I cannot remember the details, but in some cases the browser does not have the crypto API exposed, even though it should.

I will fix it for the next canary (and then the next stable patch version).

7

Thanks, amazing! I want to add though that this is the current Chrome version. Edge doesn’t work (maybe expected, chromium and thing) but Firefox doesn’t work either.