TrueCommand Version 3 Release Notes

TrueCommand 3.1.0 builds on the foundation of previous releases, delivering the latest feature enhancements, improved system stability, and expanded software compatibility. This major update introduces new monitoring tools, configuration options, and quality-of-life improvements to make managing your TrueNAS systems even simpler. Here are the major changes in this release:

TrueCommand is primarily offered as a Software as a Service (SaaS) solution from iXsystems, but can be self-hosted as a container deployment.

TrueCommand Cloud registrations are available from https://portal.ixsystems.com. A valid email address and credit card is required (sign up instructions).

A self-hosted TrueCommand container is available from https://hub.docker.com/r/ixsystems/truecommand/tags under the tag release-3.1.0 (deployment instructions).

TrueCommand Cloud deployments are upgraded automatically by TrueNAS. Self-hosted instances must be updated manually by a local TrueCommand administrator.

As a best practice, back up your instance data directory before deploying updates. Self-hosted containers are typically updated by backing up the container volume and pulling the latest available container version. See the container update tutorial for guidance.

Migrating off of TrueCommand v2.3.3 or later does not require additional migration processes; however, migrating from any versions earlier than v2.3.3 requires a database migration process.

After upgrading to TrueCommand 3.1.0, you might need to edit and re-apply connected TrueNAS system passwords to ensure connectivity.

Starting in version 3.1.0, TrueCommand supports STARTTLS again to support availability for Microsoft365 users.

Users can now enable or disable snapshot tasks directly, providing better control over scheduled backups.

Enhancements to CPU reporting and Disk IOPs reports provide more accurate system performance data.

A new NAS code dialog improves two-factor authentication workflows and temporary password resets for Cloud users are fixed.

Note that if you are using TrueCommand with a TrueNAS SCALE HA system, you need to update SCALE to version 23.10 or later before connecting to TrueCommand 3.1.0.

API key logins now fail and revoke the key, triggering a NAS alert. Users who are using a self-signed certificate might experience broken connections. It is advised to update your authentication settings prior to updating to TrueCommand 3.1.0 to avoid this disruption.

After updating, clear the browser cache (CTRL+F5) before logging in to TrueCommand. This ensures stale data does not interfere with the TrueCommand UI.

TrueCommand 3.1.0 is tested and compatible with these TrueNAS versions:

• 13.0
• 22.12
• 23.10
• 24.04
• 24.10
• 25.04

Self-hosted Containers:

flowchart LR
A["Legacy (Pre 1.2)"] --> B
B["1.3"] --> C
C["2.2.2"] --> D
D["2.3.3"] --> E
E["3.0.2"] --> F
F["3.1.0"]

Container | Cloud

Previous

Stable

Next

TrueCommand 2.3

Latest:

2.3.3 Maintenance 20 June 2023

TrueCommand 3.1

Latest:

3.1.0 Stable 25 March 2025

TrueCommand Next

Anticipated:

Next Major Version TBD

March 25, 2025

The TrueNAS team is pleased to release TrueCommand 3.1.0!

Notable changes:

• Dashboard averages percentages not space (TC-3160)
• System group filtering broken on dashboard (TC-3247)
• Retry connection after failover to ensure VIP has synced (TC-3249)
• Create Disk IOPs Report (TC-3255)
• API and admin login alerts are duplicated (TC-3250)
• Fangtooth Compatibility (TC-3263)
• Add STARTTLS config option (TC-3242)
• Fix encryption usage for replication tasks (TC-3281)
• Do not force update check to be successful for server initialization (TC-3270)
• Close 2FA loophole (TC-3278)
• Enable snapshot task toggling (TC-3279)
• Add images of recent models (TC-3254)
• Update container base from node 20->22, go 1.22-1.23 (TC-3280)

Click here for the full changelog of completed tickets that are included in the TrueCommand 3.1.0 release.

TrueNAS Enterprise

We recommend that TrueNAS Enterprise High Availability (HA) systems be updated from the TrueNAS UI.

If TrueCommand 3.1.0 is used to upgrade HA systems, the standby controller might fail to activate the updated boot environment, resulting in a version mismatch error between the controllers. If you encounter this issue, manually activate the updated boot environment on the active controller and then failover to complete the upgrade.

• The Explore > Snapshots tab can timeout when selected for datasets with high numbers of stored snapshots (TC-3078).

Click here to see the latest Jira tickets about known issues in 3.1.0 that are being resolved in a future TrueCommand release.

