I just bought and installed Virtualmin Pro on a fresh install of CentOS 5. Here is what has happened so far…
Initially I made my first virtual server - life is good.
I tried to make a second and I got the AWStat error and was unable to add another - I FIXED that.
I now have 2 virtual servers, but the first one points to the second one. I tired the fixes listed in the forums, but nothing works. I thought I might be over looking something, but I have checked and rechecked and changed settings… I haven’t reinstalled because this was supposed to be a quick fix.
Any help would be great! I still have ~20 days for a refund so I am trying to get these issues worked out sooner than later.
I just deleted one of three v servers. If I use the www.deletedserver.com it still points to the first server. So this seems like a redirect problem? Please help.
I just reinstalled CentOS and Virtualmin.. uninstall of Virtualmin didn't work. Same problem.
Just for future reference: This is almost never a useful exercise. If it was broke the first time, there’s no reason to think doing the same thing again will fix any problems.
Any help would be great! I still have ~20 days for a refund so I am trying to get these issues worked out sooner than later.
You have as long as you need for a refund–if the software doesn’t work for you, we would never refuse to issue a refund. Ever.
I tried to make a second and I got the AWStat error and was unable to add another - I FIXED that.
What AWStats error?
I now have 2 virtual servers, but the first one points to the second one. I tired the fixes listed in the forums, but nothing works. I thought I might be over looking something, but I have checked and rechecked and changed settings... I haven't reinstalled because this was supposed to be a quick fix.
This one is always easy to fix.
It’s either:
IP mismatch–you’ve told Virtualmin to setup hosts on an IP address that Apache isn’t configured to deal with for virtual hosting. Check the NameVirtualHost directives (“NameVirtualHost *” is pretty much always wrong on a virtual hosting system and if you have one for an IP that doesn’t match the VirtualHost sections later, that would also be a danger sign). Virtualmin tries to guess these things during installation, but if you have multiple interfaces, it can guess the wrong one, and you’ll need to correct it in the Virtualmin Module Configuration.
VirtualHost misconfiguration. Again, * is pretty much always the wrong choice in a virtual hosting system (but a very common mistake), and having any that don’t match the NameVirtualHost directive(s) will also cause breakage.
DNS pointing to the wrong address. This one seems unlikely in your case.
This would have nothing to do with your problem–and wouldn’t do anything good. I’m not seeing where anyone suggested such a redirect in the three at 7123…if anyone did, it’s definitely not good advice for this problem.
In other words: Don’t do it. (It’s actually kind of a nonsensical redirect.)
I just discovered that if I use the internet browser on the server and type in the sites just as I would normally - they all work. I am thoroughly confused now.
We’ve gotten this one figured out, and I’ll summarize for posterity, in the event anyone else is seeing this.
The problem is DNS. The DNS servers configured at your registrar are still pointing at your old host. The redirect you’ve created is pointing to the server by IP, but the IP address (like http://192.168.1.1/) contains no hostname…so Apache only knows that you want something on the server–it has no clue what virtual host you want on the server. So it serves the first on the matches the data it has (IP and port), no matter where the request started out trying to go…the data is completely gone from the interaction by the time the browser gets around to asking your Virtualmin server for it.
The solution, of course, is to update the name server records at your registrar to point to the Virtualmin server. Or, if you don’t want to let Virtualmin manage your DNS, update the current name servers to have accurate name data.