Just to elaborate. There are so many moving parts that not all can be tested thoroughly by the actual team, which seems to be 3 or 4 active members? We the community are needed to bring up things that might be broken by an update. Almalinux 10 is a ‘grade a’ supported distro and any problems will probably get prompt attention.
Its not yet, this is normal on new releases.
2 Likes
I’m sorry in my earlier post I did not give a concrete example … this is from one of my RHEL 9 servers:
[root@webhost104 ~]# yum module list php
Updating Subscription Management repositories.
Last metadata expiration check: 1:39:48 ago on Fri 06 Jun 2025 10:30:56 PM EDT.
Red Hat Enterprise Linux 9 for x86_64 - AppStream (RPMs)
Name Stream Profiles Summary
php 8.1 common [d], devel, minimal PHP scripting language
php 8.2 [e] common [d], devel, minimal PHP scripting language
php 8.3 common [d], devel, minimal PHP scripting language
Hint: [d]efault, [e]nabled, [x]disabled, [i]nstalled
as you can see, RedHat themselves offers 8.1 and 8.2 and 8.3 for a v9 server.
Sorry about the coloring of a few words above, not sure how to prevent that 
RHEL AppStreams are, I believe, similar to using a third-party repo. I believe they do not receive the same support assurance throughout the life of the OS release that all the packages in the release receive, so they may reach EOL at the same time the upstream PHP version reaches EOL.
I have just installed an alma10 to test it and I have installed the normal version of virtualmin without any problem, I think I am going to take advantage and move my old server directly to a new Alma10, unless you see any problem and tell me the opposite, what do you think?
I would certainly do the same if I had to install a new OS!
1 Like
Well, actually I’m in the middle of a migration, I have to set up the new Alma10, move what I have moved from Alma9 to Alma10 and then move my old server, now the question is how do I do it ?
If I backup the 10 domains I have in alma9 and restore in alma10, I will have to unregister virtualminpro from the old one and move it to the new one, right ???
You can use your current Virtualmin Pro license on the new server, finish the migration within about 18 days (at most), and then de-register the license on the old server, or, you can just shut down the old server.
I tried but install fails. What version of the script are you using?
to clarify some more, redhat.com says in part
RHEL 10 Full Life Application Streams Release Life Cycle
php 8.3 Release Date: May 2025
which I take it means, as its in the “Full LIfe” chart, that for the supported life of RHEL 10, php 8.3 will also be supported.
for comparision, RHEL 9 has php 8.3 in another chart (NOT Full Life), listing Support/Retirement Date as May 2029 – note RHEL 9 itself (according to google) is supported thru May 2032.
Make a new topic about the problem with what you mean by “it fails”.
small piece of information about virtualmin installation on Alma10
The first test installation I did in this order and I didn’t have any failure.
Alma10 minimal ISO installation
Upgrade/update
webmin installation
virtualmin installation
No failures
Second Alma10 minimal ISO installation
Upgrade/update
Directly virtualmin installation → error last step virtualmin installation (sorry don’t take note of logs)
So I installed webmin and tried again with virtualmin, result installation successful and working
For now the only thing I have noticed fail with Alma10 is that postgrey is failing to install →
Installing the Postgrey package ..
Installing package(s) with command /bin/dnf -y install postgrey ..
Last metadata expiration check: 2:58:53 ago on Wed Jun 11 06:32:31 2025.
No match for argument: postgrey
Error: Unable to find a match: postgrey
.. install failed!
.. installation failed!
and mail rate too
Installing the email rate limiting package ..
Installing package(s) with command /bin/dnf -y install milter-greylist ..
Last metadata expiration check: 2:59:51 ago on Wed Jun 11 06:32:31 2025.
No match for argument: milter-greylist
Error: Unable to find a match: milter-greylist
.. install failed!
.. installation failed!
Do you need a new post for these bugs or should we concentrate the first virtualmin bugs with Alma10 in this post?
I believe VM’s version of WM is different/custom. You may run into problems. If you can’t get the install script to work, don’t go ‘off road’. Work with the team to get the script working. Almalinux is a preferred distro and new versions will get support as quickly as possible.
Stop doing this.
If you’re using Virtualmin, let the Virtualmin installer install Webmin for you from our repos.
Ok, it’s done, how can I correct it?
Just disable the Webmin yum repo that you enabled when you installed Webmin. That’s where the harm comes from, usually.
Oops — you just leaked your license key! 
That’s private info and shouldn’t be shared. I’ll rotate your license number for safety. You’ll find the new one in your Virtualmin account, and you will need to update it manually via “System Settings ⇾ Virtualmin License Manager” page.
fuck fuckr shit, this week I’m putting on a circus and I’m getting on my nerves, at what point did I listen to you about moving to Alma10
sorry, sorry, sorry, for the blunder, I hope the translator does his job well 
I think the translator has not done a very good job. 