[Help] File Manager [SOLVED]

[PeterRobertson]

Hi
I'm a newbie and a bit confused. When I open File Manager in TOS 6 my WIndows 11 PC (using Chrome browser) tells me that the connection isn't secure and https is not available.
Should I be concerned? Have I missed a step when setting up the NAS?

TIA
Peter

[MikeZhang]

This is normal. The "insecure" message indicates the browser detects the access address as unencrypted. It's normal for this to happen when accessing via IP address on a local network. Our certificate is for the tnas.online access address; therefore, it will display correctly when accessing remotely via tnas.online.

[PeterRobertson]

Thanks Mike. Very helpful and reassuring

[TMroy]

Adding an encryption certificate for local access is possible, but you will need to obtain an SSL certificate for your URL yourself, the prerequisite is that you need to bind a domain name to your NAS.. Because each user's environment is unique, we cannot do this on your behalf; it must be handled by you.

[renob]

Thanks Mike. Very helpful and reassuring

I'd like to clarify what Mike said for you and anyone else who happens to come across this post as what he wrote was incorrect and incomplete.

Your browser is NOT detecting that the site is unencrypted and does not make this claim anywhere in the wording. The connection IS encrypted and the browser knows it. It is simply letting you know that the certificate being provided by the web server on the NAS is not issued by a publicly trusted certificate issuer. Public certificate issuers adhere to strict protocols and guidelines to make sure they are issuing certificates to the legitimate owners or operators of domains and not malicious actors. If they abide by these protocols and guidelines the internet at large including the different browsers will trust the certificates from those issuers and not display the "Connection not secure" errors. Since the certificate is not from a trusted publisher the browser lets you know that you may be communicating with a malicious source.

As of today it is normal in ALL situations, not just in a local network, to receive these untrusted certificate errors when accessing ANYTHING by an IP address while using an encrypted HTTPS connection.

As of the writing of this post I should mention that Let's Encrypt does now issue publicly trusted IP address certificates with only a 6 day validity.
https://letsencrypt.org/2026/01/15/6day ... ailability