Push Notification using https generate response code SSLHandshakeException

[andy222]

Hi,

Push Notification using https generate response code SSLHandshakeException. 

Any help solving this issue will be appreciated.

Thank you

This is console output from "curl -v https://xxx.yyy.com/fitbit/echo": 

:~ test$ curl -v https://xxx.yyy.com/fitbit/echo

* Adding handle: conn: 0x7fbe92804400

* Adding handle: send: 0

* Adding handle: recv: 0

* Curl_addHandleToPipeline: length: 1

* - Conn 0 (0x7fbe92804400) send_pipe: 1, recv_pipe: 0

* About to connect() to xxx.yyy.com port 443 (#0)

*   Trying XXX.XXX.XXX.XXX...

* Connected to xxx.yyy.com (XXX.XXX.XXX.XXX) port 443 (#0)

* TLS 1.0 connection using TLS_RSA_WITH_AES_128_CBC_SHA

* Server certificate: xxx.yyy.com

* Server certificate: Go Daddy Secure Certificate Authority - G2

* Server certificate: Go Daddy Root Certificate Authority - G2

> GET /fitbit/echo HTTP/1.1

> User-Agent: curl/7.30.0

> Host: xxx.yyy.com

> Accept: */*

> 

< HTTP/1.1 200 OK

< X-Powered-By: Express

< Content-Type: text/html; charset=utf-8

< Content-Length: 155

< ETag: "59331560"

< Date: Wed, 27 May 2015 15:28:13 GMT

< Connection: keep-alive

< 

* Connection #0 to host xxx.yyy.com left intact

[JeremiahFitbit · Accepted solution]

Go Daddy Root Certificate Authority - G2 has issues. See https://community.fitbit.com/t5/Web-API/Why-am-I-seeing-SSLPeerUnverifiedException-errors-in-my/m-p/...

[andy222]

Thank you