FAQ

FAQ

Installation

Should I pre-install Webmin before I run virtualmin-install.sh script?

No. The install script runs best on a freshly installed Grade A supported operating system.

Should I install Apache or Postfix, and other similar packages before I run virtualmin-install.sh script?

No. The install script runs best on a freshly installed Grade A supported operating system.

What if I already installed Webmin on my system?

If you installed from the standard package type for your system downloaded from one of our repositories, everything should be fine. Running virtualmin-install.sh should work without any trouble.

If you installed from a third party source, or you don’t know where it came from (like it was provided on a dedicated server you’ve rented from your hosting provider), you should uninstall it, and make sure whatever software repository it came from has been disabled.

What if Apache or Postfix, and other similar packages are already installed on my system?

If you installed from the OS standard repository for your OS, everything should be fine. If you installed from any third party sources, or from source, the installation will fail and things will go badly. The install script cannot accommodate packages installed from non-standard sources.

If you can re-install your OS, it is recommended that you start with a freshly installed Grade A supported operating system.

I installed Apache manually or using packages from a third party source

I have the following error after install: “The suexec command your system is configured to only run scripts under /var/www, but the Virtualmin virtual server home directory is /home. CGI and PHP scripts run as domain owners will not be executed.”

The Apache suexec command on your system is misconfigured for use in a virtual hosting environment, and needs to be recompiled or configured (on systems that provide a configurable suexec command) with the docroot set to /home. On Debian/Ubuntu systems, you can install the apache2-suexec-custom package, and modify /etc/apache2/suexec/www-data to include /home. On other systems, you will need to recompile the Apache package or the suexec binary, which we strongly not recommend doing.

What if I need to install it on a server that is already setup and running?

It’s highly recommended to install Virtualmin on a new, Grade A supported operating system. If installation on an active server is necessary, make sure to back up all data beforehand.

The final results will depend on how invasive the changes to the running system were. Anything that conflicts with what the Virtualmin install script does would be a source of trouble. What kind of trouble is difficult to predict. The biggest risk would be causing some packages you use to be uninstalled (to satisfy dependencies of Virtualmin).

The safer way to do it would be to do the following, instead of using the full virtualmin-install.sh installer:

Setup Virtualmin repos:

./virtualmin-install.sh --setup

Install dependencies but carefully. Look at the list of what will be installed, and more importantly, what will be removed:

apt install virtualmin-lamp-stack

or

dnf group install --setopt=group_package_types=mandatory,default "Virtualmin LAMP Stack"

Or, if you want to keep it as small as possible to start, to reduce the surface area for problems (or if you’re not hosting mail):

apt install virtualmin-lamp-stack-minimal

or

dnf group install --setopt=group_package_types=mandatory,default "Virtualmin LAMP Stack Minimal"

Assuming default configuration of apt or dnf, it’ll ask before doing any removals. Don’t type “y” until you know the changes being made won’t break something you depend on.

Then install Virtualmin itself:

apt install virtualmin-core

or

dnf group install --setopt=group_package_types=mandatory,default "Virtualmin Core"

Then, assuming everything seems to be fine, run the appropriate configuration bundle (this step also has some risks, and you won’t be given any warning about what it’s doing, it assumes that if you tell it to do something you mean it):

virtualmin-config-system --bundle LAMP

Or use the MiniLAMP bundle if you did the minimal dependency install above.

Assuming everything goes right, you’d then have roughly the same system the Virtualmin install script would produce, but it would give you a couple of opportunities to bail if something disastrous is about to happen.

It’s also possible to selectively run the config step. Or selectively install dependencies, but I’ll leave that as an exercise for the reader. The things virtualmin-config-system does can be found in Virtualmin config GitHub repo.

If you wanted to handroll an installation that’s exactly the things you need and nothing you don’t. But, that’s a lot more work. If you don’t have any mail setup and if you don’t have much in the Apache configuration, yet, then running the automated stages of the install manually if probably safe-ish.

License

How do I upgrade from GPL to Pro

Once you have a serial number and a license key, you would need to undergo GPL to Pro upgrade by going to System Settings ⇾ Upgrade to Virtualmin Pro page. No other commands mentioned below should be run in this type of upgrade.

How to upgrade Virtualmin license?

Upgrading your Virtualmin Professional license is straightforward and does not require a reinstallation of Virtualmin! Once you’ve purchased your new license, just run the virtualmin change-license command. This action will update your system with the new serial number and license key. All existing licenses details can be found in the My Account → Software Licenses page on the Virtualmin website.

How do I renew an expired license?

To re-activate a system with an expired license, simply buy a new license in our shop, and use the change-license command to apply it to your server. Your server will instantly be activated on the new license.

The change-license command can be used for Virtualmin, like this:

virtualmin change-license --serial NEWSERIAL --key NEWKEY

To change license using latest virtualmin-install.sh script you can use the following command:

sh -c "$(curl -fsSL https://software.virtualmin.com/cgi-bin/install.cgi?serial=1234567\&key=AAbbCCddEE)" -- --setup

Note: 1234567 and AAbbCCddEE should be replaced with your actual serial and key.

How do I cancel a recurring license?

Licenses can be canceled in your Virtualmin account. Click on My Account, and then Software Licenses, and then find the license you want to cancel. Click the related subscription number in the licenses table. From there you can Cancel or make other changes. If your license does not have a related subscription it will automatically end when the license term is complete.

How do I upgrade or downgrade a license?