TrueCommand 3.0 brings the latest feature development, stability fixes, and software compatibility updates together in a major version that is more functional and performant than ever before. Here are the major changes in this release:

TrueCommand is primarily offered as a Software as a Service (SaaS) solution from iXsystems, but can be self-hosted as a container deployment.

TrueCommand Cloud registrations are available from https://portal.ixsystems.com. A valid email address and credit card is required (sign up instructions).

A self-hosted TrueCommand container is available from https://hub.docker.com/r/ixsystems/truecommand/tags under the tag release-3.0.2 (deployment instructions).

TrueCommand Cloud deployments are upgraded by iXsystems on an ongoing basis. Please use caution when upgrading production TrueCommand systems.

Self-hosted containers must be updated by a local TrueCommand administrator. As a best practice, TrueCommand administrators need to back up their instance data directory before deploying TrueCommand updates. Self-hosted containers are typically updated by backing up the container volume and pulling the latest available container version. See the container update tutorial for guidance.

Updating from TrueCommand v1.3 to v2.0 or later involves a database migration process. This preserves all configuration data, but does not preserve old performance statistics. Additionally, it is not possible to roll back to TrueCommand v1.3 from v2.1 or later.

An issue is found with High Availability (HA) TrueNAS SCALE 23.10.0.1 systems connected to TrueCommand 3.0. Update SCALE HA systems to TrueNAS SCALE version 23.10.1 or later before connecting to TrueCommand 3.0.

After upgrading to TrueCommand 3.0, you might need to edit and re-apply connected TrueNAS system passwords to ensure connectivity.

Starting in version 3.0.2, TrueCommand does not support STARTTLS or port 587 for SMTP email configuration. Users with SMTP configured on port 587 should use port 465 and select Enable TLS for full SSL/TLS encryption. See Configuring SMTP Email for more information.

In version 3.0.2 administrative users no longer appear on the list of users available to be assigned to a team. Administrative users have full admin permissions for all connected systems, so manual team assignment is not needed.

After updating, clear the browser cache (CTRL+F5) before logging in to TrueCommand. This ensures stale data does not interfere the TrueCommand UI.

TrueCommand 3.0 is tested and compatible with these TrueNAS versions:

• 13.0
• 22.12
• 23.10
• 24.04
• 24.10
• 25.04

Self-hosted Containers:

flowchart LR
A["Legacy (Pre 1.2)"] --> B
B["1.3"] --> C
C["2.3.3"] --> D
D["3.0.2"]

August 13, 2024

iXsystems is pleased to release TrueCommand 3.0.2!

This is a maintenance release to address issues found in the 3.0.1 version.

Notable changes:

• Fix Cloud SMTP email configuration for authentication (TC-3186).
• Investigate detached NAS connections (TC-3188).
• Disable TrueNAS UI proxy (TC-3190).
• Do not try to decrypt text between 1 and 15 bytes (TC-3198).
• UI refreshes token too often (TC-3200).
• Job “config.save” does not finish and constantly yields error 32 (TC-3202).
• User alert creator status reset on migration (TC-3177).
• Stale sessions appear as active users (TC-3180).
• Enable HSTS on web server (TC-3196).
• Disable SWEET32 cipher suite support (TC-3195).
• Increase temp password timeout for Cloud to 48 hours (TC-3187).
• Do not check for upgrade_pending status if connected via the passive controller (TC-3182).
• Paused internal alerts do not persist past reboot (TC-3181).
• The deprecated Clusters screen has been disabled in the TrueCommand UI (TC-3223)

Click here for the full changelog of completed tickets that are included in the TrueCommand 3.0.2 release.

TrueNAS Enterprise

We recommend that TrueNAS Enterprise High Availability (HA) systems be updated from the TrueNAS UI.

If TrueCommand 3.0.2 is used to upgrade HA systems, the standby controller might fail to activate the updated boot environment, resulting in a version mismatch error between the controllers. If you encounter this issue, manually activate the updated boot environment on the active controller and then failover to complete the upgrade.

• The Explore > Snapshots tab can timeout when selected for datasets with high numbers of stored snapshots (TC-3078).

• Changes made to SMTP email configuration after initial setup might not apply for new users created after created after the configuration updates. If you have previously updated your SMTP configuration, create new user accounts as described in Creating User Accounts. Log in as the new user and review settings in Alert Services > SMTP Email to confirm they are correct.

• Removing all the systems from a group does not automatically delete the group. However, the system group is still manually removable.

Click here to see the latest Jira tickets about known issues in 3.0.2 that are being resolved in a future TrueCommand release.