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: 

Large quantity of 502 errors.

ANSWERED

‎06-24-2020 09:39 - edited ‎06-24-2020 09:43

‎06-24-2020 09:39 - edited ‎06-24-2020 09:43

Around 7 AM Central, we started receiving the following 502 responses to our requests for data (which we request in response to notifications via the subscription API).

 

<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>

 

At first it was a few, which quite often seem to go away, but now climbing to over 10% of the responses we receive.

 

We see no other communication errors with any other endpoints we interface with, just with https://api.fitbit.com.

 

Can you assist?

 

 

Best Answer
Labels:
0 Votes
1 BEST ANSWER

Accepted Solutions

‎06-24-2020 11:57

In response to Gordon-C

‎06-24-2020 11:57

I believe we have fixed the 502 errors now.  Please let me know if you're still seeing them during your next batch pull

Gordon Crenshaw
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

View best answer in original post

Best Answer
0 Votes
12 REPLIES 12

‎06-24-2020 10:14

‎06-24-2020 10:14

We have observed a similar situation.  We poll ~3k users every hour and have had internal alerts go off due to the number of 502 responses the past two hours.

 

Fitbit's status page is still green.

Best Answer

‎06-24-2020 10:28

In response to LifeOmic-Dev

‎06-24-2020 10:28

Hi @jeaglemc  and @LifeOmic-Dev  for reporting the 502 errors.  I'm looking into it.

 

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

‎06-24-2020 10:37

In response to Gordon-C

‎06-24-2020 10:37

We've updated fitbitstatus.com for this incident and will post updates on that site going forward.  If you have not signed up to receive updates from fitbitstatus.com, please go to the web site to subscribe.

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

‎06-24-2020 10:51

In response to Gordon-C

‎06-24-2020 10:51

@jeaglemc  and @LifeOmic-Dev ,

 

I'm seeing the 5xx errors have dropped in our graphs.  Are you still experience the problem?

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

‎06-24-2020 10:55

In response to Gordon-C

‎06-24-2020 10:55

@Gordon-C 

We have an hourly ingestion coming up soon.  I'll reply again once I see how those responses look.

Best Answer
0 Votes

‎06-24-2020 11:09

In response to Gordon-C

‎06-24-2020 11:09

Our recent batch of data pulls (in response to Subscription API notifications) is still receiving a high number of 502 responses - I would say about the same quantity that made me decide I should notify Fitbit.  In addition to the:

 

<html>
<head><title>502 Bad Gateway</title></head>
<body bgcolor="white">
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>

 

... response, we're now seeing one that's formatted this way:


<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>

 

The first format is the majority ... we're receiving a smaller quantity of the second format.

 

Kind regards.

 

Jay

Best Answer
0 Votes

‎06-24-2020 11:14

In response to LifeOmic-Dev

‎06-24-2020 11:14

It looks like we received roughly the same number of 502 errors with this latest bulk ingest.

Best Answer
0 Votes

‎06-24-2020 11:19

In response to LifeOmic-Dev

‎06-24-2020 11:19

Thank you.   We're still investigating.   

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

‎06-24-2020 11:57

In response to Gordon-C

‎06-24-2020 11:57

I believe we have fixed the 502 errors now.  Please let me know if you're still seeing them during your next batch pull

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

‎06-24-2020 12:22

In response to Gordon-C

‎06-24-2020 12:22

@Gordon-C That seemed to do the trick this time.  Thanks!

Best Answer
0 Votes

‎06-24-2020 12:28

In response to Gordon-C

‎06-24-2020 12:28

All is well now.  Thank you.

Best Answer
0 Votes

‎06-24-2020 12:37

In response to jeaglemc

‎06-24-2020 12:37

Thanks for the update.   We'll continue to monitor the services for a few hours to make certain it doesn't pop back up.   If you see more 5xx, let me know.

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