This happens to me as well, on Windows 10. Duplicati says “Found update” at the bottom of the screen, I click download, it says “Downloading update” for a few seconds and then goes back to the “Found update” message.
Still happening, I can’t find any DNS that can resolve the name
System.Net.WebException: The remote name could not be resolved: 'alt.updates.duplicati.com'
at System.Net.WebClient.DownloadFile(Uri address, String fileName)
at Duplicati.Library.AutoUpdater.UpdaterManager.CheckForUpdate(ReleaseType channel)
If the primary url is working fine, can you make Duplicati not attempt to resolve the url and not create a scary error in the log file regarding the alt url? The error in the log makes us think something is broken that shouldn’t be.
I thought that was the way it works. Are you saying you see the alt URL error even when things are fine? Download links not working anymore shows my CLI check used to error. It’s fine since update server fix.
Now if you meant can Duplicati better handle the primary server not working, I could agree with the wish. The messaging could be better, but ideally the alt server would exist, not have the same issue, and work.
Squashing the DNS error might be as easy as having alt DNS-resolve to same IP as primary, i.e. a retry. That would leave the installed Duplicati code the ability to go elsewhere via DNS if server admin set that. But the elsewhere would still have to exist, and preferably not updated on the same schedule as primary.
I got the error last on Jul 30, 2019 6:47 PM. It looks like kenkendk fixed a server issue in this thread shortly after that, so that probably explains my error. I like your solution of having the alternate record always point to the primary. That way, both records should resolve without error all the time.