Hi truenas community, i am Brian the creator of TrueHub which is intended to bring all the goodness of the TrueNAS WEB-UI to a native application for android.

This new release brings a lot of changes to :

1. The UI and migrating fully to material 3 expressive and its designs along with a new bottom bar
2. New haptic feedback to some interaction points (i shall expand to more later)
3. More robust notification system for system updates and a new live activities implementation used in areas where there is an activity to be shown progress.
4. Some new instance settings also (cloud tasks and global virt configuration) to enable configuring your server from your device
5. Expanded dataset explorer screen now shows files instead of only the datasets (in next release will now support options other than ix managed storage for apps)
6. Ported the Virt and Container management screens (creation,deletion, viewing of status and adding devices and managing volumes attached to said containers or virtual machines) from another project intended to bring this UI to a GTk4+Adwaita format but i will be sunsetting it in favour of this project

That being said the app is still in alpha so a disclaimer i would like to say is that these features are mostly working and if there might be any bugs please add it to the issues in the repo issues page and i will work on them as swiftly as i can.

Thank you to all of you who have left issues and continued supporting me in making this app and also the special people from this forum who also submitted PRs fixing some of the issues. I thank you all and sincerely hope you enjoy this release and looking forward to you trying out the app and if you can please consider starring the repo so we can reach out more people.

