Error while installing sample proxies via GitHub in Edge APIGEE

[charan19n]

C:\curl>curl https://mysubdomain.zendesk.com/api/v2/groups.json ^-v -u myemail@example.com:mypassword * Trying 54.172.126.223:443... * TCP_NODELAY set * Connected to mysubdomain.zendesk.com (54.172.126.223) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: C:\curl\curl-ca-bundle.crt CApath: none * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (OUT), TLS alert, unknown CA (560): * SSL certificate problem: self signed certificate in certificate chain * Closing connection 0 curl: (60) SSL certificate problem: self signed certificate in certificate chain More details here: https://curl.haxx.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.

[imesh]

Above error says following:

SSL certificate problem: self signed certificate in certificate chain More details here: https://curl.haxx.se/docs/sslcerts.html curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it.

However, the same API request seems to be working without any TLS certificate errors:

$ curl -i https://mysubdomain.zendesk.com/api/v2/groups.json
HTTP/1.1 404 Not Found
Server: nginx
Date: Tue, 11 Jun 2019 04:19:44 GMT
Content-Type: application/json; charset=UTF-8
Content-Length: 244
Connection: keep-alive
Strict-Transport-Security: max-age=0;
Cache-Control: no-cache
X-Zendesk-Origin-Server: app2.pod23.use1.zdsys.com
X-Request-Id: c6a926dc57a3b2568e70b2614620e7a8
X-Runtime: 0.019312
X-Zendesk-Request-Id: 30c82319790e2623ee4c
{
  "error": {
    "title": "No help desk at mysubdomain.zendesk.com",
    "message": "There is no help desk configured at this address. This means that the address is available and that you can claim it at http://www.zendesk.com/signup"
  }
}

You may need to check the TLS certificate chain configured in the virtual host of the above API proxy if this issue is still occurring:

# Management API Resources:

GET /organizations/{org}/environments/{env}/virtualhosts/{virtual-host}
GET /organizations/{org}/environments/{env}/keystores/{keystore}
GET /organizations/{org}/environments/{env}/keystores/{keystore}/certs/{cert}