The TrueNAS team is pleased to release TrueNAS 24.10.2.2!
This maintenance release is intended to assist the community with the TrueNAS Apps transition to per-app IP address binding.
It contains a single change to backport app update logic from TrueNAS 25.04, allowing users who prefer to remain on 24.10 past the June 1 app migration cut-off to do so (NAS-135515).
See TrueNAS Apps in the 24.10 Upgrade Notes for information on this.
Key point from the Release Notes (which each and every user always read thoroughly before hitting the “Update” button, right? Right???):
Upgrade to 24.10.2.2 or 25.04 before June 1 to continue receiving regular app updates. Existing applications installed on 24.10.2.1 or earlier do not automatically update after June 1, 2025. Users who do not upgrade to 24.10.2.2 or newer before June 1 must manually uninstall and redeploy affected applications after updating TrueNAS to resume regular application updates.
A) If I stay on 24.10.1 after June 1st I will not receive any app updates and even if I then update to 24.10.2 I will have to reinstall all affected apps for them to start working correctly.
This is stated in release notes.
Existing applications installed on 24.10.2.1 or earlier do not automatically update after June 1, 2025. Users who do not upgrade to 24.10.2.2 or newer before June 1 must manually uninstall and redeploy affected applications after updating TrueNAS to resume regular application updates.
B) If I stay on 24.10.1 after June 1st I will not receive any app updates but I can just update to 24.10.2 anytime after which will migrate the apps and they will start receiving updates.
B Is correct. That sentence was not updated correctly from the previous version. You simply need to update to 24.10.2.2 or 25.04 and the option to update apps will become available again.
Edit: It is correct behind the Read More
Update to TrueNAS 24.10.2.2 before June 1, 2025 to continue receiving app updates without interruption, including the new IP port binding functionality.
Previously installed apps on TrueNAS 24.10.2.1 (or earlier) do not receive updates after this point. Normal application update functionality resumes after TrueNAS updates to 24.10.2.2 or 25.04.
Point taken: I had not read thoroughly enough before quoting what looked like the relevant passage in the linked document from the Release Notes.
On the other hand, the clearer explanation being hidden under “Read More” reminds me of something…
“But the plans were on display…”
“On display? I eventually had to go down to the cellar to find them.”
“That’s the display department.”
“With a flashlight.”
“Ah, well, the lights had probably gone.”
“So had the stairs.”
“But look, you found the notice, didn’t you?”
“Yes,” said Arthur, “yes I did. It was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying ‘Beware of the Leopard.”
All the planning charts and demolition orders have been on display in your local planning department in Alpha Centauri for fifty of your Earth years, so you’ve had plenty of time to lodge any formal complaint and it’s far too late to start making a fuss about it now.’
it’s not yet available for all apps, it will becom available in june. I believe there’s a list on the apps github page that shows which apps have the feature already enabled.
Just a heads up on an issue. Everything seems to be fine now.
Perhaps I missed loss of network connectivity in the release notes requiring a second reboot for the fix. I experienced a complete loss of network connectivity upon updating from 24.10.2.1 to 24.10.2.2. This was fixed for me by issuing a reboot from IPMI which was the only interface available.
The system I updated is set up with a LAG on 2x1gbs ports. The update seemed to go fine, The system never became available from any ip address on the network other than the IPMI address after the update. A second manual reboot from the IPMI interface took care of the issue.
It might be that a second reboot is what is necessary to update the network or it is possible that one of the apps that was not running at the time prevented completion. Or maybe this is an edge case of using a LAG interface setup.
It may not be related, but this update killed Tailscale in one of my servers. Tried removing, reinstalling, unsetting the pool and setting it again, generating a new setup key… and nothing.
As far as I can tell, there’s nothing different with the affected machine (I have several others that upgraded uneventfully).
Will keep investigating, and post back any additional info.
P.S.: sorry for the false alarm, turned out to be a DNS issue.
I just upgraded both my NAS’es.
And i even remembered to update ZFS version on old 24.10.2.1, before upgrading to latest 24.10.2.2
I had a pending zfs upgrade, on 24.10.2.1. And was advised to wait a bit, because it would prevent fallback.
