I can’t update Duplicati via the browser-webpage.
What happens:
I have this behaviour on 3 windows machines. And I don’t know, what is the problem for that.
Is there any solution how the Update process via the backend is working?
What Duplicati are you running? Check About page.
It sounds like an older one. Image posts would help.
Are you still on older version than the popup offers?
Did you ever restart Duplicati after doing the Install?
I run:
Duplicati - 2.0.7.1_beta_2023-05-25
Under the about page it says:
Update is available, "Update Duplicati v2.1.0.2 is available, download now
I add a screenshot of the about page here. You can see also the popup at the bottom, that will end in a dead loop, if I click “Install”:
Do you need more information?
For now, probably only from the developer if needed. The updater has been changing a lot.
The updates to 2.0 Duplicati versions used a Duplicati-specific autoupdater. 2.1 is different.
Duplicati updates now work like updates for typical applications without their own updaters.
It’s manual like a new install, except it should be safe to do without uninstalling old one first.
Shutting Duplicati down first is advisable because its program files will need to be replaced.
You can look in wherever your browser puts downloads to see if there’s a file for you to run.
Did it never offer 2.0.8.1-2.0.8.1_beta_2024-05-07? Make sure you look at its About screen.
Looking at the Program Files folder or installed Apps screen will not show autoupdates done.
I’m testing on 2.0.6.3 (because I had one handy) and not totally happy with what it’s doing.
I’d note again that the jump to 2.1 is major, and I doubt 2.0.6.3 was made with 2.1 in mind.
About says You are currently running Duplicati - 2.0.6.3_beta_2021-06-17
Show button shows the 2.1.0.2 change log. I like that, as it shows important upgrade notes:
If I hover over the middle button (Download in English version), Edge in lower left shows
http://localhost:8200/ngax/index.html and if I click Download, it doesn’t, but I’m at
http://localhost:8200/ngax/index.html# even if I was on some other screen before.
I don’t know if this is something that update server can fix, or if it’s just all 2.0.6.3 can do.
I’ve seen similar popups that will send browser to the Duplicati web site Download page.
That gets people to where they need to go for 2.1, but there’s no release notice to see…
One way to get jump to 2.1 over with is to download it manually from web site and install.
EDIT 1:
The Duplicati v2.1.0.2 that’s a different color in image is the same link as Download.
Maybe the developer will have some comment on why the guidance here isn’t so helpful?
There is a consistency check that fails when downloading, because you are downloading 2.0.8.1 and the release message says you should be downloading 2.1.0.2 (which is not possible for 2.0.6.3). After the download it checks that you have indeed downloaded 2.1.0.2, but you have downloaded 2.0.8.1, so the update is rejected.
If it was working, it would install 2.0.8.1 and then notice a new manual update, and direct you to:
You can save the in-between steps, and just download the latest version from there.
In case you want another version, they are listed here:
The manifest is dual-purpose, it serves both pre-2.0.8.1 versions by offering 2.0.8.1, and it offers a manual update link for 2.0.8.1.
The problem is that there is an additional version check as described above, so the 2.0.8.1 update is rejected after being downloaded.
That’s possibly the code I posted about 9 minutes after this explanation in my EDIT 2, however it doesn’t really matter whether I found the spot, as it now seems understood better. We’re not likely to be changing old Duplicati, so the even greater speculations I posted later might be what’s relevant – what update cases are impacted by the check?
The update checks work as they should. Versions older than 2.0.8.1 (and one of the canaries before that) do not support the upgrade-to-manifest-v2 code path so they treat the update as a literal update to version 2.1.0.2 (or a canary, depending on channel).
The only part that does not work is actually installing the update, as the version check fails. Manual install of the update works.