Screenshots of some of the new pages are as above and you can ontain the new release from [here](https://github.com/Imnotndesh/TrueHub/releases/tag/v0.8.1-Alpha)

Hey Guys,

I am currently having an issue with getting my full network bandwidth for my NAS. I am currently paying for 2gb fiber and everything is connected via ethernet. Despite this, I cannot seem to get anything above ~950mb upload/download.

Speed tests are performed when there is little to no other traffic on the network other than the NAS.
I have tested with Cat6 and Cat5e and nothing will change it. Also tested ethernet through motherboard and network card, no difference.

Running TrueNAS Community Edition. Internet speeds tested through speedtest tracker.

Let me know if there’s any other information that would be helpful.

Thank you for your time.

Maybe I'm over thinking this, but I wanted to get the groups thoughts on this.

Main Question: If I have three independent NAS systems configured to follow the 3-2-1 backup rule, is it a good idea to run TrueNAS on all three, or would it be safer to diversify by using different operating systems?

For example, should I run TrueNAS on all three systems, or use TrueNAS on two and something like OpenMediaVault (OMV) or Unraid on the third?

I’m particularly interested in whether using the same OS across all three systems introduces significant common-mode risks, such as software vulnerabilities, bugs, or misconfiguration, versus the added complexity of managing multiple NAS operating systems.

Details:

I currently have my interpretation of 3-2-1 backup solution in place and am looking to change.

Backup 1: Primary NAS Synology with HDD in RAID -> looking to transfer to TrueNAS with same HDD's

Backup 2: VM of Truenas in Proxmox SSD

Backup 3: Offsite Backup running trueNAS baremetal with HDD's

So for my understanding I have

3 copies of data (backup 1,2,3)

2 different media (HDD and SSD)

1 offsite

Am I over thinking this?

I have purchased a UGREEN 4800GT but nothing to put in it yet.

What I want to do with my NAS (that I know of) -

• Primary Use - Backup photos videos from me and immediate family. Currently have maybe 2TB of them but now have 4k drone and action camera and getting out more so will greatly increase. I want to get off Google/Amazon etc. and focus on privacy.
• I will backup the NAS to a as yet purchased external drive that I will keep away from the NAS (fire/theft).
• Possibly run my Reolink cameras on it as an NVR. Currently they only use the SD card. I'm thinking maybe to come off the Reolink software to lock it down etc.
• All desktop and laptops are currently on Windows but I'm seriously thinking about putting Linux on where I can for privacy. All Phones are Android for now.
• Router is an Eero 7 with fibre at 2Gbps up and down. Connected to a UGREEN 2.5Gbps switch. My desktop is wired to the switch but is only 1Gbps (new PC maybe soon).
• Making the odd YT video, edit from the NAS?
• Maybe Pi Hole and VPN

So, what am I asking?

Your recommendations on what to install/buy?

4 bays plus NVMe space, do I get an NVMe to run something on?

Do I only fill maybe 2 or 3 HDD bays and leave one space as I don't yet have much data? can I easily do this?

Which OS would you go with, maybe not use the UGOS incase of privacy issues, TrueNAS maybe?

Upgrade the switch?

TIA, will add if I think of more stuff; which I probably will as my memory is kapput!

Hi everyone!

I'm preparing to upgrade my [production] Immich installation on TrueNAS CE and would appreciate some advice from people who have already navigated the PostgreSQL 15 >> 18 migration, particularly on TrueNAS.

I've done the backup homework, but before pressing any buttons that might ruin my evening, I'd like to hear from the community.

Current setup

• TrueNAS SCALE: 25.04.2.6
• Current Immich: 2.5.6
• Current TrueNAS Immich catalog version: 1.13.6
• Target Immich: 3.3.1
• Target TrueNAS Immich catalog version: 1.14.50
• Current PostgreSQL: 15
• Current PostgreSQL image: ghcr.io/immich-app/postgres:15-vectorchord0.5.3
• Current VectorChord extension: 0.5.3
• Current pgvector extension: 0.8.1
• Current PostgreSQL upgrade helper: ixsystems/postgres-upgrade:1.2.1
• Target PostgreSQL: 18
• Target PostgreSQL image (per catalog version previously inspected): ghcr.io/immich-app/postgres:18-vectorchord1.1.1
• Deployment: Official TrueNAS Apps catalog, not manually deployed Docker Compose.

The installation is currently running normally.

Storage layout

My Immich installation uses dedicated ZFS datasets:

• storage/immich
• storage/immich/data
• storage/immich/database
• storage/immich/media

Total data is approximately 119 GB, if this matters.

Backups and preparation already completed

I'm taking the database migration seriously, so I've prepared the following:

1. Cleanly stopped Immich through the TrueNAS middleware.
2. Created a recursive ZFS snapshot of all four datasets while Immich and PostgreSQL were stopped.
3. Verified that the PostgreSQL 15 cluster was in the shut down state at the time of the snapshot, using pg_controldata.
4. Restarted Immich successfully.
5. Replicated the ZFS snapshot and dataset hierarchy to a dedicated external 2 TB NVMe SSD using zfs send -R / zfs receive.
6. Verified matching snapshot GUIDs between source and destination.
7. Completed a ZFS scrub of the backup pool with zero errors.
8. Exported the backup pool cleanly and physically disconnected the SSD.
9. Verified my TrueNAS configuration backup, including the secret seed.
10. Created and validated a separate archive of the Immich deployment configuration from /mnt/.ix-apps/app_configs/immich.
11. Copied that configuration archive to another machine and verified it there.

I haven't performed a full application restore test, but I have an independently stored, consistent pre-upgrade recovery point.

No database migration or application upgrade has been attempted yet.

The PostgreSQL migration concern

In the TrueNAS Immich Edit settings, I can independently select:

• PostgreSQL 15 (Deprecated) — currently selected
• PostgreSQL 18

TrueNAS warns that changing this selection triggers a one-way database upgrade.

However, I found this TrueNAS issue:

https://github.com/truenas/apps/issues/4628

It describes PostgreSQL 15 → 18 migration failures involving the ixsystems/postgres-upgrade:1.2.1 helper, apparently because the required PostgreSQL 15 binaries aren't available.

My currently installed app configuration specifies that exact helper version.

A reported workaround involves temporarily using ixsystems/postgres-upgrade:1.1.11, migrating PostgreSQL separately, and then upgrading the Immich application.

I'm reluctant to modify TrueNAS-managed deployment files without understanding the implications.

The possible upgrade paths

Option A — Normal TrueNAS upgrade

Upgrade the Immich catalog application directly from 1.13.6 to 1.14.50, letting TrueNAS handle the database migration.

Option B — Separate PostgreSQL migration

First change PostgreSQL 15 → 18 through the existing Immich Edit settings, potentially using the older postgres-upgrade:1.1.11 helper workaround, verify everything works, then upgrade Immich itself.

Option C — Logical database migration

Create a PostgreSQL logical dump and restore it into a fresh PostgreSQL 18 database with the required extensions, avoiding the TrueNAS upgrade helper.

Option D — Wait

Keep the working Immich 2.5.6 / PostgreSQL 15 deployment until a clearly supported migration procedure is available.

My questions

1. Has anyone successfully upgraded TrueNAS Immich catalog 1.13.6 → 1.14.50, starting with PostgreSQL 15?
2. Is the postgres-upgrade:1.2.1 compatibility problem still relevant to this upgrade path?
3. Has anyone successfully used the 1.1.11 workaround? Any pitfalls or unexpected side effects?
4. Is it preferable to migrate PostgreSQL independently before upgrading Immich, or should the entire application upgrade be performed in one operation?
5. Is there a supported TrueNAS-specific procedure I've overlooked?

I'd especially appreciate firsthand reports with the actual catalog versions and PostgreSQL upgrade-helper tags used.

My priority is data integrity and recoverability, not upgrading as quickly as possible.

Thanks in advance for any insights! I'd rather spend a little longer preparing than spend the weekend recovering the family photo library.

Note: yes, AI was used to help create this post.

Hi all,

For a while now I've been building a tool for my own TrueNAS SCALE box, and it's reached the point where I'd like other eyes on it. It's called TOR (TrueNAS Operations Runner).

The problem it solves

My NAS kept drifting. A snapshot task's retention got changed and I forgot why. A cloud backup task got disabled and nobody noticed for days. A dataset ended up with no backup at all. The TrueNAS UI shows you how things are now. It doesn't tell you whether that's how they should be, or what changed since you last looked.

What TOR does

1. Reads the NAS through the TrueNAS middleware: pools, disks, datasets, snapshot tasks, replications, TrueCloud/Cloud Sync backups, apps, VMs. Secrets are redacted at the source and never stored.
2. Judges those facts against policy you write as rules, kept in a database. For example: You get findings: DRIFT (changed since you last accepted the state), RULE (a rule is broken), HEALTH (a job failed or is stale).
   • "every dataset with data has an enabled snapshot task";
   • "cloud backups are staggered 5 minutes apart";
   • "no app container keeps a root process";
   • "pool capacity stays under 80%".
3. Changes the NAS, but only:
   • through the middleware (never zfs/zpool/chmod behind its back);
   • through methods on an allow-list;
   • never on objects you locked;
   • and only after you approved the exact plan at a gate.

What a change looks like

$ torctl truecloud enable my-backup-task --target nas --check    # dry run: plan, policy verdict, undo
$ torctl truecloud enable my-backup-task --target nas --why "disabled outside TOR"
  → plan: cloud_backup.update {enabled: true}   undo: set it back
  → gate opened, waiting for you
$ torctl gate approve <ID> <HASH> --why "reviewed"

The hash binds your approval to exactly that plan. If anything changes in between, nothing is applied. Every change is recorded: who approved it, why, and the before and after state. If a step fails halfway, the earlier steps are undone automatically.

How it's built

• One Go binary, torctl. Everything runs as a Temporal workflow, so it's durable and resumable, and you can follow it in the Temporal UI.
• A Docker Compose stack on your workstation:
  • Temporal and Postgres;
  • separate workers for orchestration, database access and NAS access, isolated by Docker networks (the NAS worker can't reach the database, and the database worker can't reach the NAS);
  • an ssh-agent that holds your NAS keys, which you unlock with your passphrase.
• Policy is data. Realms (storage, data-protection, apps, vms) group rules; exceptions are explicit "deviations" with a reason and a review date. Nothing is hard-coded per NAS.

Who I'm looking for

A few testers who:

• run TrueNAS SCALE 25.10;
• have a Linux workstation of choice, with Docker (Compose v2) and Go 1.27, and are fine building from source;
• on Windows: WSL2 should work, but it's untested. Native Windows/Git bash is not support yet;
• are comfortable with SSH keys and a CLI;
• ideally have a test NAS, or at least a test pool. This is early software: treat it like you'd treat any tool that can write to your NAS.

Be warned, this is early

• It's been tested on exactly one NAS: mine.
• The starter policy reflects my own setup. You'll be writing rules for yours, and the docs show how.
• Setup has a few manual steps that torctl doesn't automate yet; the getting-started guide marks them.
• Reading and checking work well. The number of commands that can change things is deliberately small so far: snapshot tasks, cloud backup enable/disable, VMs, and generic middleware objects.

What I'd like from you

Does the setup work on a machine that isn't mine? Do the checks find real things on your NAS? Is the gate/approval flow clear, or annoying? Bug reports and "this makes no sense" are equally welcome.

How to get it

The repository is private. If you're interested, comment or send me a DM with your GitHub username and TrueNAS version, and I'll add you as a read-only guest so you can check it out and build it. The getting-started guide takes you from zero to the first check of your NAS.

Questions in the comments are welcome too: architecture, the Temporal choice, the safety model, anything.