These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for When Virtualmin Install Script will be ready for the new Debian 9 on the new forum.
Web Hosting and Cloud Computing Control Panels
I mean, is the Virtualmin Install Script is ready for new Debian 9?
Thanks in advance for the answer!
I also would be grateful for Debian 9/Stretch Support for virtualmin (gpl)
It's coming. We usually add support within a few days of release. Sometimes it takes longer, if there's something complicated about it, but everything new in Debian 9 has already been supported in some other OS (systemd, mariadb, php7 are the obvious big changes), so it should be easy to port.
--
Check out the forum guidelines!
Hi, Joe! Can you post here when the Virtualmin Install Script (gpl) is ready for the new Debian 9.
It will be much appreciated!
Thank you in advance!
Hi everybody,
I'm running on Debian 9 for a new project and want to install Virtualmin with nginx/php7/php7-fpm/MariaDB .
When do you plan to release a new install script?
Thanks in advance. Best regards
Hi, Joe!
Can you tell us a deadline (approximately) for the Virtualmin installation script?
This uncertainty and waiting kills us!
Thank you for understanding!!!
I too would like to install Virtualmin on Debian 9 / Stretch.
Hi, unfortunately it is still impossible to install Vmin via script. What a surprise - Debian Stretch came over night and nobody knew!? We send all of our customers to use/buy the Pro-version. So I am no free-loader who complains. But knowing that Strech is arriving lots of time and it doesn't work till today is a pity.
Sorry for that - but I am really upset because of this.
Regards Walhalla
for anyone who cannot wait and want to try it, install debian jessie, then install virtualmin and then do distro upgrade..or if you sit on jessie, just do distro upgrade, reboot couple of times and you should be on debian9. I've done this accidentally but it all works. Normally I would wait for couple of months with upgrade like this or do fresh install but its done now.
Configuring/troubleshooting Debian servers is always great fun
Reading state information... Package php5 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source
Package php5-mysql is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source
Package php5-cgi is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source
Package libapache2-mod-php5 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source
debian seem to have removed old versions .
Reading package lists... Building dependency tree... Reading state information... Package php5 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source
Package php5-mysql is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source
Package php5-cgi is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source
Package libapache2-mod-php5 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source
One of the most interesting changes in stretch for those of us hosting websites, is it is now much easier to run multiple php versions. That is, instead of the php5 packages, it now gives the choice of php5.6 and php7.0 without needing to add 3rd party repositories. That is one of the things the installer script needs to take into account when it is updated, so it calls the right package names. In fact, there's probably no reason the updated installer shouldn't install both.
apt-get update && apt-cache search ^php
I'm working on it, y'all. New distro support is always a lot of work (even an easy one, like this one). Tons of very slow testing (each new install takes several minutes, if I want a really good test I have to start with a freshly imaged VM). It's coming as soon as possible.
I don't want to make a firm estimate, but I'm working on it today (and worked on it yesterday). So, it's coming soon.
--
Check out the forum guidelines!
It's kinda sorta done, but untested. See the Virtualmin 6 beta thread in the news forum for the link to the vm6-install.sh script (it's the same vm6-install.sh linked at the top of the thread, it's been updated for Debian 9).
It is definitely not recommended for production as my testing has been very limited (I had to make my own Debian 9 VM and it's got a ton of weird quirks). I'm still working on getting the bugs worked out in the VM. But, I know all of the dependencies are in place in our repos (there's a new virtualmin-stretch repo, and a new version of virtualmin-lamp-stack metapackage for Debian 9).
If you try it, post any errors you run into. If it fails (ClamAV and quota errors are expected in many circumstances even when everything went as right as it can), post the last few lines of the log here and which item(s) during the install failed (you'll know which items failed because they'll have a red X instead of a green checkmark).
--
Check out the forum guidelines!
I have successfully installed Virtualmin. But I have problem to Save in> Network Configuration> Hostname and DNS Client> DNS Client Options!
The problem is that in> Features and Plugins when i want to enable BIND DNS domain, i get this ERROR:
Failed to save enabled features: Virtualmin is configured to setup DNS zonesq but this system is not setup to use itself as a DNS server. Either add 127.0.0.1 to the list of DNS servers, or turn off the BIND feature on the module config page.
I tried to add 127.0.0.1 in> Network Configuration> Hostname and DNS Client> DNS Client Options..but nothing happens, when i click the button Save. Nothing is saved!
I can't add 127.0.0.1 or anything New and to Save the configuration!
Help!
My Server is with new Debian 9
I reinstalled webmin, usermin and virtualmin..
When i click on Re-Check Configuration, I get this:
The status of your system is being checked to ensure that all enabled features are available, that the mail server is properly configured, and that quotas are active ..
.. your system is not ready for use by Virtualmin.
I tried to add 127.0.0.1 in> Network Configuration> Hostname and DNS Client> DNS Client Options..but again!..nothing happens, when i click the button Save. Nothing is saved!
I can't add 127.0.0.1 or anything New and to Save the configuration!
Any ideas?
I got that message, too, but I had no problem updating it. I just clicked on the link within the message itself and it took me to the right place. It is just adding it to /etc/resolv.conf, so you can add it manually if you want. Also, that raises the question, are you logged in as a user with enough privileges to make the change (ie. root)?
Yes, i am log in as a root user.
I tried manually to add in
/etc/resolv.conf
nameserver 127.0.0.1 and now is working!
But after I Restarted the server the /etc/resolv.conf is Generated by NetworkManager and again the problem is here!
???
Did you do a minimal install of Debian? You really don't need NetworkManager on a server. Personally, I'd ditch it in this case as it's getting in the way of your configuration.
Seems like you're using DHCP to set your IP and network configuration. That's not really suitable for servers (Virtualmin will work with it, but it's a bad idea on a bunch of other fronts). You can configure NetworkManager to include 127.0.0.1 as a DNS server on the system, even if you don't switch to a statically configured network.
Also note this warning is about a few optional features of Virtualmin; it is not strictly mandatory, it just allows the Virtualmin Preview Website feature to work even before DNS propagates, among other things.
--
Check out the forum guidelines!
When I go to Features and Plugins and uncheck checkbox BIND DNS domain i get this:
The status of your system is being checked to ensure that all enabled features are available, that the mail server is properly configured, and that quotas are active ..
Your system has 7.28 GB of memory, which is at or above the Virtualmin recommended minimum of 256 MB.
Mail server Postfix is installed and configured.
Postfix can support per-domain outgoing IP addresses, but is not currently configured to do so. This can be setup in the Postfix Mailserver module.
Apache is installed.
The following PHP versions are available : 7.0.19 (/usr/bin/php-cgi7.0), 7.0 (mod_php)
PHP-FPM support is available on this system.
Webalizer is installed.
Apache is configured to host SSL websites.
MySQL is installed and running, but does not have any root password set! This should be changed immediately in the MySQL Database module.
ProFTPD is installed.
Logrotate is installed.
SpamAssassin and Procmail are installed and configured for use.
ClamAV is installed and assumed to be running.
Plugin AWstats reporting is installed OK.
Plugin DAV Login is installed OK.
Plugin Protected web directories is installed OK.
Using network interface enp0s25 for virtual IPs.
Default IPv4 address for virtual servers is 192.168.0.185.
Default IP address is set to 192.168.0.185, but the detected external address is actually XX.1XX.66.0. This is typically the result of being behind a NAT firewall, and should be corrected on the module configuration page.
Both user and group quotas are enabled for home and email directories.
All commands needed to create and restore backups are installed.
The selected package management and update systems are installed OK.
Chroot jails are available on this system
.. your system is ready for use by Virtualmin.
But when i try to enable again checkbox BIND DNS domain, i get this:
Failed to save enabled features : Virtualmin is configured to setup DNS zones, but this system is not setup to use itself as a DNS server. Either add 127.0.0.1 to the list of DNS servers, or turn off the BIND feature on the module config page.
I again tried to add 127.0.0.1 in> Network Configuration> Hostname and DNS Client> DNS Client Options..but again!..nothing happens, when i click the button Save. Nothing is saved!
I can't add 127.0.0.1 or anything New and to Save the configuration!
I don't have any new ideas what to do!
THE SOLUTION:
https://wiki.debian.org/NetworkConfiguration#Using_DHCP_to_automatically...
The resolv.conf configuration file
The configuration file resolv.conf at /etc/resolv.conf contains information that allows a computer connected to a network to resolve names into addresses. (Note: Do not confuse this configuration file with the program resolvconf, which unfortunately has a nearly identical name.)
The resolv.conf file typically contains the IP addresses of nameservers (DNS name resolvers) that will attempt to translate names into addresses for any node available on the network. There will be a line or lines that look like this:
nameserver 12.34.56.78 nameserver 12.34.56.79
In this example, the system is using nameservers at the IP addresses 12.34.56.78 and 12.34.56.79. Simply edit the file and enter the IP addresses of the nameservers you need to use after each nameserver. Add more nameserver lines if you have more nameservers. Don't use this method if you have the resolvconf program installed.
The resolv.conf configuration file has many other options for defining how resolver looks up names. See man resolv.conf for details.
The resolvconf program
The resolvconf program keeps track of system information about the currently available nameservers. It should not be confused with the configuration file resolv.conf, which unfortunately has a nearly identical name. The resolvconf program is optional on a Debian system.
The configuration file resolv.conf contains information about the nameservers to be used by the system. However, when multiple programs need to dynamically modify the resolv.conf configuration file they can step on each other and the file can become out-of-sync. The resolvconf program addresses this problem. It acts as an intermediary between programs that supply nameserver information (e.g. dhcp clients) and programs that use nameserver information (e.g. resolver).
When resolvconf is properly installed, the resolv.conf configuration file at /etc/resolv.conf is replaced by a symbolic link to /etc/resolvconf/run/resolv.conf and the resolver instead uses the configuration file that is dynamically generated by resolvconf at /etc/resolvconf/run/resolv.conf.
The resolvconf program is generally only necessary when a system has multiple programs that need to dynamically modify the nameserver information. In a simple system where the nameservers do not change often or are only changed by one program, the resolv.conf configuration file is adequate.
If the resolvconf program is installed, you should not edit the resolv.conf configuration file manually as it will be dynamically changed by programs in the system. If you need to manually define the nameservers (as with a static interface), add a line something like the following to the interfaces configuration file at /etc/network/interfaces:
dns-nameservers 12.34.56.78 12.34.56.79
Place the line indented within an iface stanza, e.g., right after the gateway line. Enter the IP addresses of the nameservers you need to use after dns-nameservers. Put all of them on one line separated by spaces. Don't forget the "s" on the end of dns-nameservers.
The resolvconf program is a fairly new addition to Debian and many older programs need to be updated or reconfigured to work properly with it. If you have problems, see /usr/share/doc/resolvconf/README. It has lots of information on making other programs get along with resolvconf.
I addeded in at /etc/network/interfaces:
search 77.xx.xx.55 mydomain.com dns-nameservers 127.0.0.1 99.XX.66.0 192.168.0.1 192.168.0.165 dns-domain 77.xx.xx.55 mydomain.com
Hope this will help!
Hello all;
Any news about new script to install Virtualmin on debian 9 ?
Best Regrads, JC
If you are keen to get started, you could try the beta installer from this thread --> https://www.virtualmin.com/node/52613
It works pretty well, and the more people that try it and report their results, the faster everything will be ready.