As with cancellations, you can make changes to your licenses in the My Account page under Software Licenses. Find the license you want to modify, click the related subscription, and choose to upgrade or downgrade. Confirm the order to make the change. If your license does not have a related subscription, that means it was purchased before 2021 and is not known to the new commerce system. To make changes, you’ll need to purchase a new license and switch to it using the virtualmin change-license command as described above.

Where are my expired licenses?

Expired licenses don’t have any intrinsic value and are removed from the Software Licenses page one month after their expiration date.

Why do I see a license error message?

You may see a license error message if you’re using the same Pro license on multiple servers. Here are the important details to understand:

• Each Pro license is valid for exactly one server. Using it on multiple servers will trigger a license error unless you’re in the migration grace period.

• When migrating between servers or testing, you get a 21-day grace period (minus 48 hours for license server lock release) to use the same license on multiple servers.

• After the grace period expires:

  • Virtualmin will switch to “read-only” mode on all affected servers, and you won’t be able to make changes through the Virtualmin UI or CLI.
  • Your websites, databases, and other system services will continue running normally.

• For expired licenses, there’s a 7-day grace period to renew before the same restrictions are applied.

To resolve license errors, you can either:

• Complete your server migration within the grace period.
• Purchase additional licenses for extra servers.
• Ensure you’re only using the license on one server.

How do I update payment information or find my invoices?

If your billing information has expired, we will not be able to renew your licenses automatically. To add a new default payment method, browse to My Account ⇾ Payment methods, and then click the Add payment method button.

Security

What are the default file and directory permissions?

When Webmin and Virtualmin create files and directories, they rely on the default mode mask (“umask”) without setting specific permissions. By default, all files and directories have full permissions set to “666 (rw-rw-rw-)” for files and “777 (rwxrwxrwx)” for directories. The “umask” value, typically set to “022”, modifies these default permissions. This means the actual default permissions are set and calculated as follows:

• For files

  666 - 022 = 644 (rw-r--r--)
  

• For directories

  777 - 022 = 755 (rwxr-xr-x)
  

However, these default settings can be overridden in Webmin ⇾ Webmin Configuration: Advanced Options page under the Umask (unset permission bits) for created files option, which for example can be set to “027” to restrict default permissions to “640 (rw-r—–)” for files and “750 (rwxr-x—)” for directories.

Additionally, Webmin and Virtualmin offer specific settings for certain files and directories:

• Default home directory permissions can be controlled in System ⇾ Users and Groups: Configuration ⇾ Home directory options page.
• Permissions for files in the “public_html” directory can be set in System Settings ⇾ Server Templates: Edit Server Template / Website for domain using the Permissions on website subdirectory option.

  Note: Changes made in templates only apply to newly created virtual servers.

Packages and web apps upgrades

Virtualmin and all related packages are outdated, and no updates are available. Why?

This problem typically arises from outdated repositories. To resolve the issue, simply re-setup the Virtualmin repositories by executing the command below. This command is designed to function across all Grade A and some Grade B supported operating systems and is compatible with both Virtualmin GPL and Pro versions:

sh -c "$(curl -fsSL https://software.virtualmin.com/gpl/scripts/virtualmin-install.sh)" -- --setup

How to update Virtualmin and all related packages?

When a new version is available, you will see a message on the Dashboard page stating that there are Virtualmin related package updates available. Other packages may be listed too, depending on what is available to be updated. To install these updates, just click the Install All Updates Now button and follow onscreen instructions.

Upgrading from the command line is also possible, using the dnf or apt-get commands, depending on your OS.

For example, on EL systems, you can run the following command to update all system packages, including Virtualmin related ones:

dnf update -y

On Debian and derivatives, you can run the following command:

apt-get update && apt-get upgrade -y

Alternately, you can install specific packages, e.g.:

dnf update perl webmin wbm-virtual-server usermin -y

or

apt-get install perl webmin webmin-virtual-server usermin -y

How can I make sure my web applications are up-to-date without having to wait for the next Virtualmin release?

In Virtualmin, go to System Settings ⇾ Script Installers / Installer Updates, and ensure Download script updates is set to Yes to automatically receive the latest install script updates.

System upgrade

How do I upgrade my system from one major version to another?

Upgrading major versions of your Linux distribution, such as from Ubuntu 22.04 to 24.04, AlmaLinux 8 to 9, or Debian 11 to 12, is a significant process and is not something we can assist with. It’s important to note that distro upgrades can sometimes lead to complications. Some users might experience issues that require manual intervention to resolve, while others may find the upgrade process smooth and without major problems. We strongly recommend that such questions be directed to the respective forums or support communities. They are better equipped to provide detailed, distribution-specific advice and guidelines for the upgrade process.

Remember, it’s always a good idea to backup your data before attempting any major system upgrade.

User interface

What are the key terminology differences between cPanel and Virtualmin

Virtualmin and cPanel have key differences in terminology — in Virtualmin, what cPanel refers to as “domain” is called a “Virtual Server”, “add-on” domains roughly akin to a “sub-server” and “parked domain” may be comparable to an “alias”. “Subdomains” as they appear in cPanel are not usefully comparable to anything in Virtualmin. Either a Virtual Server or a Sub-Server can have a subdomain name. A subdomain is just a name to Virtualmin. A sub-server in Virtualmin is a domain owned by a top-level or parent Virtual Server, it has no relation to how it is named.

What modules are included in the ‘Un-used Modules’ section in Webmin?

Un-used modules means “Modules that are installed but for which the detection logic in the module did not find the related packages installed”. Any module that has service detection functions will end up in un-used modules if it does not detect the service or application it manages. The way to get a module out of unused modules is to install the related package. Many standard modules will be in unused modules on any given system, because no system should be doing everything a Webmin system can manage, that’d be a chaotic.