I recently changed my server’s hostname and default domain in Virtualmin. Since making these changes, I’ve been unable to create a complete server backup. When I try, the process fails and I receive an error — I’ve attached a screenshot of the backup log showing the issue.
Has anyone experienced this before, or can someone help me troubleshoot what might be causing the problem?
as you can see from the arrow the folder virtualmin can not find the directory that the default domain is expected to live in. Are you hosting a domain in virtualmin with the same name as your hostname ? If so you shouldn’t do that as it will give you all sorts of odd problems.
My server’s hostname is s1.domainname.com, and I’m hosting domain.com as a Virtual Server.
Everything was working perfectly when I was using my previous domain name.
This does not explain why the path /home/_default_hostname is being referenced on my vm system that path doesn’t exist and all domains are located in /home/<domain_owner>, so how did you rename the domain ?
Using a sub domain name as the hostname makes no odds unless you are hosting that sub domain, which would be a rule break. The _default_domain user appears to be just an odd choice of name for a virtualmin user, perhaps this has something to do with how the installer gets the sll certificate for webmin in the first place, as my virtualmin installs are old I have never had that username directory appear under /home, but we still don’t know how the OP renamed the default domain in the first place
I believe I may have accidentally deleted a folder named something like ‘defaulthostname’ from the home directory, which was listed alongside all my virtual server folders.
Thanks, @tpnsolutions is usually very reliable.
So I would expect that to work.
my one reservation though is (as suggested above) we are assuming all is up to date and using the latest OS/Webmin/Virtualmin
More to the point it appears that this linux user has lost it’s home and may have other effects on the virtualmin inferstucture we still don’t know how this domain was renamed, the OP is not forthcoming with that, after testing everything works for me so I guess the OP has used a different route
nevertheless, it should still be possible, either by examining a previous (good) backup or by executing a (good) disaster recovery plan.
Then starting over with the change documented.
so we can all stop guessing