I see "SSLException" logged on the Fitbit subscriberstats page for the app when Fitbit calls my subscription end point.
I'm almost certain it's because Azure (where my app is hosted) quite often uses TLS + SNI which isn't supported by Fitbit (for others interested in HTTPS requirements check out "Using HTTPS" under https://dev.fitbit.com/docs/subscriptions/#configuring-a-subscriber).
I used Runscope as the middle man to help figure this out (FYI, it appears that Runscope have updated their screens so it would be helpful if you updated your help re: setting up runscope: https://dev.fitbit.com/docs/subscriptions-debugging/)
Are the HTTPS requirements listed for Fitbit subscription end point call purely for the POST call… are the requirements different for the verification call? (since it seems to be able to do the GET verify call ok, but not the POST activity call – note, I’m not 100% sure about if the GET call succeeded or not - I was making lots of changes to try and figure out the issue).
Are there any plans to support TLS + SNI (any reason why it isn't currently supported)?
As some feedback, it might be useful to have something in the documentation that talks about common errors in the subscription activity screen and want they might be caused by e.g. SSLException didn’t help me much.
Also I logged these questions as a support email on the 24th June and haven't heard back yet.
