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: 

Intermittent HTTP Connection Failures

‎10-11-2017 13:54

‎10-11-2017 13:54

For the last day or our API connections seem unstable to the Fitbit API backend with our underlying HTTP calls failing: "Message: Unable to connect to the remote server" and "An attempt was made to access a socket in a way forbidden by its access permissions"

 

Is there a hosting / dns / gateway issue going on now?

 

--Aaron

Using Fitbits in Research? Check out Fitabase --www.fitabase.com
Best Answer
Labels:
0 Votes
2 REPLIES 2

‎10-12-2017 13:38

‎10-12-2017 13:38

I'm also seeing a lot of errors come through. Error codes are 504 and 530 

Best Answer
0 Votes

‎10-13-2017 12:44

In response to SteveWT

‎10-13-2017 12:44

We continue to see errors as well. Here's a CF Ray that just occurred resulting in a Status Code of 530 to the devices endpoint:

3ad4af4a99256dae-SJC

 Here is another that returned Status Code 502 to the OA2 token refresh:

3ad4c3a41c726dae-SJC

 

 

Using Fitbits in Research? Check out Fitabase --www.fitabase.com
Best Answer
0 Votes