Not sure if this is related but I installed virtualmin on 18.04 and all seems to be fine except LetsEncrypt certificates are not installing. It seems that the necessary files in .well-known are not being created so the verification callback fails.
You wouldn’t have an .htaccess file with mod_rewrite on in your public_html dir?
nothing at all, it’s a totally empty domain.
If you add a file in the public_html directory, you can access it through the domain name?
That side of things is fine, I’ve tested. The problem is that the /.well-known/ directory and the necessary files within it are simply not generated at all. Is there any way I can find logs to give me some idea of what is happening?
OK I’ve found the letsencrypt logs in /var/log. And I found this line
2018-09-12 00:12:34,535:DEBUG:certbot.plugins.webroot:Attempting to save validation to /home/prod/public_html/.well-known/acme-challenge/0tn42AAtDk8wWBtjH6EBC6_b7q_XITel5oURR6a-Dms
But no error message and no file is ever created.
I’m just following up to say that I eventually tracked down the issue and it is unrelated to 18.04 - it was tied to the fact that there was an IPv6 IP on that domain and Virtualmin had not set the host to respond on IPv6. This was combined with the fact that certbot now deletes the challenge files after use - something that my old CentOS machines don’t do - so I was mistakenly thinking the files were never created. In fact, they were created then deleted.
sudo do-release-upgrade
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,258 kB]
Fetched 1,259 kB in 0s (0 B/s)
authenticate ‘bionic.tar.gz’ against ‘bionic.tar.gz.gpg’
extracting ‘bionic.tar.gz’
Reading cache
Checking package manager
Continue running under SSH?
This session appears to be running under ssh. It is not recommended
to perform a upgrade over ssh currently because in case of failure it
is harder to recover.
If you continue, an additional ssh daemon will be started at port
‘1022’.
Do you want to continue?
Continue [yN]
Starting additional sshd
To make recovery in case of failure easier, an additional sshd will
be started on port ‘1022’. If anything goes wrong with the running
ssh you can still connect to the additional one.
If you run a firewall, you may need to temporarily open this port. As
this is potentially dangerous it’s not done automatically. You can
open the port with e.g.:
‘iptables -I INPUT -p tcp --dport 1022 -j ACCEPT’
To continue please press [ENTER]
Reading package lists… Done
Building dependency tree
Reading state information… Done
Hit http://mirror.hetzner.de/ubuntu/packages xenial InRelease
Get:1 http://mirror.hetzner.de/ubuntu/packages xenial-backports InRelease [107 kB]
Hit http://de.archive.ubuntu.com/ubuntu xenial InRelease
Get:2 http://mirror.hetzner.de/ubuntu/packages xenial-updates InRelease [109 kB]
Get:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Get:4 http://mirror.hetzner.de/ubuntu/security xenial-security InRelease [107 kB]
Get:5 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Get:6 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB]
Hit http://ppa.launchpad.net/ondrej/apache2/ubuntu xenial InRelease
Hit http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease
Hit http://software.virtualmin.com/vm/6/gpl/apt virtualmin-xenial InRelease
Ign http://download.webmin.com/download/repository sarge InRelease
Hit http://software.virtualmin.com/vm/6/gpl/apt virtualmin-universal InRelease
Hit http://download.webmin.com/download/repository sarge Release
Fetched 646 kB in 0s (0 B/s)
Reading package lists… Done
Building dependency tree
Reading state information… Done
Updating repository information
Third party sources disabled
Some third party entries in your sources.list were disabled. You can
re-enable them after the upgrade with the ‘software-properties’ tool
or your package manager.
To continue please press [ENTER]
Get:1 http://de.archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
Get:2 http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:3 http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:4 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
Get:5 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1,019 kB]
Get:6 http://de.archive.ubuntu.com/ubuntu bionic/main i386 Packages [1,007 kB]
Get:7 http://de.archive.ubuntu.com/ubuntu bionic/main Translation-en [516 kB]
Get:8 http://de.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [9,184 B]
Get:9 http://de.archive.ubuntu.com/ubuntu bionic/restricted i386 Packages [9,156 B]
Get:10 http://de.archive.ubuntu.com/ubuntu bionic/restricted Translation-en [3,584 B]
Get:11 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8,570 kB]
Get:12 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages [8,531 kB]
Get:13 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [167 kB]
Get:14 http://de.archive.ubuntu.com/ubuntu bionic/universe Translation-en [4,941 kB]
Get:15 http://de.archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [151 kB]
Get:16 http://de.archive.ubuntu.com/ubuntu bionic/multiverse i386 Packages [144 kB]
Get:17 http://de.archive.ubuntu.com/ubuntu bionic/multiverse Translation-en [108 kB]
Get:18 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [322 kB]
Get:19 http://de.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages [286 kB]
Get:20 http://de.archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [122 kB]
Get:21 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [192 kB]
Get:22 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages [192 kB]
Get:23 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [90.1 kB]
Get:24 http://de.archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [4,180 B]
Get:25 http://de.archive.ubuntu.com/ubuntu bionic-updates/multiverse i386 Packages [4,336 B]
Get:26 http://de.archive.ubuntu.com/ubuntu bionic-updates/multiverse Translation-en [2,740 B]
Get:27 http://de.archive.ubuntu.com/ubuntu bionic-backports/universe amd64 Packages [2,704 B]
Get:28 http://de.archive.ubuntu.com/ubuntu bionic-backports/universe i386 Packages [2,704 B]
Get:29 http://de.archive.ubuntu.com/ubuntu bionic-backports/universe Translation-en [1,136 B]
Get:30 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages [132 kB]
Get:31 http://security.ubuntu.com/ubuntu bionic-security/main Translation-en [62.9 kB]
Get:32 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [66.6 kB]
Get:33 http://security.ubuntu.com/ubuntu bionic-security/universe i386 Packages [66.5 kB]
Get:34 http://security.ubuntu.com/ubuntu bionic-security/universe Translation-en [39.2 kB]
Get:35 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [1,444 B]
Get:36 http://security.ubuntu.com/ubuntu bionic-security/multiverse i386 Packages [1,608 B]
Get:37 http://security.ubuntu.com/ubuntu bionic-security/multiverse Translation-en [996 B]
Fetched 27.3 MB in 0s (0 B/s)
Checking package manager
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating the changes
Calculating the changes
No candidate ver: linux-image-4.13.0-36-generic
No candidate ver: linux-image-4.13.0-38-generic
No candidate ver: linux-image-4.13.0-39-generic
No candidate ver: linux-image-4.13.0-41-generic
No candidate ver: linux-image-4.13.0-43-generic
No candidate ver: linux-image-4.13.0-45-generic
No candidate ver: linux-image-extra-4.13.0-36-generic
No candidate ver: linux-image-extra-4.13.0-38-generic
No candidate ver: linux-image-extra-4.13.0-39-generic
No candidate ver: linux-image-extra-4.13.0-41-generic
No candidate ver: linux-image-extra-4.13.0-43-generic
No candidate ver: linux-image-extra-4.13.0-45-generic
Do you want to start the upgrade?
3 installed packages are no longer supported by Canonical. You can
still get support from the community.
16 packages are going to be removed. 226 new packages are going to be
installed. 625 packages are going to be upgraded.
You have to download a total of 530 M. This download will take about
1 hour 7 minutes with a 1Mbit DSL connection and about 20 hours with
a 56k modem.
Fetching and installing the upgrade can take several hours. Once the
download has finished, the process cannot be canceled.
Continue [yN] Details [d]
No longer supported: gcc-5-base gcc-6-base tcl
Remove: apache2 libnss3-nssdb libperl5.22 perl-modules-5.22 php-curl
php-imagick php7.0-curl virtualmin-lamp-stack
Remove (was auto installed) apache2-bin apache2-suexec-custom
libapache2-mod-fcgid libapache2-mod-php7.2 libcurl3
libmagickcore-6.q16-2 libmagickwand-6.q16-2 php7.2-curl
Install: autopoint binutils-common binutils-x86-64-linux-gnu
btrfs-progs cpp-7 dh-autoreconf dirmngr e2fsprogs-l10n fdisk
firebird3.0-common firebird3.0-common-doc fontconfig
fonts-droid-fallback fonts-noto-mono g+±7 gcc-7 gcc-7-base
gcc-8-base geoip-database gnupg-l10n gnupg-utils gpg gpg-agent
gpg-wks-client gpg-wks-server gpgconf gpgsm ibverbs-providers
imagemagick-6-common libalgorithm-c3-perl libarchive-cpio-perl
libasan4 libass9 libassuan0 libauthen-sasl-perl libavcodec57
libavdevice57 libavfilter6 libavformat57 libavresample3 libavutil55
libb-hooks-endofscope-perl libb-hooks-op-check-perl libbind9-160
libbinutils libbluray2 libboost-filesystem1.65.1
libboost-iostreams1.65.1 libboost-system1.65.1 libcairo2
libcdio-cdda2 libcdio-paranoia2 libcdio17 libchromaprint1
libclass-c3-perl libclass-c3-xs-perl libclass-data-inheritable-perl
libclass-method-modifiers-perl libcom-err2
libcrypt-openssl-bignum-perl libcrypt-openssl-rsa-perl
libcryptsetup12 libcurl4 libdata-optlist-perl libdatrie1
libdevel-callchecker-perl libdevel-caller-perl
libdevel-globaldestruction-perl libdevel-lexalias-perl
libdevel-stacktrace-perl libdist-checkconflicts-perl
libdns-export1100 libdns1100 libdynaloader-functions-perl
libegl-mesa0 libegl1 libemail-date-format-perl libeval-closure-perl
libevent-2.1-6 libevent-core-2.1-6 libexception-class-perl
libext2fs2 libfastjson4 libfcgi-bin libgbm1 libgcc-7-dev
libgdbm-compat4 libgdbm5 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-bin
libgdk-pixbuf2.0-common libgl1 libglvnd0 libglx-mesa0 libglx0
libhunspell-1.6-0 libibverbs1 libicu60 libidn2-0
libio-socket-ssl-perl libip4tc0 libip6tc0 libipc-shareable-perl
libiptc0 libisc-export169 libisc169 libisccc160 libisccfg160
libisl19 libjson-c3 libksba8 libldap-common libllvm3.9
liblog-dispatch-perl liblwres160 libmagic-mgc libmail-dkim-perl
libmailtools-perl libmime-lite-perl libmime-types-perl
libmodule-implementation-perl libmodule-runtime-perl libmpfr6
libmpg123-0 libmpx2 libmro-compat-perl libmysofa0
libnamespace-autoclean-perl libnamespace-clean-perl
libnet-smtp-ssl-perl libnl-route-3-200 libnpth0 libnss-systemd
libopendkim11 libopenjp2-7 libopenmpt0 libpackage-stash-perl
libpackage-stash-xs-perl libpadwalker-perl libpango-1.0-0
libpangocairo-1.0-0 libpangoft2-1.0-0 libparams-classify-perl
libparams-util-perl libparams-validationcompiler-perl libperl5.26
libpixman-1-0 libpng16-16 libpostproc54 libprocps6 libpsl5
libpython3.6 libpython3.6-minimal libpython3.6-stdlib libreadline7
libreadonly-perl libref-util-perl libref-util-xs-perl
librole-tiny-perl librsvg2-2 librsvg2-common librubberband2
libruby2.5 libsdl2-2.0-0 libsndio6.1 libspecio-perl libstdc+±7-dev
libsub-exporter-perl libsub-exporter-progressive-perl
libsub-identify-perl libsub-install-perl libsub-name-perl
libsub-quote-perl libswresample2 libswscale4 libtfm1 libthai-data
libthai0 libtommath1 libtry-tiny-perl libunistring2 libva-drm2
libva-x11-2 libva2 libvariable-magic-perl libvorbisfile3 libvpx5
libwayland-client0 libwayland-cursor0 libwayland-egl1-mesa
:
Continue [yN] Details [d]d
No longer supported: gcc-5-base gcc-6-base tcl
Remove: apache2 libnss3-nssdb libperl5.22 perl-modules-5.22 php-curl
php-imagick php7.0-curl virtualmin-lamp-stack
Remove (was auto installed) apache2-bin apache2-suexec-custom
libapache2-mod-fcgid libapache2-mod-php7.2 libcurl3
libmagickcore-6.q16-2 libmagickwand-6.q16-2 php7.2-curl
Hi Joe, just wondering if there is any update in this regard? would love to give 18.04 another go. Thanks! 
(if you use code blocks, your text will be much easier to read!!)
This text: < code > sample < /code > (without the spaces)
Like this: sample
sample
sample
sample
Installed 18.04 on Rackspace Cloud Server yesterday. Failed after reboot on 5 successive attempts.
Tried to update machine first, ie apt update / apt upgrade, then reboot. Reboot was good. Did install. No errors. Could connect via GUI fine.
After install: apt update
All packages are up to date.
N: Usage of apt_auth.conf(5) should be preferred over embedding login information directly in the sources.list(5) entry for ‘http://software.virtualmin.com/vm/6/apt’
N: Usage of apt_auth.conf(5) should be preferred over embedding login information directly in the sources.list(5) entry for ‘http://software.virtualmin.com/vm/6/apt’
Post installation wizard “lost connection to server” for about 10 seconds after “next” click on the “memory use” screen.
Virtualmin now gives me a warning
Warning!
Recent package updates (such as a new kernel version) require a reboot to be fully applied.
Reboot and all connection from outside of Rackspace fails. I can still connect from the Rackspace console.
Getting a new VPS for work next week. I ran VirtualMin on CentOS7 for my personal use, but would love to start the new VPS with Ubuntu 18.04.
Have things been fixed from VirtualMin side? I know it’s a bad idea to run company internal stuff on Ubuntu anyways, but would like to use something different than CentOS
Or go with good old CentOS?
Thanks guys
I just set up another production server last week – used DEBIAN 9…
Smooth as silk.
Thanks jimdunn, but this thread is all about Ubuntu 18.04
I’ve been installing Virtualmin on Centos for over 10 years now. I did two last week. But, I wanted to setup an 18.04 to test TYPO3 9.4
So i am on Digital Ocean (DO) with no backup, no ipv6, no script, yes monitor.
The person on comment #31 made me trying to manually setting netplan. I read /etc/netplan/50-cloud-init.yaml but my list of ip addresses is not quite like the person in the comment have mentioned so I simply try my luck and just run sudo netplan apply and it throw me error about set-name is wrong or something like that. And this is my yaml file.
network:
version: 2
ethernets:
eth0:
addresses: [MULTIPLE_IP_ADDRESSES]
gateway4: IP_ADDRESS
nameservers:
addresses: [MULTIPLE_IP_ADDRESSES]
match:
macaddress: MAC_ADDRESS
set-name: eth0
Referring to the man page here http://manpages.ubuntu.com/manpages/cosmic/man5/netplan.5.html#description about set-name seems that it has the wrong indentation, so I moved the set-name line 1 level up, which is the same level as match. Redo sudo netplan apply and this time it gives no error and be able to access the host again via ssh. Shutdown, reboot etc is also fine, too.
Of course I can only speak for myself and not sure if this is a valid fix and/or can apply to other people. It will be good if something from virtualmin can give this a check.
Hello, I am wondering what the current status is with virtualmin/webmin and Ubuntu 18? Does it work now or should we stick with 16LTS for now?
I didn’t see Ubuntu 18 listed on the virtualmin page but I just went through an install and it rebooted. Everything seems fine.
Thanks
It’s expected to work now that Webmin 1.900 is in the repos, but it’s untested by me, so I haven’t added it back to the supported OS list yet. I welcome success/fail reports from folks who want to try it (file a ticket or start a new thread in the forum about it, don’t keep this old thread alive forever).
Hi there,
I just want to confirm that Virtualmin are now support for Ubuntu 18.04 LTS in install.sh even the supported OS haven’t listed yet.
I’m using Webmin 1.900. No more network problem after rebooting server. I’m able to ssh to server as usual. I use DigitalOcean.
Thank you.
hmm, ok, my server is saying:
Welcome to Ubuntu 16.04.5 LTS (GNU/Linux 4.17.17-x86_64-linode116 x86_64)
New release ‘18.04.1 LTS’ available.
Run ‘do-release-upgrade’ to upgrade to it.
and Virttualmin is saying:
Recent package updates (such as a new kernel version) require a reboot to be fully applied
Are these related and do you think I am reasonably safe updating a production server to 18.04.1 LTS at this time?
Chris
I’ve gotten Ubuntu 18.04.1 LTS to work on my DigitalOcean droplet, but with teething issues:
- Nginx doesn’t run automatically upon reboot; needed to change some config settings to work
- DKIM doesn’t currently work https://www.virtualmin.com/node/59560