First of all, try upgrading to the latest version. Many bugs in older releases are fixed in the latest version.
The second place to check is the Webmin updates page, on which bugfixes for the current version are posted. The easiest way to install all the latest updates is to use the second and third forms on the Webmin Modules page in the Webmin Configuration module.
If you really have found a new bug, go to the bug tracking system page to report it.
Included with the Webmin distribution is a program called changepass.pl to solve erecisely this problem. Assuming you have installed Webmin in /usr/libexec/webmin, you could change the password of the admin user to foo by running
/usr/libexec/webmin/changepass.pl /etc/webmin admin foo
Just installing Webmin will not cause any config file changes to be made. When you start to use it, only the config files related to the changes that you make in Webmin will be modified. For example, using the Apache Webserver module would not effect your Sendmail configuration.
If you are using SSL, make sure you connect to a URL like https://myhost:10000/ instead of http://myhost:10000. Without the https, your browser won't use SSL mode and thus will display this error.
After extracting the Webmin tar file, cd into the webmin-1.850 directory and type ./setup.sh. Because the root user on many system does not have the current directory in his path, just typing setup.sh will not work.
The Webmin Users and Groups module supports the encryption of passwords with the MD5 algorithm, if your system supports it. However, this depends on the Perl Digest::MD5 module. The simplest way to install it is with the command :
perl -MCPAN -e 'install Digest::MD5'
Once you have downloaded a new module as a .wbm file, enter the Webmin Configuration module and click on the Webmin Modules button. Then use the form at the top of the page to install the module either from the local filesystem of the server Webmin is running on, or uploaded from the client your browser is on.
Yes, this can be done with some configuration. See this document for details on running Webmin under Apache, or this page for details on running Usermin.
You can also run Webmin under the Zeus webserver in a similar way. See this documentation for instructions.
On some people's Slackware systems, the Perl crypt() function does not work because the descrypt.tgz package has not been installed. To solve this problem, install the package from your Slackware CD or FTP site.
You need to download and compile the latest Perl source from http://www.cpan.org/src/stable.tar.gz. Or if you have Solaris or HPUX you can download pre-built packages that avoid the need to compile Perl yourself.
By default, basic logging is enabled in Webmin. To turn on full logging, go into the Webmin Configuration module, click on the Logging icon and turn on the Log changes made to files by each action option. This will record all file changes and commands run by Webmin. Once logging is enabled, all actions performed from then on can be viewed in the Webmin Actions Log module.
Your browser has automatically gunzipped the file for you. Just rename it to webmin-1.850.tar (if it hasn't been already) and skip the gunzip step in the install instructions.
This happens because the default SSL certificate that is generated by webmin is not issued by a recognized certificate authority. From a security point of view, this makes the certificate less secure because an attacker could theoretically redirect traffic from your server to another machine without you knowing, which is normally impossible if using a proper SSL certificate. Network traffic is still encrypted though, so you are safe against attackers who are just listening in on your network connection.
If you want to be really sure that the Webmin server you are connecting to is really your own, the only solution is to order a certificate from an authority like Verisign that is associated with your server's hostname and will be recognized web browsers. This certificate should be placed in the file /etc/webmin/miniserv.pem and be in the same certifcate+key format as the existing miniserv.pem file.
To request a certificate, follow these steps :
The follow environment variables are set by Webmin before the script is called :
This happens if Webmin cannot identify your OS by looking at your /etc/issue file, possibly because it has been changed from the default contents. The best solution is to install the .tar.gz version of Webmin, which asks for the OS name and version manually.
In the Webmin Servers module, create a new user and give him access to only the Apache Webserver module. After saving, click on Apache Webserver next to the user's name in the list of Webmin users and use the form that appears to deny him access to everything except one selected virtual server.
Many other modules can also be configured in a similar way to restrict the access of a user to only certain DNS domains, Unix users or mail aliases.
It is possible to install the ZIP package of Webmin on Windows using the included setup.pl script. However, this is extremely alpha-level code, and only a few of the Webmin modules work due to packages like Squid, Sendmail and so on not existing under Windows. In addition, the Windows security and permissions systems are quite different from Unix, so anything that deals with file ownership and modes may not work.
The file you need to modify is /etc/webmin/miniserv.conf , in particular the allow= or deny= lines. If the allow= line exists, it contains a list of all addresses and networks that are allowed to connect to Webmin. Similarly, the deny= line contains addresses that are not allowed to connect. After modifying this file, you need to run /etc/webmin/stop ; /etc/webmin/start for the changes to take effect. Naturally, the file can only be edited by the root user.
I'm not sure how this error happens, but if it does you can follow these steps to fix it :
Yes, with some small changes to the config files. The steps you need to follow are :
If you are using xinetd instead of inetd, follow these steps instead :
service webminIf you have installed webmin somewhere else, you will have to change the /usr/libexec/webmin part of the path above.
user = root
env = LANG=
port = 10000
socket_type = stream
protocol = tcp
wait = no
disable = no
type = UNLISTED
server = /usr/libexec/webmin/miniserv.pl
server_args = /etc/webmin/miniserv.conf
To run Usermin from inetd or xinetd, follow the exact same steps but replace /etc/webmin with /etc/usermin and change the port to 20000.
This can be done by following these steps :
If PAM is not used on your operating system, the first two steps can be skipped. Webmin will instead read the /etc/passwd or /etc/shadow file directly to authenticate users who are using the Unix Authentication password mode.
Just run the command /etc/webmin/uninstall.sh .
If you have installed the RPM version of Webmin, you can also use rpm -e webmin, or if you have installed the Solaris package you can use pkgrm WSwebmin .
Follow these steps :
Again, if your system does not use PAM the first two steps can be skipped, and Webmin will read /etc/passwd or /etc/shadow file directly to authenticate users.
Another alternative to doing all this is to install Usermin, which allows all Unix users to login and access only settings belonging to them, using a similar interface to Webmin.
Normally when you double-click on a file in the right-hand list, it is displayed in a separate browser window. However, if you hold down shift while double-clicking, your browser should prompt you to save the file instead.
In Webmin versions 0.966 and above, you can also download by selecting the file and clicking on the Save button in the top-left corner of the file manager.
By default, Solaris doesn't allow packages to be upgraded. However, you can change this by editing the file /var/sadm/install/admin/default and changing the instance= line to instance=overwrite. An upgrade can then be performed by simply installing the new Webmin .pkg file.
By default, when a user composed email the From field contains username@systemhostname. This can be changed by following these steps :
By default the module will list all of the databases on your system on the main page, even if some are not actually usable by the logged-in user. To change this, follow these steps :
jcameron: database1A * in the database column means all databases, while a * in the username column means any user not listed so far.
fred: database2 database3
This often happens on Redhat Linux systems due to a bug (in my opinion) in the default Webalizer configuration. To fix it, do the following :
If you have a firewall that transparently proxies outgoing HTTP requests (such as one by Sonicwall), this may cause requests made by Webmin to by timed out. Without going into the underlying protocol details, my investigation has shown that Sonicwall is making incorrect assumptions about the number of IP packets an HTTP request will be in, and is thus broken.
The work-around is to disable the Enforce Host Tag Search option in the firewall, which turns off this broken feature.
Webmin has two RPC modes - slow mode, that only uses the same HTTP port the webserver listens on (typically 10000), and fast mode which uses ports 10000 on up. The upper bound depends on the number of concurrent RPC operations, but opening the range 10000 to 10010 should be enough when configuring the firewall between two Webmin servers.
If you see this error in /var/log/auth.log , edit the file /etc/pam.d/webmin and change the line @include common-session to @include common-session-noninteractive . Then run /etc/webmin/restart .