CODE reports untrusted NC TLS certificate

ℹ️ Support 📄 Office
,
1

Followed this and 3 of the 4 tests pass, but this one fails. Can’t seem to figure out what the problem is.
Both programs are running in containers on TrueNAS, output from the Collabera shell:

cool@71807853469a:/$ curl -v https://nc.technospider.com/status.php
*   Trying 192.168.2.2:443...
* Connected to nc.technospider.com (192.168.2.2) port 443 (#0)
* ALPN: offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (OUT), TLS alert, unknown CA (560):
* SSL certificate problem: unable to get local issuer certificate
* Closing connection 0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.
2

Your CODE container doesn’t trust your clouds TLS cert (or at least the curl binary). Google CA seems not really new but till now I was not familiar with it… the CODE container CA bundle might be not up-to-date as well. I would review CA stores of the CODE container and add the Google CA there (if missing).

Update: the curl command above on my CODE is successful against your cloud - please try updating.

3

I cleared out all my settings, turned off the proxy for the Collabora server, turned it back on, and tried again and now all is well.
Never changed any of the ssl files, so I don’t know what the issue was.