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: 

SocketTimeout exception from Fitbit from 10/30

‎11-24-2015 12:34 - edited ‎11-24-2015 12:34

‎11-24-2015 12:34 - edited ‎11-24-2015 12:34

Fitbit API subscriber for our product was disabled on Friday[30-OCT-2015]. We did not had any issue with subscriber till last 10/29 Thursday. 

 

We enabled the subscriber on Saturday[31-OCT-2015], We were only seeing failure response Exception (SocketTimeoutException) getting added in "subscriber endpoint stats",  again the subscriber was disabled on the same day. 

 

We analysed from our end, we did not have any issue from our product. Looks like, the request from FitBit is not hitting our product subscriber endpoint URL. We noticed that FitBit server was down due to maintenance on Friday and from that point we are facing this issue. 

 

Could you please verify from your end and let us know if there is any issue. It would be great if you can help us on this at the earliest. I have sent an email to Fitbit support. No response.

 

Thanks

Gabriel

Best Answer
Labels:
0 Votes
5 REPLIES 5

‎11-24-2015 12:36

‎11-24-2015 12:36

@GabrielSusai wrote:

Fitbit API subscriber for our product was disabled on Friday[30-OCT-2015]. We did not had any issue with subscriber till last 10/29 Thursday. 

 

We enabled the subscriber on Saturday[31-OCT-2015], We were only seeing failure response Exception (SocketTimeoutException) getting added in "subscriber endpoint stats",  again the subscriber was disabled on the same day. 

 

We analysed from our end, we did not have any issue from our product. Looks like, the request from FitBit is not hitting our product subscriber endpoint URL. We noticed that FitBit server was down due to maintenance on Friday and from that point we are facing this issue. 

 

Could you please verify from your end and let us know if there is any issue. It would be great if you can help us on this at the earliest. I have sent an email to Fitbit support. No response.

 

Thanks

Gabriel

The SocketTimeoutException usually indicates we had trouble trying to connect to your server.

 

Are you whitelisting Fitbit IPs on your subscriber endpoint?

Best Answer
0 Votes

‎11-24-2015 13:13

In response to SunsetRunner

‎11-24-2015 13:13

We are not whitlisting the fitbit IPs. It's open for public. Even our phone clients communicate to the same URL.

Best Answer
0 Votes

‎11-24-2015 14:04

In response to GabrielSusai

‎11-24-2015 14:04

Can you PM me your subscriber endpoint URL and the client id or consumer key of your application?

Best Answer
0 Votes

‎11-25-2015 06:40

In response to SunsetRunner

‎11-25-2015 06:40

Hello Dan - I have sent you a PM mesasge. Please let me know if you need more information.

 

Best Answer
0 Votes

‎11-25-2015 11:44

In response to GabrielSusai

‎11-25-2015 11:44

Thanks, I've responded via PM. 

Best Answer
0 Votes