Hi!
This problem is independent of the target NAS to be managed. I have two TrueNAS CORE systems but one current TrueNAS CE 25.10. All of them show the same problem.
All NAS systems have a proper valid certificate for my internal domain. I imported the CA that signed them to TrueCommand. When I try to connect a system TrueCommand complains like this:
Now why should the cert of the NAS system be valid for “localhost”? That NAS has got an FQDN and the certificate is a wildcard cert for my internal domain. Perfectly valid for any system (including my desktop) trusting my local CA. The error is not about trust - it’s about the CN. Of course I used freenas2.my.local.domain in TrueCommand as the address of the NAS to be managed.
Someone (TrueCommand) is seriously confused about how TLS works. When I check “ignore all SSL errors”, of course “everything works”. But that’s not really a solution for an enterprise product.
I don’t need TC, just thought, hey, give it a spin, like I suggested in that other thread.
Kind regards,
Patrick