LabVIEW HTTP SSL, Certs, and error 363507

[jyoung8711]

So, I've been trying to get the LabVIEW HTTP toolkit working with some HTTPS addresses, and I have not been able to get this to work with the "Verify Server" option set to true.

The "real" use case, is that we have an NI Web Server (the 'newer' apache based server)  running that's exposed on on our company domain

       https://app.mycompany.com

(we actually have several apps, app1 , app2, etc) 

We have a global cert registered for " *.mycompany.com " coming from Go Daddy.

We've loaded our global cert on the NI Web Server running on those. The certs loaded fine, and in all web browsers, stuff works exactly as expected.

When I try to communicate with this server through the LabVIEW HTTP toolkit.  I get the 363507 error "LabVIEW could not verify the authenticity of the server".  I've tried this on LV 2020, LV2022, and LV2023 (all 64-bit)

I understand that the LabVIEW HTTP Toolkit uses it's own NICURL, package which is disconnected with windows browsers, and relies on it's own cert bundle found here : "C:\Program Files\National Instruments\Shared\nicurl\ca-bundle.crt"

I have tried the following:

1. Downloaded the root Go Daddy cert used, and specified that path using the "ConfigSSL.vi"

2. Tried explicitly adding the cert contents to the existing ca-bundle.crt

3. Tried just replacing the ca-bundle.crt file with my Go Daddy cert, (correctly renamed)

4. Tried replacing the ca-bundle.crt file with the latest Mozilla CA certificate store (https://curl.se/docs/caextract.html)

none of this worked.

I do NOT get the same error if I try just doing a GET from https://www.google.com

I do NOT get the same error if I use the .NET HTTP REST interface (however replacing lots of existing code would be undesirable).

After going through the above, I decided to try another test... On my dev system, I switched the NI Web Service to use HTTPS using a self-signed certificate, clicked the "Export Root Certificate" from the Web Server Configuration application, and tried 1, 2, & 3 from above with this certificate, and all options gave me the same errors (again this LabVIEW running from the same machine as the NI Web Server).  I also tried this using hostname, IPAddress, 127.0.0.1, and every other option that came to mind.

I'm a bit at a loss for why neither of these use cases work (as I would expect they would).  I can only guess that I'm just missing something here, but I have no idea what it could be.

I'm hoping that someone out there might be able to shed some light on what I might try to get this working.

Thanks!