Webmin down after wbm-server-manager-4.6-1.noarch upgrade

I upgraded the following webmin module (through CM) and now one systems shows "Webmin down" status.

Jun 25 09:59:35 Updated: 2:wbm-server-manager-4.6-1.noarch

Webmin is up and running on that server as I can connect to it directly, login, etc. The error message is Detailed status error Webmin failed to complete in 20 seconds

System load is 10:26:45 up 8 days, 11:35,  1 user,  load average: 0.64, 0.68, 0.73

Any ideas?

Closed (fixed)


In an attempt to fix this I set it to NOT log into webmin thinking I would set it back but that option is completely gone now. I guess CM isn't recognizing Webmin as installed and working on that system. CM is now managing that instance via SSH but we have the full virtualmin/webmin stack installed there w/ a couple domains. I'll wait until I hear from you so as to not mess things up further. -- Craig

Does it help if you restart Webmin on the remote system?

Try running /etc/webmin/stop , making sure there are no miniserv.pl processes running, then running /etc/webmin/start

Also, make sure the remote system isn't firewalling any ports in the range 10000 -> 10100.

Tried restarting on the remote system multiple times - no joy. I've included a copy of the FW rules below but I do have ports 10000:10010 open.

Here's the error - Detailed status error Webmin login disabled. Almost sounds like I have to enable it somewhere in CM...

Firewall rules (on the remote system):

# Generated by webmin
-A FORWARD -o venet0 -j LOG --log-level 7 --log-prefix BANDWIDTH_OUT:
-A FORWARD -i venet0 -j LOG --log-level 7 --log-prefix BANDWIDTH_IN:
-A OUTPUT -o venet0 -j LOG --log-level 7 --log-prefix BANDWIDTH_OUT:
-A INPUT -i venet0 -j LOG --log-level 7 --log-prefix BANDWIDTH_IN:
-A INPUT -p udp -m udp --dport ftp-data -j ACCEPT
-A INPUT -p udp -m udp --dport ftp -j ACCEPT
-A INPUT -p udp -m udp --dport domain -j ACCEPT
-A INPUT -p tcp -m tcp --dport 20000 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 10000:10010 -j ACCEPT
-A INPUT -p tcp -m tcp --dport https -j ACCEPT
-A INPUT -p tcp -m tcp --dport http -j ACCEPT
-A INPUT -p tcp -m tcp --dport imaps -j ACCEPT
-A INPUT -p tcp -m tcp --dport imap -j ACCEPT
-A INPUT -p tcp -m tcp --dport pop3s -j ACCEPT
-A INPUT -p tcp -m tcp --dport pop3 -j ACCEPT
-A INPUT -p tcp -m tcp --dport ftp-data -j ACCEPT
-A INPUT -p tcp -m tcp --dport ftp -j ACCEPT
-A INPUT -p tcp -m tcp --dport domain -j ACCEPT
-A INPUT -p tcp -m tcp --dport smtp -j ACCEPT
-A INPUT -p tcp -m tcp --dport ssh -j ACCEPT
# Completed
# Generated by webmin
# Completed
# Generated by webmin
# Completed

"Webmin login disabled" means that you turned it off at Edit System -> Authentication.

Try turning it back on again, then clicking the "Refresh status" button.

That's what I was talking about in reply #1; that option no longer exists in Edit System -> Authentication; only the SSH stuff is there. See the attached image.

Ah .. that means that Cloudmin thinks that Webmin is not installed!

Does the remote system have an /etc/webmin directory?

Yes, /etc/webmin is there. As I indicated in the original post I can connect directly to the remote server and login to Virtualmin/Webmin directly. Everything seems to work correctly once logged in.

The only issue is that CM is not seeing Virtualmin/Webmin installed on this container after the package update above.

If you SSH in as root and run cloudmin refresh-systems --host the.vpsname.com , what does it show as the status?

Also, on the Edit System page under System Details, what does it show as the "Detailed status error" ?

[root@cm1 ~]# cloudmin refresh-systems --host id1002.cm1.dashsystems.com
Refreshing status of 1 systems ..
id1002.cm1.dashsystems.com: nowebmin (SSH)

How about the message in the "Detailed status error" field?

Also, what is the output from the command :

cloudmin run-command --host id1002.cm1.dashsystems.com hostname

Detailed status error Webmin login disabled

[root@cm1 ~]# cloudmin run-command --host id1002.cm1.dashsystems.com hostname

Ok, I think I see it .. this can happen if Webmin was disabled when the system was originally added.

The fix is to get the system's ID with the command :

cloudmin list-systems --host id1002.cm1.dashsystems.com --id-only

and then edit the file under /etc/webmin/servers named ID.serv . At the end, add the line :


I found that entry in file but it was =1; I changed it to =0 and that made webmin visible in CM again. I still can't get connected but I think through the process I changed the password and I think this might be a security precaution on CM's part...

Detailed status error HTTP error : HTTP/1.0 403 Access denied for The host has been blocked because of too many authentication failures

Looks like the remote system needs Webmin to be restarted in order to clear the blocked IP.

Also, this is usually triggered by an incorrect username or password..

I restarted webmin and reset the webmin pasword; it is working again.

Most of this ticket involved getting webmin "turned back on" after I disabled it just after my original post - any idea why webmin showed as "down" after the update?

Ok, I see it .. I didn't realized that it is possible to select "Do not attempt Webmin login", but once you have done so it is impossible to disable that mode!

I will fix this in Cloudmin 4.7.

Automatically closed -- issue fixed for 2 weeks with no activity.