05-27-2015 22:35
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-27-2015 22:35
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
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.

- Labels:
-
Subscriptions API
Accepted Solutions
06-02-2015 18:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-02-2015 18:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
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.

06-02-2015 21:05
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-02-2015 21:05
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Thanks Jeremiah, I figured as much. That's a bummer but I'll switch CAs I guess.

05-28-2015 16:42
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



05-28-2015 16:42
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Are you using TLS+SNI? Fitbit does not support SNI yet.

05-28-2015 18:41 - edited 05-28-2015 21:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-28-2015 18:41 - edited 05-28-2015 21:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
No, no SNI.

05-29-2015 21:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

05-29-2015 21:43
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
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?

06-02-2015 12:29
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post


06-02-2015 12:29
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Please send PM to me your application id.
Senior Software Developer at Fitbit

06-02-2015 18:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



06-02-2015 18:07
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
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.

06-02-2015 21:05
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

06-02-2015 21:05
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Thanks Jeremiah, I figured as much. That's a bummer but I'll switch CAs I guess.

11-20-2015 09:29
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

11-20-2015 09:29
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I'm having this same issue. Can we get more detailed exception descriptions?

11-20-2015 10:31
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



11-20-2015 10:31
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
@thai_sentrian: What's your host name?

11-20-2015 10:47
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

