Node openssl Displays Unsecured Connections from https Service Browser (windows Environment)

  node.js, question

I follow

openssl genrsa -out ca.key 2048
openssl req -new -key ca.key -out ca.csr
openssl x509 -req -in ca.csr -signkey ca.key -out ca.crt
Generate a self-signed root certificate
openssl genrsa -out server.key 2048
openssl rsa -in server.key -pubout -out server.pem
openssl req -new -key server.key -out server.csr
openssl x509 -req -CA ca.crt -CAkey ca.key -CAcreateserial -in server.csr -out server.crt
Generate server certificate

// app.js:
 var options = {
 key: fs.readFileSync(’./keys/server.key’),
 cert: fs.readFileSync(’./keys/server.crt’)
 https.createServer(options, (req, res) => {
 res.end(‘hello world!’  );

Browser accesshttps://localhost:443, showing:

Then I installed ca.crt, went to the “trusted root certificate authority” directory (windows), and visited again and still showed this problem.
After observing fiddler’s method of capturing https, fiddler is also installing its self-signed certificate Do_Not_Trust_fiddlerRoot to’ Trusted Root Certificate Issuing Authority’, and will not report this error when opening Fiddler’s capturing package.
What is the reason?

The signature generated by oneself must be like this. Only the signature issued by a formal ssl certificate authority will be recognized as a security certificate by the browser.
You can apply for a free certificate at a first-class certification authority such as Wharton. After the signature is configured, a green lock will be displayed in front of the browser address bar.