TerraMaster Forum

TMtina wrote: ↑26 Oct 2025, 17:13

bitconductor wrote: ↑26 Oct 2025, 16:33

Hello, we have noticed that the certificate for the tnas.link domain has recently expired. Our team is currently processing the renewal. This will not affect your normal access to the device or the use of its core functions. Thank you for your patience and understanding.

When can we expect an update?

TMtina wrote: ↑26 Oct 2025, 17:13

bitconductor wrote: ↑26 Oct 2025, 16:33

Hello, we have noticed that the certificate for the tnas.link domain has recently expired. Our team is currently processing the renewal. This will not affect your normal access to the device or the use of its core functions. Thank you for your patience and understanding.

Hi there.
could you tell us when you are waiting to finishing for the renewal sert for tnas.link\tnas.online domain?
its importnat for me because i usually directly share files with my collegues from my nas f4-424

10x in advance.

ganezzi wrote: ↑05 Nov 2025, 04:14

If you are using a higher version of the TOS system, you can automatically update the certificate by restarting the TNAS.online service.

TMzethar wrote: ↑05 Nov 2025, 15:36

ganezzi wrote: ↑05 Nov 2025, 04:14

If you are using a higher version of the TOS system, you can automatically update the certificate by restarting the TNAS.online service.

Yes i am using F2-424 (6.0.783).
But if the problem isn't related to the certificate, then why can't anyone access the file I shared with TNAS via the link?

ganezzi wrote: ↑08 Nov 2025, 18:26

We apologize, but we only recently received this information: Due to system optimization, the service for updating system certificates has been removed in versions 6.0.770 and later. This also means that the latest version 6.0.783 cannot update certificates via a reboot.

You can try using the TOS 6.0.783 (X86) Patch Update at the following link to update your certificate: viewtopic.php?t=9240

EthanLiu wrote: ↑08 Nov 2025, 20:06

ganezzi wrote: ↑08 Nov 2025, 18:26

We apologize, but we only recently received this information: Due to system optimization, the service for updating system certificates has been removed in versions 6.0.770 and later. This also means that the latest version 6.0.783 cannot update certificates via a reboot.

You can try using the TOS 6.0.783 (X86) Patch Update at the following link to update your certificate: viewtopic.php?t=9240

That patch doesn't fix the certificate problem. And support doesn't even answer tickets half the time. We need an updated certificate and the ability to install on reboot should be restored.

Even after TNAS updated it's certificate all browsers are still showing an error with the certificate and can no log in securely. So what now? Support says certificate is fine and wants to ignore the problem that didn't exist until they changed the way the way their system updates the certificate.

tc0566 wrote: ↑12 Nov 2025, 00:15

I learned that the technical support email initially informed you of the reason and solution. I can briefly summarize it here.

The 'insecure' warning occurs because the NAS cannot provide a certificate for the local network (each NAS may has a different LAN IP in each person's usage environment).

The simplest method is to set up local DNS resolution:
xxx.xxx.xxx.xxx ???.tnas.link
(Edit this fil as administrator C:\Windows\System32\drivers\etc\hosts)

Afterward, you can access the NAS using ???.tnas.link instead of the LAN IP on your computer to bypass the 'insecure' warning.

TMzethar wrote: ↑12 Nov 2025, 09:14

tc0566 wrote: ↑12 Nov 2025, 00:15

I learned that the technical support email initially informed you of the reason and solution. I can briefly summarize it here.

The 'insecure' warning occurs because the NAS cannot provide a certificate for the local network (each NAS may has a different LAN IP in each person's usage environment).

The simplest method is to set up local DNS resolution:
xxx.xxx.xxx.xxx ???.tnas.link
(Edit this fil as administrator C:\Windows\System32\drivers\etc\hosts)

Afterward, you can access the NAS using ???.tnas.link instead of the LAN IP on your computer to bypass the 'insecure' warning.

Yeah and that is not an answer. Does that provide secure access to the server...NO. And this is the warning from chrome. Editing host file does not work and leads to a gateway timeout. Cannot connect to NAS using 8181 does not work either. And now the error is this : net::ERR_CERT_COMMON_NAME_INVALID

Hi,

I’m on a TNAS-F5-421 with TOS 4.2.40. TNAS.online is running and registered (Regist cloud success), DNS and network to app.terra-master.com are fine, but the HTTPS certificate presented by TNAS.online (tnas.link) has been expired for 63 days.

I’ve restarted the online service, nginx, checked date/time, and even performed a full NAS reboot, but the certificate hasn’t updated.

I verified the certificate presented by TNAS.online via command line:

openssl s_client -connect tnas.link:443 -servername tnas.link </dev/null 2>/dev/null | openssl x509 -noout -dates -subject


It shows:

notBefore=Sep 16 2025
notAfter=Dec 15 2025
subject=/CN=tnas.link


Meanwhile, the local nginx certificate (/etc/nginx/server.crt) is valid until Dec 15 2026, so the expired certificate comes from TNAS.online, not the NAS itself.

Given that the certificate has been expired for over two months, this seems like a server-side issue on TerraMaster. Is there a way to manually refresh the TNAS.online certificate, or can you confirm when it will be renewed?

Thanks for your assistance!