There is a feature request open on this forum for this I believe, I suggest reviewing and voting for it.
2 Likes
Ah, getting the UPS stats from a remote system.
Yes, it should work as expected (and as it does in CORE, as you said), so this one is most likely an implementation bug.
Will do, thanks for the help
Thank You for the smooth migration 
1 Like
You might want to start a new thread with details of the previous configuration you had and software version.
There is a plan for dedicated IPs for Apps, but without a description, Iām not sure automigration will work.
So I updated and ā¦ everything still works?! Did I do something wrong? 
8 Likes
Congratulations and many thanks to everyone involved in making Electric Eel possible. In my opinion, the decision to switch from Kubernetes to Docker was absolutely the right one.
Upgrading both of my TrueNAS 24.10 RC2 hosts went buttery smooth and without hiccup \o/
Because as always after the release is before the release:
Fangtooth creates the next reason for anticipation with the integration of Incus. Personally, I refrain from using VMs and prefer resource-saving alternatives. Incus will be the icing on the cake and make the personal need for Proxmox superfluous.
3 Likes
I think it might be prudent to highlight in the announcement above that the apps architecture is changing from kubernetes to docker in this main release ā¦ just in case people havenāt been following the beta and RC stages.
Hi All,
Just updated, all went smooth, Great Stuff 
only app that kept on deploying was Tailscale, this seems to need a new key.
generated a new key and it went running right away.
Big Thanks to all involved.
1 Like
upgrade went to but transmission app failed to migrate.
Have you checked in the netdata backend if it shows 2 connected ups? One called something like ix-dummy and then your ups? If yes did you change the ups identifier in the service from āupsā to anything else?
I broke the ups reporting by changing the identifier, reverting the identifier back to ups solved the reportinig issue.
Thanks. Using the same identifier as I did on CORE, which worked. Tried reverting which did not fix reporting. I can confirm that TrueNAS SCALE is monitoring my network UPS Master, since I get notifications when power flickers. Itās just a minor nuisance that reporting does not work. Hopefully, one day it will get priority and get worked.
Regarding the update.
I see this posted on several places.
" Encrypted Root Dataset:
Applications do not migrate to 24.10 if the ix-applications dataset is configured on a pool with an encrypted root dataset (see NAS-131561). Relocate installed applications to an unencrypted pool on 24.04 before attempting to upgrade to 24.10."
I did a fresh install on 24.04 and now have 24.04.2.3 and i dpnt want to get in to more trouble than i have to during the update 
I have some apps. Plex, Tautulii, wg-easy. They are installed in the ix-system folder that is not encrypted. but the root of the pool is. (this setup was done by Truenas it self when setting it up with an encrypted pool)
Does this mean that i will have a problem upgrading? (I know i need to force the ACL first for the folders) But I mean with the migration due to encryption?
This is a fairly new built system. Do i need to rebuild and move the apps to a new pool? or is there a way around this that is less troublesome?
The migration of the apps will not work if the pool the apps are hosted on is encrypted. So you need to move them to a different pool.
1 Like
Are we saying that a scenario like what I currently have for a custom app below isnāt possible with EE at all? Or that itās just that auto-migration wonāt work, and Iāll have to configure it manually in YAML?
Ok, so i need to add more disks and create a new pool for the apps, is there anything to think of when doing that on 24.04?
and also, is it possible to use the boot disk for this? i have plenty of space on the SSD that the OS uses.
My ix-applications dataset is also within an encrypted dataset. I believe this is how the system set it up when I first installed it. Or at least I donāt remember forcing it to be that way. Regardless, I only have two top level datasets on my system and they are both encrypted.
What am I supposed to do in this case? Can I force move it to the boot-pool? Could I attach a USB hard drive and create a new temporary pool? If so, could I move it back afterwards? Or does it have to stay within an unencrypted dataset after the upgrade?
2 Likes
Hello,
Iām not sure where this checkbox is.
This is my Storj TrueNAS app on Scale Dragonfish-24.04.2
Is the āEnable ACLā checkbox?
Best Regards,
Antonio
Hmm. The bug states that it should only happen if you have āEnable ACLā checked, but not the āForceā box that appears underneath it. 
This might be worth submitting a problem ticket with a debug file attached so that we can poke into the app_migrations.log file
Iām not migrating yet this Scale box: Storj check uptime, so I donāt want to stay offline for a long time.
Someone already migrate a server with Storj app running? It works?
Best Regards,
Antonio