Please pardon an essay, but there is detail in what seems like a simple problem…
I have a TS-230 running QTS 5.2.4.3092, installed in 2022. The two drives are a RAID 1 pair. My PC running Windows 10, the router, and the NAS are wired together in the same subnet, my home LAN behind NAT. I have been using it as a local cloud, with volumes mapped to Windows letter drives.
I have just rebuilt my machine to be able to run Windows 11. I reinstalled W10 to get the system the same as before, before I upgrade. Before the rebuild, QFinder could find the NAS normally, and it could be accessed as a server by the IP address through a browser. In the new W10, the server is no longer trusted: browsers report that the SSL Certificate is not valid, and QFinder simply fails to find the NAS. I can access the NAS through QLink, but I want the TCP/IP access I had before.
To my mind, there are two possibilities: 1) There is a security setting in W10 which was off before, but is on by default in the new installation. I haven’t found such a setting yet. 2) I need a new network access certificate which will be trusted in the current security environment–the one on the NAS is unchanged since original installation. I don’t know much about them, and have no idea where to look. QNAP provides only a cloud certificate, and specifically states that it is to protect domain access from the internet, not local access by IP.
Thanks for reading; any ideas gratefully received!
You cannot get an SSL cert for a private IP (non FQDN) without either playing with your DNS or trusted cert authority.
Check that you do not have any crappy security software installed that prevents you from skipping over http (just fine in LAN) or untrusted https certs
To better understand your situation, our Support team will likely need to clarify your specific configuration. Please feel free to open a support ticket with us, and our team will be able to assist you directly.
dolbyman: Thanks for your reply–you confirmed I can’t get a private network SSL cert. The problem has to be untrusted certs, but I disabled both my Norton360 and MalwareBytes and no change. I even cycled QFinder Discovery Service, making sure the right UDP port was open on my Norton firewall, but no luck.
SteveKo: My current ticket is Q-202506-18879. The first session concentrated on retrieving the CloudKey, and the original communication problem remains. I plan to ask for another session. I appreciate you reaching out.
If you don’t use HTTPS, then there should be no certificate issues as HTTP is insecure and that is fine on a LAN. Double check all your network settings. Something may have changed there. Are you still on the same subnet as previously? Etc. Etc…
The main issue was QFinder not finding the NAS even though it’s local. I suddenly thought about my Mozilla VPN, and that was the problem. QFinder can’t get through the VPN tunnel, so its search fails. With QFinder on the list of Mozilla’s excluded apps, it’s working fine.