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
Showing results for 
Show  only  | Search instead for 
Did you mean: 

SocketTimeoutException on webhook

‎05-29-2016 06:03

‎05-29-2016 06:03

Hi Fitbit team,

I currently have an issue where my webhook messages are all timing out, and the endpoint has already been disabled once. I've had legitimate timeout issues in the past, due to downtime or network issues on my end, but this time my server is fine. I can't see any issues with it and I can ping api.fitbit.com from it without a problem. I'm wondering if there are network issues on your end at the moment because I just can't see any problems here.

Can you please investigate? My client ID is 2292KR.

Thanks!
Best Answer
Labels:
0 Votes
1 REPLY 1

‎05-29-2016 18:01

‎05-29-2016 18:01

10 hours later, when I turn this back on manually it works, phew. I'd still like to know what the cause was though, if you could verify that you had an issue.
Best Answer
0 Votes