help menu

Join us on the Community Forums!

  • Community Guidelines

    The Fitbit Community is a gathering place for real people who wish to exchange ideas, solutions, tips, techniques, and insight about the Fitbit products and services they love. By joining our Community, you agree to uphold these guidelines, so please take a moment to look them over.

  • Learn the Basics

    Check out our Frequently Asked Questions page for information on Community features, and tips to make the most of your time here.

  • Join the Community!

    Join an existing conversation, or start a new thread to ask your question. Creating your account is completely free, and takes about a minute.

Not finding your answer on the Community Forums?

Cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Cannot verify subscriber end point

‎11-11-2016 05:26 - edited ‎11-11-2016 05:29

‎11-11-2016 05:26 - edited ‎11-11-2016 05:29

The subscriber end-point verification fails. However I have no entry of an access in my logs. I can however just copy-paste the notify-endpoint into the browser, and that gives me a log entry, so logs and firewalls work correctly.

 

It seems the fitbit server does not trust our certificate and never accesses the actual endpoint. Our CA is COMODO, so that's fairly well-known. 

 

However we ran into a similar issue ourselves and had to update the curl certs. Seeing as you're running Ubuntu and curl just like us, maybe your CA certs are also outdated?

 

You can check with curl whether you can access api.switch.southerncross.co.nz : If that gives you an error 60, then that's the same problem.

Best Answer
Labels:
0 Votes
2 REPLIES 2

‎11-11-2016 10:26

‎11-11-2016 10:26

@SamSam222 Can you PM me your subscriber endpoint?

Andrew | Community Moderator, Fitbit

What motivates you?
Best Answer
0 Votes

‎11-30-2016 02:25 - edited ‎11-30-2016 02:27

In response to AndrewFitbit

‎11-30-2016 02:25 - edited ‎11-30-2016 02:27

Is there an update to this? We've replaced our certificate to conform with your non-standard requirements (common name is deprecated: we added it anyway), but I still see SSL handshake errors on the end-point after a successful verification. The certificate is definitely valid according to the https://cryptoreport.websecurity.symantec.com/checker/ you sent me.

 

This seems to be a problem on your end now, maybe you still need to update curl?

Best Answer
0 Votes