TerraMaster Forum

Just bought and set up a F8 SSD Plus NAS. Trying to get the HTTPS to work. I am here at the forum to request help activating the HTTPS web connections (as so far eveything I have done isn't working).

On the forum, "Live Chat" does nothing and I do not have permission to post in almost every topic in this forum, so I was wondering if anyone from Terramaster could give me your definition of "Support"? It obviously doesn't match my definition.

Oh, and by the way, how does one get the HTTPS turned on for connecting to the NAS?

Hello！
If you want to achieve remote access, it is recommended to go to Control Panel - Network Services - Remote Access - Enable the service to use HTTPS for remote access.
If you want to access TOS using HTTPS within the local network, please go to Network Services - Network - Interface - View Response Ports, and you can also modify the response port for HTTPS.
If none of the above applies, could you please describe the problem you are encountering in more detail?

Yes, I am trying to use https within the local network. There is no choice called View Response Ports on the Interface page.

I am using TOS version 6.0 with a F8 SSD Plus NAS. Under Network - General I have TOS Access Settings with HTTP port 8181, HTTPS port 5443, and Force redirect from HTTP connections to HTTPS connections checked. At the bottom, I see this "Enter the following address in your browser to access TOS" with the URL displayed as https://192.168.2.252:5443

WHen I use that URL, I get this error message "Your connection to this site is not secure", meaning that the HTTPS connection did not work.

WHen I use that URL, I get this error message "Your connection to this site is not secure", meaning that the HTTPS connection did not work.
It is normal to receive this prompt when accessing https://192.168.2.252:5443.

You might like to read this:

viewtopic.php?p=42810#p42810

TMjack wrote: ↑06 Feb 2025, 15:12 WHen I use that URL, I get this error message "Your connection to this site is not secure", meaning that the HTTPS connection did not work.
It is normal to receive this prompt when accessing https://192.168.2.252:5443.

No, it is not normal to receive this prompt. This prompt means that the https connection did not make a secure connection and that the https is not working. Based on your comment, it sounds to me like you are also trying to use an https connection and have been receiving this error message. Trust me, if you are receiving this message then your https connection is also not working.

davidmay wrote: ↑06 Feb 2025, 21:43

When a browser displays that a visit is insecure, it is usually because it determines that the accessed address has not been encrypted. In a LAN environment, it is relatively common for visits using IP addresses to display as insecure, as IP visits typically do not involve Domain Name System (DNS) resolution and the associated SSL/TLS certificate validation. Our SSL certificate is issued for the domain tnas.online, which contains the domain's public key and related information, and is signed by a trusted Certificate Authority (CA). Therefore, when users access remotely using the domain tnas.online, the browser can resolve the corresponding IP address through DNS and validate the SSL certificate's validity, thereby displaying a normal secure connection status. This is because the certificate is bound to the domain, ensuring identity authentication and data transmission encryption for both communicating parties.

Just like requiring a driver's license to prevent chaos on public roads, but now I'm driving my rusty pickup in my own LAN farm - would you force yourself to carry a driver's license? Might be a decent habit, though usually as unnecessary as HTTPS certs in this digital pasture.

Lord.mjj wrote: ↑18 Feb 2025, 18:07

A fine analogy ..... until someone knocks down the gate to your private road and dumps garbage on your property. Then you have to clean up someone else's mess.

Lord.mjj wrote: ↑18 Feb 2025, 18:07

Yes, you are driving on your own LAN farm, but your car automaticlly requests your driving license before you can start the engine even you own your car, but this car has been set to behave like this before it came out from the manufacturer.