It appears for some users the GUI based updates are not correctly restarting the server, but it works fine for others. So I’d like to try and get some metrics from both sides to see if we can narrow down potential causes.
For me, it worked fine going from 2.0.2.17 canary to 2.0.3.2 canary on Windows 10 running in server (service) mode.
Installation
(We still need a category for “Bug”)
For reference, a 2.0.2.15 Experimental update to 2.0.3.1 Experimental on a system WITH a GUI password left me hanging at:
Until I manually refreshed the window at which point I got this message after which clicking OK and logging in dropped me on the Home page (which was not where I started)
But it seemed a bit confused as to what I was really running:
Clicking “Dismiss” then manually checking for updates does NOT make the message re-appear.
Running in service mode (Windows), the new version becomes active after I restart the Duplicati service.