TOS 7.0.0392 Beta (X86) is Released for Update

[RyanYang]

Target Users:
Users currently running TOS 7.0.0299 beta or later versions.

Note:
If your TOS version is TOS 6, please refer to the TOS 7 beta update instructions first

Here, we sincerely thank user @Gremlin,@rfbjr,@DCCentR,@PeteBest,@f2245Plus,@OttO1916,@True1Santony and others, for their sharing and feedback. It is your support that has enabled us to quickly identify and resolve some issues.

Update Notes
Bugs fixed:
1. Fixed an issue where uninstalling USB Copy might delete system notification files.
2. Fixed an issue where entering the developer mode page for the first time could trigger an error.
3. Fixed an issue where sorting installed applications by update time was incorrect.
4. Fixed an issue where the cancel function might fail during manual upload of application installation packages.
5. Fixed an issue where repeatedly selecting different DDNS servers might result in no data being displayed.
6. Fixed an issue where desktop shortcuts copied to other locations could not be properly deleted.
7. Fixed an issue where the pop-up styles were inconsistent across some pages.
8. Optimized the style of table statuses in Storage Manager.
9. Fixed other known issues.

Important Information:
1.Updating the system theoretically will not affect the data on your hard drives, but for safety, please make sure to back up your data in advance.
2.Before updating, ensure that your primary volume (usually volume1) has at least 3GB of available space. Insufficient storage space may cause the update to fail.
3.After the update, the IP address of your TNAS may change. Please use the TNAS PC desktop client to search for and reconnect to the device.

Update Procedure:
1.Go to TOS > Control Panel > General Settings > System > Update, and click "Check for updates."
2.Follow the prompts to update the system.
3.After the system update is complete, you may need to refresh your browser.
4.The TNAS IP address may change after the update. If you cannot connect to your TNAS using the previous IP address, use the TNAS PC client to search for the new IP address.

Client Downloads:
1. Download TNAS PC 5.2.506 for Windows OS.
2. Download TNAS PC 5.2.506 for macOS (x86 and ARM architectures).
3. Download TNAS PC 5.2.506 for macOS (ARM architecture).
4. Download TNAS PC for Linux.
5. Download TNAS Mobile 3.X for Android.
6. For iOS, experience TNAS Mobile 3.X via: https://testflight.apple.com/join/wFWYABJS.

[JSCFORCE]

Installed, working well.

[weerasak]

Technical Summary: Connectivity Issues on TOS 7 Beta with Bonded Interfaces and Tailscale
1. Environment Configuration
Hardware: TerraMaster NAS (X86 Platform)

OS: TOS 7 Beta (Build .0392)

Network Setup: * Bonding: Bond 1 (Balance-XOR) with a mix of 2.5GbE and 1GbE links.

Hash Policy: Layer 3+4 (IP + Port).

Docker: Using Macvlan for containers (Pi-hole, Tailscale).

Internal IP: 193.178.22.90

2. Problem Statement
After upgrading to TOS 7 Beta and configuring Link Aggregation (Bond 1), the NAS is accessible via local IP but fails to respond to external/remote requests via Tailscale and DDNS, even though the NAS can be "Pinged."

3. Key Issues Identified
Asymmetric Routing & Packet Reordering: Because the bond consists of mismatched speeds (2.5G + 1G), the Balance-XOR (Layer 3+4) policy causes packets to be sent out across different interfaces. This leads to out-of-order packets and MAC address switching, which causes Tailscale and remote HTTPS connections to drop or "Time Out."

Strict Host Header Validation (Application Layer): TOS 7's web server (Nginx) appears to have stricter security. When accessing the NAS via Tailscale IP (100.x.x.x) on port 5443, the server returns "Connection Refused." This suggests the OS is rejecting requests that do not match the local hostname or local IP whitelist.

Macvlan & Host-to-Guest Conflict: Running Tailscale/Pi-hole inside a Docker Macvlan prevents the containers from communicating directly with the NAS Host IP. This creates a "silo" effect where Tailscale can reach the network but cannot manage the NAS itself.

IP Forwarding Reset: The setting, which is required for Tailscale Subnet Routing, is frequently reset or disabled by the OS after network configuration changes or reboots in the Beta version.net.ipv4.ip_forward=1

[OttO1916]

Both F2-221 and F5-221 upgraded to TOS7.0.0392 without any issues. Thanks!

[rfbjr]

OK so far on F4-425 Plus and F4-223 but hibernation settings are turned back on after the update.
Also, when displaying processes, I really wish the screen would remember the sort order.

[jdcesari]

issue with jellyfin - can not reach it anymore via the app center = the port is wrong / https://192.168.1.1xx:5443/jellyfin/ instead of http://192.168.1.1xx:8096/web/#/home.html

[Gremlin]

Generally trying to establish link modes on asymmetric lan ports will not work well. Either restrict the 2.5Gbe port to 1Gbe or just use the 2 ports separately. {e.g. I use the slower port for things like Network UPS communication or desktop}. This has been documented previously iirc.

F2-424 Updated.

[TMzethar]

issue with jellyfin - can not reach it anymore via the app center = the port is wrong / https://192.168.1.1xx:5443/jellyfin/ instead of http://192.168.1.1xx:8096/web/#/home.html

Did this appear after the update? If possible, please provide a screenshot. We will try to check it.

[jdcesari]

yes
after last update
i can not make screenshot, because it is only a wrong url

[samius]

No, this isn't a system update. This issue appeared in the latest Jellyfin update. In the app incorrectly specifies the port for Nginx. Instead of 8096, it specifies 8098.