Issue template update

[PeterDaveHello]

This could make sure the situation is more like what it really is, and also make the output smaller.

[ljharb]

LGTM as long as you can confirm that when there are SSL certificate errors, -I will include that information (which seems likely)

[PeterDaveHello]

sorry that I think I didn't follow the situation up here, do you mean the last test failed?

[ljharb]

@PeterDaveHello no, i mean, the sole purpose of having that curl command in the readme is to expose when a user's SSL certificate authorities are out of date, thus making them unable to connect to nodejs.org - so I'm asking if -I will include that information in that failure case?

[PeterDaveHello]

@ljharb you'll get something like this if the cert is invalid:

curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

curl will tell what the problem is there, no problem at all