Accessing webmin after a test repository upgrade on a Buster appliance...
Warning!
It is detected that the Webmin web-server daemon was not restarted correctly on the last package upgrade. This is necessary to restart web-server manually by calling /bin/systemctl restart webmin command.
Clicking the 'Yes - try to restart it' button fixed things.
I can't see any errors in the logs.
I upgraded a second Buster appliance and the webmin process also wasn't restarted after the upgrade (I checked that it still had the same process number from before the upgrade). Manually running 'systemctl restart webmin' before accessing the web interface meant that I didn't see the error on first login on the second appliance.
Quick initial tests (on Buster) after restarting webmin are that it looks to be working OK.
Webmin 2.0 upgrade problems on Buster
Accessing webmin after a test repository upgrade on a Buster appliance...
Clicking the 'Yes - try to restart it' button fixed things.
I can't see any errors in the logs.
I upgraded a second Buster appliance and the webmin process also wasn't restarted after the upgrade (I checked that it still had the same process number from before the upgrade). Manually running 'systemctl restart webmin' before accessing the web interface meant that I didn't see the error on first login on the second appliance.
Quick initial tests (on Buster) after restarting webmin are that it looks to be working OK.