Hi, I’m trying to set up a virtual server. I’m using Debian 10 with Virtualmin as Webmin Module.
Here is what happens after creating a virtual server:
Creating administration group cloud ..
.. done
Creating administration user cloud ..
.. done
Creating aliases for administration user ..
.. done
Adding administration user to groups ..
.. done
Creating home directory ..
.. done
Creating mailbox for administration user ..
.. done
Adding new DNS zone ..
.. done
Adding new virtual website ..
.. done
Adding webserver user www-data to server's group ..
.. done
Performing other Apache configuration ..
.. configuration failed : PHP execution mode mod_php was selected, but is not supported on this system!
Creating MySQL login ..
.. done
Re-starting DNS server ..
.. done
Applying web server configuration ..
.. done
Saving server details ..
.. done
So Apache2 seems to have a big problem. And if I open the subdomain in browser, I see the document root of the root user, not of the created user.
How did you install Virtualmin? Did you use install script? If not you gonna have a lot of small issues like that. I’d recommend start with using installer script.
I used the official install script. And I already installed php-fpm and libapache2-mod-fcgid via apt but this doesn’t changed anything.
:~# apt-get install php-fpm libapache2-mod-fcgid
Reading package lists... Done
Building dependency tree
Reading state information... Done
libapache2-mod-fcgid is already the newest version (1:2.3.9-4).
php-fpm is already the newest version (2:7.3+69).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
:~# a2enmod fcgid
Module fcgid already enabled
After I saw so many screenshots, where the menu looked different to mine I decided to reinstall everything, and looks much better now. I were able to configure virtual servers for the main domain, and subdomains.
Sometimes I see an error in this situation, something like “… error in line 37 in pem file …”. Yesterday I had this when trying to activate ssl on an sub server. I found out
that I had to remove the (maybe old?) ssl.* files in the vhost’s main dir. After that, ssl activation worked and creating Letsencrypt cert, too.