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: 

Seeing a fair number of 502 and 504 errors.

‎02-18-2020 13:00

‎02-18-2020 13:00

Beginning around 9:44 AM CST, we've been receiving a fair number of 502 and 504 errors to our requests for data.  The 504's are Gateway Timeouts and we don't receive content for them, and the content for the 502's appear like:

 

<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>502 Server Error</title>
</head>
<body text=#000000 bgcolor=#ffffff>
<h1>Error: Server Error</h1>
<h2>The server encountered a temporary error and could not complete your request.<p>Please try again in 30 seconds.</h2>
<h2></h2>
</body></html>
~Bad Gateway~The remote server returned an error: (502) Bad Gateway.

 

We we would normally see 0 to 3 per request cycle, but we've been seeing about 20 to 40 for a while.

 

Can you assist?

 

Kind regards.

 

Jay

Best Answer
Labels:
0 Votes
3 REPLIES 3

‎02-24-2020 11:54

‎02-24-2020 11:54

Hi @jeaglemc,

 

Are you still seeing the 5xx error messages today?   If so, would you please provide me with the endpoints that you're executing?

 

Thanks!

Gordon

Gordon Crenshaw
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
Best Answer
0 Votes

‎02-24-2020 12:42 - edited ‎02-24-2020 12:44

In response to Gordon-C

‎02-24-2020 12:42 - edited ‎02-24-2020 12:44

Hello @Gordon-C -

 

The errors started clearing up about an hour or two after I posted, and by the following morning our 5xx error rate was back to normal -- normal is about 0.001% of our connection attempts, and I think those are because the Internet is sometimes a capricious thing.

 

We re-queue 5xx failed attempts, it's just that a lot of them can cause congestion in our interface (like an accident on the freeway).

 

Thank you!

Jay

Best Answer
0 Votes

‎02-26-2020 16:38

In response to jeaglemc

‎02-26-2020 16:38

Thanks @jeaglemc    We did experience an issue with one of our servers on Monday and fixed it.  We posted updates to fitbitstatus.com.   So, the problem should be resolved now.  If you see 5xxs again, please let us know.

Gordon Crenshaw
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
Best Answer
0 Votes