out of sheer desperation, i went back into webmin–>Servers–>ApacheWebserver and tried to manually recreate one of the virtual servers I accidentally deleted, but that didn’t affect httpd.conf either.
I didn’t think it was applicable to RH variants but people disliked one huge axx file to manipulate. If something went wrong it was harder to maintain. In Debian the structure is for each website to have its own file under sites-enabled.
ok there is SOME activity with the httpd.conf file: whenever I go in and disable the virtual server Apache website I get the following lines written to the end of my /etc/httpd/conf/httpd.conf file:
On the current set up? Probably not. If you want to start from scratch, then it is a viable option. Virtualmin should ONLY be installed on a fresh OS . Installing it on an already configured system, even if it already has Virtualmin, is a disaster waiting to happen. Just way to much going on for a small team to try and test and bug fix with every new release.
Backups or starting over from scratch are the only real recovery modes. Period. End of.
wow - i wish i could thank you for that reply. intellectually, I am thanking you. emotionally, I am pissed off as hell. i KNOW you are right, unless Joe can salvage this.
So i checked the old thread, it is amazing how joe given this much time and still wiling to give more. @edwardsmarkf get backup of db, /home. then backup the vm/vps if possible.
connect with your hosting provider/or if you can clone the vps to a new vps to test.
You are making a lot of changes here and there, i still not get it how many edits you have made.
also if you can get a fresh vps and compare the setup if needed.
webmin/virtualmin is very powerful and comes with a responsibility. no one knows what steps you were taking and at what point it broke down and then what changes you made after it. if you have premium, get the backup to remote and local. get a clone copy of vps, sometime hosting provider can give a replicated vps. and then also get a new vps to review those changes. keep a log of each changes you made to revert back if needed.
That is a configurable option in Virtualmin. Virtualmin defaults to configuring things the way the OS configures things. We try to never surprise you.
EL distros, by default, put all the VirtualHosts in /etc/httpd/conf/httpd.conf.
Debian/Ubuntu distros, by default, put all the VirtualHosts in /etc/apache2/sites-available.
Either can be configured to behave the other way. But, I would generally recommend you do things that aren’t surprising, if you have other people also working on your servers. Surprises are bad.
Did you modify your Server Templates? I can’t figure out how you’d convince Virtualmin to do this unless you told it you wanted to control the whole VirtualHost and then deleted the config that would tell Virtualmin what to put in the VirtualHost in Server Templates.
I’ve covered how to probably troubleshoot that in your other thread, but I think you should focus on the more pressing problems and let this one sort itself out later. Seeing System Information is not a critical function. Get critical functions figured out first. (And, I suspect this problem has to do with removing the TLS certs out from under Webmin.)
