My windows system has already imported the nginx certificate, why is it still unsafe?

Asking for help

I used cfssl to generate an nginx certificate as follows:
```sh
tee ca-csr.json <<- "EOF"
{
"CN": "cfssl",
"hosts": [
"10.17.38.191"
],
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "US",
"ST": "California",
"L": "San Francisco",
"O": "cfssl",
"OU": "devops"
}
]
}
EOF

cfssl gencert -initca ca-csr.json | cfssljson -bare ca

tee ca-config.json <<- "EOF"
{
"signing": {
"default": {
"expiry": "8760h"
},
"profiles": {
"nginx": {
"usages": [
"signing",
"key encipherment",
"server auth",
"client auth"
],
"expiry": "8760h"
}
}
}
}
EOF

tee nginx-csr.json <<- "EOF"
{
"CN": "10.17.38.191",
"hosts": [
"10.17.38.191"
],
"key": {
"algo": "rsa",
"size": 2048
},
"names": [
{
"C": "CN",
"ST": "Beijing",
"L": "Beijing",
"O": "nginx",
"OU": "devops"
}
]
}
EOF

cfssl gencert -ca=ca.pem -ca-key=ca-key.pem -config=ca-config.json -profile=nginx nginx-csr.json | cfssljson -bare nginx
```


Start by reviewing the cfssl commands and the certificate details shown in the screenshots, then check whether Windows trusts ca.pem and whether nginx presents nginx.pem for 10.17.38.191. A useful resolution would identify why the browser still reports the connection as unsafe and document the required certificate or nginx configuration change.

Written by the indexing model from the issue text.