I had some unencrypted datasets in an encrypted dataset, which used to work despite being patched and being “unsupported”. However, since the update, when unlocking the encrypted “parent”, the unencrypted “children” are mounted, and it results in a conflict with the mount path. Was there a change in this behaviour? Why? Is there any way I can keep my unencrypted datasets inside my encrypted dataset?
nginx-proxy-manager, which I used to run as root to bypass the issue of being stuck on “setting permissions” is now, while running as 568, stuck at “setting permissions”.
Thanks!
Truenas apps migrated properly, except dashy:
Error:
It looks like something’s gone wrong…
This is likely caused by the app source not being found at the current domain
If you need additional support, check the browser console then raise a ticket
Fix:
I stopped the app, moved the host-path to a different name, created a new host-path and copied only the conf file to the new host-path and re-deployed the app.
Other:
These 2 happened because of an expired web certificate.
I’m guessing I acknowledged the alert of the expiration, thinking that the system would remind me again? (cert expired Oct 12 and I did not have a notification/alert about it).
If not, is it possible to add further checks during upgrade?
Like check for expired certs and stop the upgrade and notify the user?
-Web UI HTTPS certificate setup failed.
-3 API login failures in the last 24 hours: (username=root,session_id=8e3a7716-95d8-4a31-91cc-900d67d0164a,address=127.0.0.1),(username=root,session_id=beaf59eb-4773-496b-a96f-fdff2cb34a58,address=127.0.0.1),(username=root,session_id=beaf59eb-4773-496b-a96f-fdff2cb34a58,address=127.0.0.1)
2024-10-29 14:07:07 (US/Eastern)
Just upgraded my home bare metal NAS to 24.10 release from 24.04.2
Good news is everything worked straight away, including Jailmaker, without any issues as far as I can tell, and I did have issues, even with RC.2 previously.
I just upgraded from RC2 and it mostly went ok. Several of the apps did not come back up after the upgrade, while others did. Some of the ones that didn’t showed the state as Stopped, and starting them worked fine. 3 were marked as Crashed; one of them just needed to be started as well. (Thanks for the Crashed status, btw, I much prefer that to the previously empty column.) The other 2 did not want to start and eventually the start jobs failed. Looking at /var/log/app_lifecycle.log, they were throwing the following error:
[2024/10/17 19:34:52] (ERROR) app_lifecycle.compose_action():56 - Failed 'up' action for 'sassbot-jasmeralia' app: sassbot-jasmeralia Pulling
sassbot-jasmeralia Error pull access denied for sassbot, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
Error response from daemon: pull access denied for sassbot, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
This was a docker image that I had built locally, so the apps were just pointed to the image sassbot, rather than something like ghcr.io/username/imagename, but it still tried to pull it. After another 5 minutes or so from finding the log message, I tried starting them again and they came up successfully. Not exactly sure why it tried to pull originally but then later was fine without doing a pull.
After sorting all that out, I noticed that the Plex app had an update available and I applied that (from 1.0.23 to 1.0.24). However, Plex itself still shows there’s a newer version available (1.41.1.9057 versus 1.40.2.8395), so it looks like 1.0.24 is still outdated. I would file a PR to bump the version, but the readme indicates that PRs aren’t being accepted right now. Any idea when that version might get updated?
I got the stuck on setting permissions too for nginx, I just-had-to-wait, almost 3 minutes, and then it just finishes. I wonder why it takes so long in that step.
Hi @nkr, you can gather a debug & raise a bug, or start a separate topic with more information that might allow someone to provide some ideas. You should be able to roll back to 24.04 from the boot environments.
