[root@virtualmin ~]# wget https://software.virtualmin.com/gpl/scripts/virtualmin-install.sh
--2023-02-11 12:14:09-- https://software.virtualmin.com/gpl/scripts/virtualmin-install.sh
Saving to: ‘virtualmin-install.sh’
virtualmin-install.sh 100%[====================================================================================================>] 42.55K --.-KB/s in 0.001s
2023-02-11 12:14:09 (68.1 MB/s) - ‘virtualmin-install.sh’ saved [43570/43570]
[root@virtualmin ~]# chmod a+x virtualmin-install.sh
[root@virtualmin ~]# ./virtualmin-install.sh
Running Virtualmin 7 pre-installation setup:
Syncing system time ..
.. done
Updating CA certificates ..
.. done
Welcome to the Virtualmin GPL installer, version 7.0.3
This script must be run on a freshly installed supported OS. It does not
perform updates or upgrades (use your system package manager) or license
changes (use the "virtualmin change-license" command).
The systems currently supported by install script are:
Red Hat Enterprise Linux and derivatives
- RHEL 8 and 9 on x86_64
- Alma and Rocky 8 and 9 on x86_64
- CentOS 7 on x86_64
Debian Linux and derivatives
- Debian 10 and 11 on i386 and amd64
- Ubuntu 20.04 LTS and 22.04 LTS on i386 and amd64
If your OS/version/arch is not listed, installation will fail. More
details about the systems supported by the script can be found here:
https://www.virtualmin.com/os-support
The selected package bundle is LAMP and the size of install is
full. It will require up to 650 MB of disk space.
Exit and re-run this script with --help flag to see available options.
Continue? (y/n) y
[INFO] Started installation log in /root/virtualmin-install.log
▣◻◻ Phase 1 of 3: Setup
Installing core plugins for package manager ✔
Downloading Virtualmin 7 release package ✔
Installing Virtualmin 7 release package ✔
▣▣◻ Phase 2 of 3: Installation
Installing EPEL release package ✔
Enabling CRB package repository ✔
Cleaning up software repo metadata ✔
Checking and installing system packages updates [ERROR] Failed with error: 1
✘
[ERROR] Something went wrong. Exiting.
[ERROR] The last few log entries were:
Verifying : epel-release-9-4.el9.noarch 1/4
Verifying : epel-release-9-2.el9.noarch 2/4
Verifying : cloud-init-104218:22.4_96_g4610833_46108-104218.x86_ 3/4
Verifying : cloud-init-101921:22.4_96_g4610833_46108-101921.x86_ 4/4Error: Transaction failed
Upgraded:
epel-release-9-4.el9.noarch
Failed:
cloud-init-101921:22.4_96_g4610833_46108-101921.x86_64
cloud-init-104218:22.4_96_g4610833_46108-104218.x86_64
Checking and installing system packages updates: [2023-02-11 12:16:14 UTC] [ERROR] Failed with error: 1
[2023-02-11 12:16:14 UTC] [ERROR] Something went wrong. Exiting.
[2023-02-11 12:16:14 UTC] [ERROR] The last few log entries were:
[root@virtualmin ~]# rpm -qa | grep epel-release
epel-release-9-4.el9.noarch
[root@virtualmin ~]# yum list | grep epel-release
epel-release.noarch 9-4.el9 @epel
[root@virtualmin ~]# ls /etc/yum.repos.d/
almalinux-appstream.repo almalinux-extras.repo almalinux-plus.repo almalinux-saphana.repo epel-testing.repo
almalinux-baseos.repo almalinux-highavailability.repo almalinux-resilientstorage.repo almalinux-sap.repo virtualmin.repo
almalinux-crb.repo almalinux-nfv.repo almalinux-rt.repo epel.repo vultr-apprepo.repo
[root@virtualmin ~]#
This is a known problem with Vultr. They’ve got a broken repo for cloud-init. We can’t fix it.
The workaround would be to disable that repository until they fix it. Edit /etc/yum.repos.d/vultr-apprepo.repo and change enabled=1 to enabled=0 then do dnf clean all.
Everything should work fine after that. Talk to the Vultr folks, if you want that repo to not be broken. As I said, we have no control over third party repos, and we cannot support them.
I’ve filed a ticket with the Vultr folks, since many of our sites and one of our download servers is hosted with Vultr and I can reproduce the problem.
1 Like
Why are you using the git version of the install script!?
Don’t do that. Always download the stable version from the download page. The development version is not better it does not give you anything new. It is just much more likely to be broken. We can’t support that.
Vultr responded with the following, so hopefully it’ll be fixed soon.
Hello,
We are working on getting a fix for this pushed out now.
Regards,
Eric B.
I’m not sure how I ran across the git link on my first install on a VM on my home machine but that’s what I used. Later I couldn’t even find it. 
I found an article on the internet that links to it (I’ve asked them to change it). But, if you don’t follow random guides you find on the internet, and instead follow our documentation on the Virtualmin download page, you will be fine.
We try so hard to make all of this easy and reliable, but somehow there’s always bad advice our there that gets followed.
We had someone write up a whole guide for installing Virtualmin with nginx and submitted it as a PR to one of the Virtualmin github repos just a couple days ago. The guide was wrong in a number of ways, and they clearly hadn’t read any of our installation documentation, and then yelled at us for not having installation documentation. Very confusing/frustrating. They put so much effort into it, but none into looking at our website, at all.
I don’t know how to make it harder to miss…I put it on the “Download” page because I figured everybody has to download it before installing, so they can’t possibly miss the instructions for installing if the page where you download it also provides the documentation for installing it.
Thanks Joe.
Yes, I installed the virtualmin script on vultr’s VPS.
I tested AlmaLinux9, Rocky Linux9, and CentOS7 on vultr, and found the same problem.
I wouldn’t expect any difference. This is a well understood problem; nothing mysterious about it. They shipped a broken package. I would expect it to fail on any RPM-based distro that has that repo enabled and that package installed.
I posted the workaround above, and they told us they’ll fix the package, there is no need for further experimentation, IMHO.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.