Release: 2.0.8.1 (beta) 2024-05-07

Actually that particular one looks a bit odd, but the lead developer might be personally testing something. Currently, the latest external releases are 2.0.8.1 Beta and 2.0.8.108 Debug, and show those in Default:

image

I’m kind of doubting that the suggestion of using Settings to wait for eventual Stable will work in 2.0.8.1. Maybe there’s something cooking, or maybe you have to wait for more stability, and an announcement.

Another point that is simpler compared to Debian is that parallel maintenance is very rare. For example,
About → Changlog or https://github.com/duplicati/duplicati/releases shows the continuous flow towards Stable. After a Beta is released, Canary releases happen, for willing testers of something hot off a build.

Experimental is (IMO) a bit of a misnomer, as it’s a Canary proven well enough to be a Beta pre-release helping for example to ensure through testing that the slower Experimental/Beta channel updates is OK.

Experimental is literally a Canary that is felt stable enough to relabel, and Beta is Experimental after test.
This might change at some point, e.g. after first Stable, or if a big organization allows a different method.

Currently Duplicati usually does repetitions of Canary/Experimental/Beta. Recently Debug has come out beneath Canary for the bravest testers. It’s off the channel display on the risk scale, and Stable is off too.

Perhaps the Settings display needs an update to show current use, and order channel risks ascendingly.

Yes, it was just what I had running at the time :slight_smile:

It would achieve what is being asked for: no more notifications until the stable release.
I can on the update server logs that a number of user has this set up.

Technically, when choosing the stable channel, it will then check for a file that does not yet exist.
Once the stable is released, I can create that file and users will be notified.

There is no button to do it. I can force other Settings Default with environment variable:

AUTOUPDATER_Duplicati_CHANNEL - Choose different channel than the default Beta, valid settings: Stable,Beta,Experimental,Canary,Nightly,Debug

I’m actually testing 2.0.7.1 to also test for a 2.0.8.1.

Beta gets popup: New update found: 2.0.8.1_beta_2024-05-07
Stable gets server log: System.Net.WebException: The remote server returned an error: (404) Not Found.
Debug gets server log: System.IO.InvalidDataException: Unable to verify signature

so while I suspect this will silence notices before Stable, I’m not sure it will spot Stable when it comes out.

Ok, that is a flaw then. I guess it has been overlooked because there has been no stable release.

I’m running Duplicati - 2.0.6.1_beta_2021-05-03 (Windows). When I check for updates via my Duplicati web page (About), it says 2.0.7.1_beta_2023-05-25 is available. Why wouldn’t it show 2.0.8.1_beta_2024-05-07 as available? Do I need to update to 2.0.7.1 prior to 2.0.8.1?

Is downloading and running the new installation file preferable (safer) than running the update via a web browser?

Thanks

Not a safety issue, as far as I know, however it’s probably more certain, regardless of things going wrong.

I doubt it. It sees 2.0.8.1 even if I test from 2.0.5.1.

C:\ProgramData\Duplicati\duplicati-2.0.5.1_beta_2020-01-18>Duplicati.Library.AutoUpdater list
 * 2.0.5.1_beta_2020-01-18 (2.0.5.1)
C:\ProgramData\Duplicati\duplicati-2.0.5.1_beta_2020-01-18>Duplicati.Library.AutoUpdater check
New version is available: 2.0.8.1_beta_2024-05-07

You could do a similar test, except your Duplicati probably starts from C:\Program Files\Duplicati 2
Maybe you’re not on Windows. If not, what are you on, and are you behind firewalls, etc. that might block?
I did try looking at the alternate update site. I’m not the expert, but so far I can’t explain the results you see.

EDIT 1:

Do you see any updater warnings or errors in About → Show log → Stored?

EDIT 2:

This release was soon superseded as 2.0.6.x Beta by 2.0.6.3_beta_2021-06-17, and Duplicati should have been notifying you automatically of that since around then. Later it would move to 2.0.7.1_beta_2023-05-25, and then 2.0.8.1_beta_2024-05-07. Is this what you were seeing, but you chose to stay on 2.0.6.1 release?

Thanks for the response. Running Windows 7. Disabled firewall. I did get notifications about previous updates, but didn’t want to break something as my backup system works. Now I feel like the version I’m running is so old that it would be worth upgrading.

Here is the command line check running as Administrator. My path is a little different from yours.

C:\ProgramData\Duplicati\updates\2.0.6.1>duplicati.library.autoupdater list

  • 2.0.6.1_beta_2021-05-03 (2.0.6.1)

C:\ProgramData\Duplicati\updates\2.0.6.1>duplicati.library.autoupdater check
Error detected: System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.
at System.Net.WebClient.DownloadFile(Uri address, String fileName)
at Duplicati.Library.AutoUpdater.UpdaterManager.CheckForUpdate(ReleaseType channel)
Error detected: System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.
at System.Net.WebClient.DownloadFile(Uri address, String fileName)
at Duplicati.Library.AutoUpdater.UpdaterManager.CheckForUpdate(ReleaseType channel)
No updates found

C:\ProgramData\Duplicati\updates\2.0.6.1>

So it is having an issue.

Here is the about screen showing a previous version available:

Image 2

Here is the About → Show log → Stored:

Thanks again for your help.

https://updates.duplicati.com requires at least TLS 1.2, as earlier versions have security problems.
If I recall corrctly, the previous updates host was more forgiving (and got dinged by security scans).
You could try the above link in Internet Explorer to see if fails too. Windows 7 defaults to no TLS 1.2.

Enabling TLS 1.2 on Windows 7 are some third party directions that link to some old Microsoft data.

Windows 7 support ended on January 14, 2020 so you’re living dangerously, and ought to get off it…
You’re not getting security updates from Microsoft now, so there’s no telling what bad stuff will get in.

If you really want to stay with it, you could visit Duplicati Downloads.to run an .msi installer manually.