Menu
▾
▴
#495 Usermin 1.840 crashes on first access from "Login to Usermin" button
The first time (after a server reboot) that I try to access a user's mailbox via Webmin > System > Users and Groups > (select user) > Login to Usermin I always get the (Chrome) browser message "This site can’t be reached....ERR_CONNECTION_REFUSED". If I then go to Webmin > Usermin Configuration I see that Usermin is not running (even though it was running before trying this). Clicking the green "Start Usermin" button works and subsequent mailbox accesses are fine until the next reboot.
This is completely reproducible and has been happening for months - I've only just got around to reporting it (sorry). It happens on several different servers running various versions of Ubuntu (16.04, 18.04, 20.04).
Hello,
I believe we have fixed that issue already and it must be not a problem after the next Usermin release.
The work-around would be is to enable starting Usermin at boot time manually.
Thanks for the quick response, I will wait for the next release and report if it's fixed.
I did already try manually enabling starting Usermin at boot time though, and it didn't help (Usermin was already starting OK and runs until that first crash). If you want me to do a specific test let me know.
Here's the output from "systemctl enable usermin"
usermin.service is not a native service, redirecting to systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable usermin
For now, you can try doing if from Webmin / Usermin Configuration page.
It's already selected - do you mean deselect and then reselect it?
(Not trying to be awkward, just making sure we're talking about the same bug!)
I can confirm that this is better (Webmin 2.013, Usermin 1.860) but still not working smoothly. Usermin seems to keep running but maybe just because it's forced to restart.
In Chrome an intermediate screen flashes up saying "This site cannot be reached" but then the Usermin page opens. It's too fast to grab a screenshot but in Firefox you actually have to click a button to "Try Again" and then it gets there. Screenshot attached.