05-27-2015 22:35
05-27-2015 22:35
Hi,
I'm attempting to set up a webhook subscriber and so far I'm only getting failures with the cryptic error reason "SSLHandshakeException". It seems this is a Java exception (I guess that's what the Fitbit server uses) but it can be caused by a number of reasons.
My server at exist.io definitely supports TLSv1 as outlined in the API docs, but perhaps you don't recognise my SSL cert? It's not self-signed but it is verified by StartCom (perhaps a vendor Fitbit's library doesn't recognise?)
Any help would be appreciated.
Answered! Go to the Best Answer.
Best Answer06-02-2015 18:07
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
06-02-2015 18:07
Fitbit currently uses Java 7 and StartCom is not a recognized certificate authority in that version. We will be supporting more certificate authorities in the future. For now, you will need to use another CA.
Best Answer06-02-2015 21:05
06-02-2015 21:05
Thanks Jeremiah, I figured as much. That's a bummer but I'll switch CAs I guess.
Best Answer05-28-2015 16:42
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
05-28-2015 16:42
Are you using TLS+SNI? Fitbit does not support SNI yet.
Best Answer05-28-2015 18:41 - edited 05-28-2015 21:51
05-28-2015 18:41 - edited 05-28-2015 21:51
No, no SNI.
Best Answer05-29-2015 21:43
05-29-2015 21:43
I've been testing various options such as turning on SSLv3 and resetting nginx to the default list of supported ciphers, but still no luck. Perhaps a cert issue?
Best Answer06-02-2015 12:29
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
06-02-2015 12:29
Please send PM to me your application id.
Best Answer06-02-2015 18:07
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
06-02-2015 18:07
Fitbit currently uses Java 7 and StartCom is not a recognized certificate authority in that version. We will be supporting more certificate authorities in the future. For now, you will need to use another CA.
Best Answer06-02-2015 21:05
06-02-2015 21:05
Thanks Jeremiah, I figured as much. That's a bummer but I'll switch CAs I guess.
Best Answer11-20-2015 09:29
11-20-2015 09:29
I'm having this same issue. Can we get more detailed exception descriptions?
Best Answer11-20-2015 10:31
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
11-20-2015 10:31
@thai_sentrian: What's your host name?
Best Answer11-20-2015 10:47