Nagios and OpsGenie API issues
Posted: Fri Aug 14, 2020 11:01 am
We are getting a Peer's Certificate issuer is not recognized. when we run the following CURL command for API access.
[root@nagios ~]# curl -XGET "https://nagios.acentek.net/nagiosxi/api ... =localhost"
curl: (60) Peer's Certificate issuer is not recognized.
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.
If we run the URL from the Curl command in our browser we get localhost info back. And if we run the CURL command with -k at the end we get localhost info as expected. We don't know why we are having Certificate verification errors.
[root@nagios ~]# curl -XGET "https://nagios.acentek.net/nagiosxi/api ... =localhost"
curl: (60) Peer's Certificate issuer is not recognized.
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.
If we run the URL from the Curl command in our browser we get localhost info back. And if we run the CURL command with -k at the end we get localhost info as expected. We don't know why we are having Certificate verification errors.