| SYSTEM INFORMATION | |
|---|---|
| OS type and version | Ubuntu 24 |
| Virtualmin version | Version 7.30.8 Pro |
I have completely reinstalled everything and arrive at the same problem with Apache not accessing the sites in their locations /home/user/public_html?
I have gone through all the procedures outlined in my last post.
Thank you,
Coop
I don’t know anything about your last post. As far as I can tell, you’ve only posted to the forum this one time. Unless you’re talking about a PM to staff for Pro support, in which case you should probably follow up there instead of opening a new topic here.
But, if this is happening a new install, this is pretty much always because the system was not a freshly installed OS. It had some packages preinstalled and configured. Installing Virtualmin does not undo whatever was on the system before, so if there was already any configuration, you’ll probably still have it, and it’s probably broken for Virtualmin.
Did you start with a preinstalled Webmin or Virtualmin image from your hosting provider? If so, you shouldn’t have. They never get it right. I don’t know how they always manage to screw it up, but as far as I can tell, they always do.
Finally, if you installed extra packages (via apt) that include web applications on Debian or Ubuntu it will do what you’ve described. You should not install, e.g., phpmyadmin from apt on a Virtualmin system as it is not configured correctly to operate in a virtual hosting configuration.
I mean fresh fresh. I ran the .sh files so it would use the webmin repository. I made sure not to install anything. That’s where I’m at. Ya, you are correct in that I should have send it to support. But, I’m curious now that it’s on here.
You are not giving much to go on.
Did you use the instruction from the download page?
sudo sh -c "$(curl -fsSL https://software.virtualmin.com/gpl/scripts/virtualmin-install.sh)" -- --bundle LAMP
You shouldn’t use the Webmin repository for a Virtualmin installation (there are repos at download.webmin.com, which you shouldn’t use for Virtualmin, and repos at software.virtualmin.com that you should use for Virtualmin). You should use virtualmin-install.sh, which will setup the Virtualmin repositories, and Webmin will be fetched from there. It’s not clear which one you mean.
If you used the Virtualmin install script, and did not also use the Webmin install script first or after, and it really was on a freshly installed OS with no other packages or configuration, then that should rule out that problem (but it really is pretty much only that that causes the problem you have, unless you explicitly configure Apache to not server VirtualHosts).
The problem is somewhere in the Apache configuration. So, I guess show us that. Specifically, all the VirtualHost sections. You’ve got some configuration that’s breaking VirtualHost configuration, and I can’t guess what/where it is.
Are the 000-default.conf and ssl-default.conf sites enabled? They shouldn’t be, and a successful installation of Virtualmin would disable them. That would explain the behavior you’re seeing, too, since it has * as the IP and Virtualmin defaults to using an IP for VirtualHosts (and Apache will always prefer the * because it’s heuristic for choosing which VirtualHost to serve is insane).
I did install the webmin separate from the virtualmin as I remembered from a decade ago. Turns out we don’t have to do that anymore. I did 2 more installs and then we arived at the problem was apache 2 needed to be configured with *:80 and *:443 because the addy I had was the wrong net adaptor addy. Making “any” address the option solved the problem. I thank you all for helping me. You made me realize I had installed it wrong the first go around. Yep, that’s the problem. Now that I have done that I will try to install the SSL certs.
Thank you
–Coop
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.