Trying to migrate to new server. After restore on new server, get error on Re-check Configuration - Virus filtering cannot be disabled

Help! (Home for newbies)
1
SYSTEM INFORMATION
OS type and version Debian 12
Virtualmin version 8.1.0

I’m following the Virtualmin documentation on migrating to a new server. The restore commands completes with no errors.

virtualmin restore-domain --source /root/backups/virtualmin.tar.gz --all-virtualmin
virtualmin restore-domain --source /root/backups/ --all-domains --all-features

When I try to re-check the Configuration, an error pops up:

.. your system is not ready for use by Virtualmin : The feature Virus filtering cannot be disabled, as it is used by the following virtual servers : ???.com

I stopped the Spamassassin process and tried re-checking the configuration again.

But no luck, same virus filtering error pops up.

Does anyone have any suggestions for me to correct this error?

2

Have you tried going to that domain, assuming ???.com is a stand in and not the actual error, and seeing if the domain has it turned on?

Without going into guessing on how that happened, I’d start there.

3

That ???domain is active. It just have the Virtualmin landing page.

I tried also deleted the spam filter feature for that ???domain. But still got the same error that Virus filtering cannot be disabled.

4

I deleted all the added servers. Still had same error on Re-checking Configuration.

My next step will probably be to re-install the server from scratch.

5

So bothersome!

I reinstalled Debian 12. Check configuration completed successfully.

Just got one domain backed up. Restored it with:

virtualmin restore-domain --source /root/backup1/virtualmin.tar.gz --all-virtualmin
virtualmin restore-domain --source /root/backup1/ --all-domains --all-features

Upon finishing the restore, I re-check the configuration —> original virus filtering error!

Arghh!

Do I have to restore with both commands? Or is there another way to restore?

Anyways, another reinstall of Debian 12 is in order.

Any suggestions are appreciated.

6

The virus feature is clamav, not spamassassin.

In your new VMin install did you select to have clamav? It’s off by default.

If you start clean again, stop after restoring --all=virtualmin and then check configuration before restoring the domains.

If you are using VPS, take a snapshot after installing VMin but before restoring anything.

If you don’t want to have clamav installed, go back to the old server and disable clamav for each server before doing the backups.

You could also try using Transfer Virtual Server which can work very well.

Best of luck.

7

I did select to have clamav on, both on the old and the new server.

Thanks for the suggestion. I will experiment with turning off clamav before making the backup.

edit:
Hmmm, where the heck is clamav turned off? I was expecting it to be under

Virtualmin > Edit virtual server
but I only see spam filtering (which I guess is spamassassin) and nothing regarding virus filtering

edit 2:
On the new server, under > Virtualmin > virtual server > Edit virtual server, I disabled the virus filtering.

Let’s see if that will do the trick

8

After disabling virus filtering on the only virtual server on the new server, I restored the Virtualmin configuration. Then Re-check Configuration was able to start.

But only to stop with error on Postfix configuration. It had the old server’s hostname in there.
—> I changed the Postfix config to the new server hostname
—> Re-check Configuration was able to complete. Ready for Virtualmin!

And I notice that BIND has the old hostname in there now also.

How to restore and not have the old hostnames get transferred over? Or is it meant that the new server has the same hostname as the old server?

9

Where can I change the default primary DNS server? Re-check configuration shows the old ns1:

BIND DNS server is installed, however, the default primary DNS server ns1.???.com resolves to IP address ??? which does not resolve to an IP address of a network interface on this system.

10

I had grief caused by this on RHEL.

virtualmin restore-domain --source /root/backups/virtualmin.tar.gz --all-virtualmin

First I restored only parts of it, email and templates - worked better, eventually noticed another issue so last server I created a few days ago I didn’t use it at all. I did have notes on most of the changes so I could do them manually.

1 Like
11

Can’t help with your DNS issue as I have my own separate DNS servers.

But not using the restore in my previous post might help.

12

I got to setup separate DNS servers one day.

I found the default DNS ns1 and ns2 under

Virtualmin > System Settings > Server templates > Default settings > DNS for domain

I replaced the old ns1 and ns2 with the new ones.
→ Re-check configuration didn’t complain about DNS

13

Perhaps one last problem to deal with:

Re-check configuration has detected an IPV6 address of the old server.

So, will have to figure out how to delete that.

14

Another problem: error when trying to change the PHP resource limits for the migrated virtual server (haven’t updated the domain registrar to point to the new server, if that matters):

Failed to save resource limits : Don’t know which file to add to

15

You can change php limits system wide:
Webmin, Tools, PHP Configuration, then on the right the greyed out (part of the new funky button design) Manage is actually a working button, then Resource Limits.

Better than doing it domain by domain.

16

Thanks for the suggestion.

I don’t know why, but Webmin > Tools > PHP-Configuration doesn’t show /etc/php/8.x/fpm/php.ini

That’s why I went the Virtualmin route to adjust the PHP Resource Limits.

In any case, due to the previous misalignments when I migrated the old virtualmin configuration to the new server, I think the mistake that I’m making is that:
the hostname of the new server must be the same as the old server ???

I don’t know if that’s the case, or whether I’m simply not following the instructions correctly.

I think that I will try:

  1. reinstall the OS
  2. use the new server to create the to-be-migrated-virtual-server
  3. only use the 2nd virtualmin migrate command on the new server to migrate the data over
    virtualmin restore-domain --source /root/backups/ --all-domains --all-features
17

In my last migration, I did the following:

#backup of the old server
mkdir /root/backups
virtualmin backup-domain --dest /root/backups/ --all-domains --all-features --newformat --all-virtualmin  

#Send the backup to the new server
scp -r /root/backups root@new-server.com:/root/

#restore in the new server
virtualmin restore-domain --source /root/backups/virtualmin.tar.gz --all-virtualmin
virtualmin restore-domain --source /root/backups/ --all-domains --all-features
18

Did the new server have a different hostname than the previous server? Did you have any problems like I’m having, with old references being retained on the new server?

19

I’ve been getting that on new servers lately, no relation to the restore, its before any restore.
I just disable the virus scanner in Features and Plugins.
Did you run re-check config first?

21

Yes, thanks. Your solution was the solution that I needed to get the Re-check configuration to complete after migration.

Before migration, the Re-check configuration completed successfully.

I seem to have a working migrated system after creating the virtual server on the new server (did not run the backup of the Virtualmin settings) and restoring the data.

On the new server, just had to remove old IPV6 DNS records (next time, I guess that I’d better setup the new IPV6 address on the new system before migrating over the old data).

1 Like