After reboot the virtual server in virtualmin show number domain id not the real domain

Virtualmin
1
SYSTEM INFORMATION
OS type and version Debian 12, amd64
Webmin version 2.202
Virtualmin version 7.30.3
Webserver version Apache 2.4.62

After my vm in proxmox rebooted, the other of 23 virtual server is normal but 1 virtual server that shows only domain id not the real domain as usual. the configuration in /etc/apache2/site-available is still exist but when i try to access web show error 503 service unavailable.

The folder of domain and user are available but when i try to access of feature like file manager is showing error Error opening directory /public_html No such file or directory.
The database menu in the error virtual server also gone and only access in terminal.
If i go to virtual server summary the created virtualserver is Created on 01/01/1970 07:00 AM

How to fix it?, because other virtual server in my vm with this virtualmin is accessible with normal and not errror.

2

Restiore the domain in question from a backup should fix it

3

look at thsi thread you might be able to just restore a couple of files.

4

actually i don’t have a backup, because this virtual server account just created few day ago. I’m typically backup virtual server once a week because there is no updated database everyday

5

I don’t see the solutions actually, the staff asked for backup in /etc/webmin/virtual-server/domains, and yes the file and folder of my virtual server are accessible in /etc/webmin/virtual-server/domains.

If I can access that folder domain, what should i do for next step repairing my virtual server account?

6

Best the staff guide you on what to do next, that said if you took the backup after the damage occurred you will not get further

7

You don’t need to restore the whole domain, just the Virtualmin metadata. It’s actually just one file for each domain that is empty due to a file locking bug, that I’m pretty sure has been fixed in the current Virtualmin version (at least I’m pretty sure Ilia has said it’s fixed, I didn’t fix it or look at the code).

1 Like
8

A regular thing people assume is the virtualmin backups include the servers config files I /etc/

I have mentioned these backup features should be merged for clarity.

9

That’s not relevant to this issue, though. The metadata for a domain is in the domain backup.

I’m not talking about other kinds of backups (but I do agree we need to somehow better communicate what “good backups” look like and include, because just having Virtualmin backups is probably insufficient for disaster recovery if you have any customizations in the services Virtualmin manages, since a Virtualmin backup only includes the configuration that is specific to the domain itself…so the VirtualHost section from the Apache configuration, not the whole Apache configuration).

I’m just saying you don’t need to restore the whole domain. I believe you can use the --fix flag in the virtualmin restore-domain command to just restore this metadata, and I think it probably also has an option in the UI.

1 Like
10

whats is metadata virtualmin look a like, i just googling it and probably are file in /etc/webmin/virtual-server/ with .acl extension.

I try to saw it and here it is;

feature_webalizer=1
edit_backup=1
edit_spam=1
edit_dnsip=1
admin=
edit_sharedips=1
nodbname=0
feature_virt=1
edit_ssl=1
edit_users=1
noconfig=1
migrate=0
feature_ssl=1
edit_ip=0
allowedscripts=
edit_admins=1
ipfollow=
feature_unix=1
edit_aliases=1
edit_scripts=1
edit_delete=0
edit_spf=1
edit=2
feature_ftp=1
edit_allowedhosts=1
feature_dns=1
feature_virtualmin-awstats=1
feature_spam=1
stop=0
safeunder=0
edit_redirect=1
feature_mail=1
edit_forward=1
edit_domain=1
forceunder=0
feature_logrotate=1
feature_mysql=1
feature_web=1
edit_restore=1
feature_virus=1
edit_disable=1
edit_phpmode=1
edit_dbs=1
create=2
import=0
edit_phpver=1
edit_sched=1
feature_webmin=1
edit_records=1
edit_passwd=1
local=0
edit_mail=1
feature_postgres=1
feature_dir=1
norename=0
edit_catchall=1
domains=17223031892264151

if i can restore or fix this problem with this file, what is right terminal command to do it.

i assume;

virtualmin restore-domain thedomain.com --fix --file source /etc/webmin/virtual-server/file.acl

CMIIW

thx before.

11

The very last example in this tutorial:

1 Like
12

This absolutely cannot work. The restore-domain command needs a Virtualmin backup file (which will be a tarball) for the --source field, and a --domain that is the domain name being restored. Ilia has linked an example, last one on the page.

Copying here for convenience:

virtualmin restore-domain --source /path/to/example.com.tar.gz --domain example.com --feature virtualmin --fix

If you do not have Virtualmin backups from before the problem occurred, this obviously cannot work. There are ways to fix it without backups, but it’s a lot more trouble (and please start keeping good backups).