Well it is running fine on Ubuntu 20.04 with newest Webmin version 1.952 and Usermin version 1.801 Virtualmin version 6.09 Authentic theme version 19.51 Time on system [Sunday, July 5, 2020 5:11 PM] Kernel and CPU Linux 5.4.0-40-generic on x86_64 Operating system Ubuntu Linux 20.04 Processor information Intel® Core™ i7-7700 CPU @ 3.60GHz, 8 cores Real memory 2.19 GiB used / 28.16 GiB cached / 62.6 GiB total.
Nobody is pushing here I asked only for a clear answer and not again and again unclear etas. If it is ready and tested and it is said to be released on the weekend so it is not in a few days - simple logic for anybody who writes programs. I know it is hard work and it could be much less work for any of them by sharing and collaborating with the community.
In an open Source Community you usually work together but you can’t really work together when the open source code is not accessible for collaboration. So the only way to get things done is feedbacks and feedbacks and our feedback went already as a fix by Ilja into vm for 20.04 long time ago (t’was the MariaDB fix)- simply check.
But there is another problem when installing actually and that is what the devs need to be aware of . It might be that it is only valid if you install it on a fresh minimal 20.04 Ubuntu install at Hetzner but probably it is a problem which also exists in all minimal 20.04 distribution elsewhere.
When you install virtualmin with the 20.04 script on a blank new Ubuntu 20.04 it will install Mysql and has some hickups, even you installed i.e. dummy packages. When you install first MariaDB and then install virtualmin it will overwrite MariaDB with mysql but less hickups and you need to reinstall Mariadb client and server after the install again. But that works now just perfect with MariaDB 10.5.4 (stable) - Ubuntu comes with 10.3. …
The webalizer script is usually in webalizer/webalizer.conf but the script is asking for webalizer.conf. so you need to move the webalizer.conf file one folder higher and the installation will finish.
Unfortunately the script pulls an old webmin 1.942 from the repo here the netplan issues have not been solved and when you reboot you will be probably be out of luck to reconnect!
Solution is before rebooting to update to webmin 1.952 - install the repo of webmin and update.
You also need to update the authentic theme to 1.951 but that is not enough as still the connectivity problem will exist because virualmin is writing on top of run/systemd/resolve/stub-resolv.conf file lots of stuff which does not belong there. When you restore the previous file before the installation it works fine.
# Added by Virtualmin.
nameserver 127.0.0.1
# Added by Virtualmin.
nameserver 127.0.0.1
nameserver 127.0.0.1
nameserver 213.133.100.100
nameserver 213.133.98.98
nameserver 213.133.99.99
nameserver 2a01:4f8:0:1::add:1010
nameserver 2a01:4f8:0:1::add:9999
nameserver 2a01:4f8:0:1::add:9898
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
options edns0
before the installation it looked like:
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0
it also modifies etc/netplan/01-netcfg.yaml
before the installation it looks like that
### Hetzner Online GmbH installimage
network:
version: 2
renderer: networkd
ethernets:
enp0s31f6:
addresses:
- 12.123.1.12/32
- 1234:123:12:123::2/64
routes:
- on-link: true
to: 0.0.0.0/0
via: 12.123.1.45
gateway6: fe80::1
nameservers:
addresses:
- 213.133.100.100
- 213.133.98.98
- 213.133.99.99
- 2a01:4f8:0:1::add:1010
- 2a01:4f8:0:1::add:9999
- 2a01:4f8:0:1::add:9898
and after the installation it looks like
### Hetzner Online GmbH installimage
network:
version: 2
renderer: networkd
ethernets:
enp0s31f6:
addresses: ['12.123.1.12/32', '1234:123:12:123::2/64']
gateway6: fe80::1
nameservers:
addresses: [127.0.0.1, 213.133.100.100, 213.133.98.98, 213.133.99.99, '2a01:4f8:0:1::add:1010', '2a01:4f8:0:1::add:9999', '2a01:4f8:0:1::add:9898']
routes:
to: 0.0.0.0/0
via: 12.123.1.45
it adds 127.0.0.1 - which is only necessary when using bind -and it leaves out routes: - on-link: true
Restoring both files will bring back also full internet connectivity and you will be able to access your site again after an installation of VM.
All statistics are now working fine in webmin so you can see again the running proceses and more.
Problem exist still with letsencrypt which not always produces an SSL certificate. This wasn’t like that in previous virtualmin version where it was working just fine.