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: 

Subscription giving only SocketTimeoutException since 2015/10/30

‎11-11-2015 22:13

‎11-11-2015 22:13

Subscription was working fine until 2015-10-30 04:57:45:057 +0000, after that its all SocketTimeoutException. I cheked our log and it seems that no call was made to our endpoint url since the above date. Please help us.

Best Answer
Labels:
0 Votes
2 REPLIES 2

‎11-12-2015 12:11

‎11-12-2015 12:11

That indicates that we had trouble trying to communicate with your subscription endpoint. Can you verify that your endpoint is up and responding in a timely manner?

Best Answer
0 Votes

‎11-18-2015 03:53 - edited ‎11-18-2015 03:53

In response to SunsetRunner

‎11-18-2015 03:53 - edited ‎11-18-2015 03:53

Yes, it is up. I tried making calls to the endpoint and its working fine.

Best Answer
0 Votes