The Virtualmin message is unrelated to the server message.
The latter message from Virtualmin is saying something has changed that wants a reboot (like a kernel upgrade). That’s something that already happened; you have already upgraded whatever package it is that wants a reboot. You just need to reboot to get the new kernel, or whatever. That’s a minor thing, assuming you didn’t enable any weird third party repos or anything. Just reboot. It’ll be fine.
The server message is saying there is a distribution upgrade available to 18.04.1. That would be a big deal, regardless of Virtualmin being involved. Upgrades are expected to work, because upgrading does not change the network configuration system (so it’ll be the old one, which has no known issues, or at least, no serious ones). But, upgrading the distribution is something that should not be embarked upon lightly. It will break your web applications, and will need to tweaking to bring them back. Virtualmin can usually fix some of it…just do a “re-check configuration”, so it can learn about the new PHP version, and update all the config files, but don’t plan on it…expect the worst, and you’ll be pleased when it goes easier than expected, rather than expecting an OS major version change to be completely free of problems. But, databases might need attention, etc.
And, if you do a system upgrade, you must have good backups of everything.
In short: Updates are minor, do them every day. An OS upgrade is major, do it only after preparing for the worst and only if it will give you something you need (like a new version of PHP or something that you need for a specific application).
The latest Virtualmin works fine with Ubuntu 18.04.1 LTS so far, however install.sh script still don’t state about supporting 18.04.1 LTS.
UPDATE, day after.
DO NOT INSTALL VIRTUALMIN ON PRODUCTION SERVER YET, AS IT ISN’T SUPPORTED. I spent all night trying to fix the Network Interfaces. If you have only 1 IP that’s probably fine, but I have a lot IPs and there was a problem with Network Configuration…
First put your netplan config in “code” brackets. The spacing and hierarchy matters. What you pasted is useless for diagnosing.
Second, when running netplan apply, it tells you the line number and column where the errors are. Open the config file, space down and over that number and see whats wrong.
But all you need is IP and gateway. This should get you going. Although I think that /24 on the ip should be /32, that is unless you where allotted all 254 addresses of the 207.180.193.x block. It can always be /32. Note spacing below must be spaces not tabs and hierarchy matters. Also note, quotes around IPV6 addresses are required.
network:
version: 2
ethernets:
eth0:
dhcp4: no
dhcp6: no
addresses: [207.180.193.199/32]
gateway4: 207.180.193.1
nameservers:
addresses: [127.0.0.1,“2606:4700:4700::1111”,“2606:4700:4700::1001”,1.1.1.1,1.0.0.1]
I dont know what those “invalid addresses” you listed are for as they are not even in your IP subnets. But get ipv4 going, then add ip6 stuff. Should only require additional ip and gateway. Of which gateway6: fe80::1 is wrong. Fe80 = localhost and a gateway cant be localhost.
Using the script on Ubuntu 18.04 I’m not able to manage the emails to sign with DKIM, any of you think is a bug for using the latest LTS of ubuntu and the script?
Does that work for you?
Thanks.
Update: LOG: warning: connect to Milter service inet:localhost:8891: Connection refused
However, that was not the whole fix sadly. When I do this, after and then reboot VPS, I can’t connect either via browser, ssh or ftp and ‘virtualmin check-config’ returns :
'Virtualmin could not work out the default IPv4… ’
Hi, no I used it as a boilerplate but kept all other data from my own file. On my old file I had eth0 so I kept it. Anyway, I will double check and try once more and if I have problems I will probably quit this and install Centos 7 instead. Thanks for the reply!
The first time I rebooted, the network was down (I had to access through VNC from my VPS provider), but tweaking above settings (I had a /36 prefix for IPv4 address, instead of /24 for example, or forgot to put the right interface name, …) copying them from the previous default .yaml file, but keeping the exact structure worked really fine, and I’m right into Virtualmin now.
Actually, it seems Virtualmin continues to aggressively change the netplan conf.
After the installation, I find the nameservers wrongly set:
# netplan apply
/etc/netplan/01-netcfg.yaml:9:28: Error in network definition: malformed address ' 213.136.95.11', must be X.X.X.X or X:X:X:X:X:X:X:X
addresses: [127.0.0.1,213.136.95.10,' 213.136.95.11']
I had to go back and delete the single quotes around that IP and the preceeding space.
Because I’m a bit of a nut when it comes to dns stuff, come to find out, postfix was sending out the wrong banner. It didn’t update to the new hostname, so I went into
Webmin->Servers->Postfix Mail Server->General Options and set
Internet hostname of this mail system to Default (provided by system)
Local internet domain name Default (provided by system)
Restarted Postfix and the SMTP banner is now correct and looking back in General Options, it’s back to a custom setting with the right info this time.
Thanks for the reply!