Virtualmin restore-domain on RL 10.1 giving error

Virtualmin
1

hello -

i am moving ahead on RL 10.x. Doing virtualmin restore-domain is giving me:

Module webalizer does not exist

and doing dnf install webalizer no longer appears to work:

No match for argument: webalizer

is webalizer critical to getting virtualmin restore-domain to work properly? i wanted to ask before i spent too much time looking around for it.

thank you.

EDIT: this page points to a homepage that no longer exists.
i have posted this question on the RL forum in case this is critical.

EDIT(2): i found an rpm and installed, trying out virtualmin restore-domain again.

i get the feeling its not maintained anymore:
Webalizer V2.23-08 (Linux 6.12.0-124.21.1+2.1.el10_1_ciq.x86_64 x86_64) English Copyright 1997-2013 by Bradford L. Barrett

SYSTEM INFORMATION
OS type and version RL 10.1
Webmin version 2.621
Virtualmin version latest
Webserver version Apache/2.4.63
Related packages SUGGESTED
2

Yeah, we no longer support Webalizer, as it has been unmaintained for years. You probably don’t want it.

You can restore a domain with some features disabled, or, better, if you have the original server and can make new backups, just disable that feature before backing up.

1 Like
3

nohup nice virtualmin backup-domain --dest … --all-virtualmin \
–all-features --except-feature webalizer \
–all-domains &

2 Likes
4

well darn that didnt work… i did both backup-domain and restore-domain using:

–all-features --except-feature webalizer

but i still get:

[05/Feb/2026:23:55:07 +0000] Module webalizer does not exist

EDIT: trying again after this:

/usr/bin/sed  --in-place  --expression='s/^backup_feature_webalizer=1$/backup_feature_webalizer=0/;'   /etc/webmin/virtual-server/config  ;   ## 2026-02-05
/usr/bin/sed  --in-place  --expression='s/^webalizer=1$/webalizer=0/;'                  /etc/webmin/virtual-server/config  ;   ## 2026-02-05

damn… still gives me:

06/Feb/2026:02:07:00 +0000] Module webalizer does not exist

EDIT: going to go to the source backup-domain and make sure its disabled there before even starting. wish me luck…

5

Would domain transfer handle this better?

6

That’s what I recommended.

But, you should also be able to specify which features to backup, but I think you’ve got conflicting options. If you say --all-features you get all features. You’d just use --except-feature webalizer to exclude that feature.

1 Like
7

thank you.

trying again… i (mis)interpreted --all-features --except-feature webalizer to mean “all, except”.

EDIT - we must list at least one feature so i will try again listing just the features i need.

this is an extremely useful command i was unaware of: virtualmin list-features;

now i am trying again just listing my necessary features individually:

virtualmin backup-domain \
–dest /../virtualmin.tgz \
–feature dns \
–feature web \
–feature ssl \
–feature dir \
–all-virtualmin \
–all-domains ;

Note: on the Edit Virtual Server page, the dir option is not listed with the Enabled features section but instead is in Virtual server details section. Omitting it just creates a VS without any data. although i have found omitting this and creating a new VS to be very handy occasionally.

8

now i am trying to do VS’s individually but getting a new error, so i am reposting this:

9

Hmm… that’s bug-like. If --except-feature doesn’t work with --all-features, then --except-features should mean all features except the ones specified, because otherwise --except-feature is completely useless. I’ll ask @Jamie to take a look.

10

since i am only using four features, i just decided to specify them individually.

11

Try adding the flag --only-features to not setup the restored and re-created domain with Webalizer enabled.

1 Like
12

Yet can users use --all-features with --except-feature webalizer? It’s perfectly logical to expect it would work, I think.

1 Like
13

my thinking now is that when i first installed this webmin/virtualmin, i was “rushing” since i was under the Centos/RockyLinux conversion deadline and the originall installation was never clean.

so the mysterious issues i face are probably due to my faulty installation. :astonished_face:

so for now, i will just re-create the domains on the NEW server and use tar.

once the server migration is completed, i will revisit this, although i strongly suspect it will work perfectly.

14

There’s a subtle difference when the restore re-creates a domain that doesn’t exist on the destination system. If you omit --only-features, the re-created domain will try to include all features that were on the original system, BUT may not restore the settings for all those features.

However, if --only-features is given, the domain will only be re-created with the features selected to restore.

I admit this is confusing, so maybe we should change it :slight_smile:

1 Like
15

it might be very useful to include a couple of your examples here.

but the more i think about it, the more i realize, at least for now, that its far easier for me to just have a series of virtualmin create-domain commands since i only have four services.

here is an example:

openssl rand -hex 12
| xargs virtualmin create-domain --domain XX.com --dir --unix --dns --web --ssl --pass {} ;

my long-term goal is to have scripts that do the entire migration for me, so once a year or so i can just run a bunch of scripts and quickly migrate.

16

Given the fact that restoring a domain onto a new system without a feature that was available on the old system is very common (because we’ve deprecated a few features over the years), and restoring fails with no obvious way to avoid it, it’s currently a pretty bad user experience.

I don’t actually know how to do what needs to be done to restore this domain, given what you just said. It seems like a “can’t get there from here” problem, which isn’t great UX.

17

In this specific case, the user should be able to just add the flag --only-features to the end of the restore-domain command.

But yeah this should be the default I agree..