Has anyone tried the new almalinux10 version on virtualmin?
Is it supported or is it going to be supported in the short term?
I ask more than anything to know if I’m playing it safe by continuing to configure virtualmin on an Alma9 or risk migrating to v10 now that I’m on time…
Hello,
Thanks for the heads up!
Nothing’s stopping you from installing on Alma 10, though it does need a bit more thorough testing first. I wouldn’t recommend upgrading from Alma 9 just yet, but if you’re doing a clean install, Alma 10 is a better choice to start with.
The software bump in Alma 10 to MariaDB, BIND, Postfix and Apache should be fine—they’ve already been supported and working for years on other distros like Ubuntu 24 and Debian 12.
Thank you Illia
Alma9 has support until 2027/2032 so for now I think that’s plenty of time…
I see that by default it stays on PHP 8.0.30, I find it curious, I guess I’ll have to add some repository to have PHP more updated.
By the way, a curious thing and that I need to support my customers, in the old server when I went to a user in the Password field there was a round with a drawing of a person and putting the mouse over it I got the user password, in the new server I do not get it, and I’ve been looking everywhere in the Virtualmin configuration and I can not find it anywhere ???
PS: Sorry for the offtopic
That is surprising, you do know how to install different version on Virtualmin, don’t use other docs to do it.
1 Like
Yes, that’s right, and it’s quite simple to do:
We’d be happy to help, but you’ll need to create a new topic for that!
1 Like
In RHEL 10, PHP 8.3 is the default version of PHP:
2 Likes
Yes, of course (thank you i don’t view this doc before), that’s why in my old server I have installed a PHP version higher than the one in my new Almalinux 9, hence my surprise that the new version only has 8.0.30 by default, I just ask if you can recommend me a repository, in the old one I use remi if I remember correctly.
PD: i view your doc
A stable release isn’t going to push out a later version as it could break something. That’s the point. PHP seems to push out new features in point releases. so X.1.yy stays stable. X.2.yy could break something. In the Debian world people rely on backports for new features. Hence ‘remi’. Same concept.
1 Like
Thanks, So I understand that the recommended thing to do would be to add the REMI repository to keep it updated, is that correct?
Yes, it is correct. You have to use the remi repo and install de new php version following the tips in Configuring Multiple PHP Versions | Virtualmin — Open Source Web Hosting Control Panel
1 Like
remi has a wizard for which commands to run to replace the stock version.
personally I prefer one more updated version that multiple versions.
Only if you must have versions of PHP other than the one that comes with your OS. I recommend you stick with OS-provided packages when possible, because they will have a longer lifecycle and will have more active maintenance (security patches will be applied faster, most likely).
If you are using third-party PHP packages, it’s your responsibility to keep an eye on when a given PHP version reaches EOL upstream, and make sure you get anything depending on those versions upgraded. The version provided by your OS will be supported through the life of your OS, the third-party versions will be supported as long as the PHP developers and the packager support it (which generally means EOL upstream is EOL for the package).
1 Like
I would discourage that, I think. I haven’t used/seen it, but I think you want to stick with explicitly installing only the packages you need.
That’s a reasonable goal, but the better way to do it is to get a newer OS.
Thats fair. It has been working great for me in virtualmin. The updates come from their repo nicely.
With a single version you have it easier IMO you can just use php- instead of having to worry about appending version names for extensions etc…
I totally agree to use the base OS version from a current OS but things like nextcloud move fast with php.
Now 8.3 is recommended, I am sure going into next year 8.4 wil be the recommended version.
Other things seem less sensitive. Where anything over 7.4 will do.
1 Like
Yeah, there are benefits to it, and having only one version means you only need to keep up with when that one version reaches EOL and any security issues in that one version.
I don’t think replacing the system one is bad if you know what you’re doing. I’ve just seen a lot of folks mess up that plan.
I don’t have a RHEL 10 box around, but try this to see what is available in your base O/S
yum module list php
as its possible, while I use REMI myself on some servers, that you can stick with just things from Alma
What an interesting post with this discussion, that’s how you learn interesting things 
I’ll summarize what I have understood, which can be a good practice on the topic of PHP versions, let’s see if I have understood it well…
It is advisable to leave by default the PHP version that comes with the operating system installed, because even if it is an ‘old’ version, as in this case of AlmaLinux 9 the PHP 8.0.30, while Alma9 is supported with its extended security support until 2032, that version 8.0.30 will have the latest security fixes so it will be safe.
In case it is needed or for performance, I can install the latest REMI versions like 8.3 for Nextcloud or Wordpress themes which effectively improves the speed a lot.
Is this correct?
Would this be a good security / performance practice?
1 Like
It’s reasonable for security. I highly doubt you’ll see it “improve the speed a lot”.
I wouldn’t generally recommend upgrading for theoretical performance improvements, as it’s probably not going to be noticeable and it adds complexity.
Also, if you’re using multiple versions, it will consume more memory, and most people on small/cheap VMs are more memory-constrained than CPU constrained. So, you’ll probably hurt performance by adding more PHP versions to the mix. Running multiple copies of the same binary is generally more memory-efficient than running different versions. (This is one good argument for getting rid of the system stock PHP, if you require a newer one.)
I recommend you only do things for performance reasons if you really understand all of the performance restrictions on your system and make informed decisions about what will help.
But, almost always, I think we should mostly just trust our OS vendor and use the packages they provide. It saves time, it is likely more secure long-term, and there’s less room for user error. If you want newer versions of various services, the best way to get them is to upgrade to a newer version of your OS.
1 Like
The problem its that i have installed the last Almalinux version supported by virtualmin and it have a PHP 8.0.30, if i see the web of php i view that this 8.0.30 its unsupported, and 8.3 and 8.4 its supported by PHP, looking at this…
I change the default version 8.0.30 to 8.4/8.3 as recommended by PHP?
You misunderstand the situation. Packages provided by your OS are supported by your OS vendor. And, your OS vendor provides (much) longer support than upstream PHP.
I think we expect Virtualmin installer to work OK on Alma 10 (though we haven’t announced support for it yet, it’s coming soon), so if you need a newer version I’ll repeat my advice: get a newer OS.
If you run into problems they’ll get sorted out in the coming week, probably.