TOS 7.0.1341 (x86) Official Release Update

[CursaYang]

TNAS PC 5.2.560 had not been released yet when TOS 7.0.1341 was released, so the TNAS PC version in the update notification was not updated.

For information about the new TNAS PC 5.2.560, you can refer to this post:

viewtopic.php?t=10687

The TNAS PC client will automatically detect the new version and prompt you to update — just follow the on-screen instructions.

[Gremlin]

Noted. Under normal circumstances I would never have read that post. I don't do Macs.

[bull5]

Hi, after update no way to connect the webgui (remote and local). Si a power on power off fix this issue.
Webdav access via DDNS: not working! Router port open 474, webdav activated. No way. F2 425

[EriChan]

Regarding the issue where the WebGUI was inaccessible after the update, if this problem occurs again, please generate and send a system report (via TOS Desktop > Support & Help > Issue Report) to our technical support team at support(at)terra-master.com.

Regarding WebDAV access via DDNS not working, please check the following:

1. Test local WebDAV access first:

• Try connecting via WebDAV locally using the NAS internal IP (e.g., http(s)://<NAS_IP>:<internal_port>).

• If local access works, the WebDAV service itself is functioning normally, and the issue lies in port forwarding, protocol mismatch, or DDNS resolution.

2. Check port mapping and protocol in TOS:

• Go to Control Panel > File Services > WebDAV and verify the assigned port for HTTP or HTTPS.

• Ensure external port 474 on your router is correctly forwarded to that exact internal WebDAV port on the NAS IP.

• Make sure the connection URL used in your WebDAV client specifies the correct protocol (http:// vs https://) matching port 474.

3. Check DDNS and Public IP:

Verify that your DDNS domain resolves to your router's current public WAN IP, and ensure your ISP provides a public IP rather than a CGNAT address.

Please let us know the results of the local test so we can assist you further!

[bull5]

Hi,
regarding webDAV, locally is working. DDNS should be fine cause I have remote access. Duckdns.org pubblic IP is ok.
I created a TCP port forwarding rule with IP address of the NAS (static) port 474 for HTTPS protocol.

Still not accessible.

[EriChan]

Since local access and DDNS resolution are working, please check the following to resolve the remote connection:

1. Test Outside Local Network (NAT Loopback):

• If you are testing:
  https://yourdomain.duckdns.org:474
  while connected to the same local Wi-Fi, the connection will fail if your router does not support NAT Loopback (Hairpinning).

• Please disconnect Wi-Fi and test using mobile cellular data (4G/5G) or from an external network.

2. Check Port Reachability Externally:

• Ensure your router's port forwarding rule maps External Port 474 to the NAS IP with Internal Port 474 (TCP).

• Use an online port checker (such as canyouseeme.org) to test port 474 against your public IP / DDNS to confirm it shows as Open.

3. SSL Certificate & Client Restrictions:

• Because port 474 uses HTTPS, certain clients (such as Windows native "Map Network Drive") will silently block the connection if the SSL certificate is self-signed or does not match your DuckDNS domain.

• Try connecting via a dedicated client (such as Cyberduck or RaiDrive) with the option to trust/allow self-signed certificates enabled.

Please let us know the results of testing over cellular data or the online port check!

[bull5]

Hi
Test Outside Local Network (NAT Loopback)
Result: Fine, accessible from internal network
Fail with hotspot 5g network missing certificates (client autentification, anyconnectOID)
Check Port Reachability Externally
Fine: checked with android and 5g network checked with DNS checker, result: port open
SSL Certificate & Client Restriction
With RaiDrive Mount: not working (5g mobile network), no connection

Cheers

David

[bull5]

With solidexplorer android and 5g network is working fine!
Something wrong with certificates?

[EriChan]

Thanks for your ongoing feedback.

Here is why it works on your phone but fails on the PC:

• Mobile vs. Desktop validation: Solid Explorer automatically permits or prompts you to trust unverified/mismatched SSL certificates. In contrast, RaiDrive and Windows enforce strict SSL/TLS validation. Because TOS uses its built-in default certificate, the domain on the certificate does not match yourdomain.duckdns.org, causing RaiDrive/Windows to reject the handshake.

• Corporate software interference: The anyconnectOID error you saw earlier indicates that Cisco AnyConnect or enterprise endpoint security software on your PC is intercepting TLS traffic and enforcing strict client certificate rules.

How to resolve this for RaiDrive/PC:

1.Apply a matching SSL Certificate:

Go to TOS > Control Panel > Security > SSL Certificate and import or apply a valid SSL certificate matching your *.duckdns.org domain (such as a free Let's Encrypt certificate). Once the certificate matches the domain, RaiDrive will connect securely without throwing certificate errors.

2. Use HTTP (Port 8800) as an alternative:

If you do not want to set up an SSL certificate, forward port 8800 on your router and connect via standard HTTP in RaiDrive.

Glad to see the core issue isolated and working!

[bull5]

Solved using HTTP and port 8800 thanks! Great support.

But you have to do the 2 steps below in windows


Step 1: Modify the Windows Registry

1. Press the Windows Key + R on your keyboard to open the Run dialog box.
2. Type regedit and press Enter to open the Registry Editor.
3. In the left sidebar, navigate to the following path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
4. Click on the Parameters folder, then look at the right pane. Double-click on the value named BasicAuthLevel.
5. Change the Value data from 1 to 2, then click OK. (Value 2 forces Windows to accept credentials over both HTTP and unverified HTTPS connections).




Step 3: Restart the WebClient Service

For these changes to take effect, you must restart the network service responsible for WebDAV:
1. Press Windows Key + R, type services.msc, and press Enter.
2. Scroll down until you find the service named WebClient.
3. Right-click on WebClient and select Restart. (If it is not running, click Start)