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: 

High traffic app being disabled

ANSWERED

‎02-26-2018 13:46

‎02-26-2018 13:46

Hi Fitbit! We have a high traffic app that is getting disabled but can't seem to get more information about the issue. The metrics and status codes on our side look consistent over the past 30-90 days. Any help would be appreciated!

Best Answer
Labels:
0 Votes
1 BEST ANSWER

Accepted Solutions

‎02-27-2018 14:38 - edited ‎02-27-2018 14:38

In response to newcomer

‎02-27-2018 14:38 - edited ‎02-27-2018 14:38

@jlyke,

 

We looked into the stats based on provided encoded client  id. You api subscriber is being disable because we receive lots of 500s from you. Here is the example of response:

Subscriber id=XXXX; Received bad HTTP status: 500. Elapsed time: 148. Response headers: Content-Type=text/html; Date=Tue, 27 Feb 2018 16:19:26 GMT; Server=nginx; Content-Length=192; Connection=keep-alive {4}
Response Body: <html>
<head><title>500 Internal Server Error</title></head>
<body bgcolor="white">
<center><h1>500 Internal Server Error</h1></center>
<hr><center>nginx/1.8.0</center>
</body>
</html>

Here are some (not all) timestamps (GMT) when it happened: 

2018-02-27 16:19:22

2018-02-27 16:20:17

2018-02-27 16:20:27

2018-02-27 16:20:36

 

Could you please check any errors on your side? 

 

Thanks,

Oleg

View best answer in original post

Best Answer
0 Votes
2 REPLIES 2

‎02-26-2018 21:46

‎02-26-2018 21:46

Hi @jlyke,

 

Could you please send me through private message your client encoded id, so we could find out more details regarding your case?

 

Thanks,

Oleg

 

 

Best Answer
0 Votes

‎02-27-2018 14:38 - edited ‎02-27-2018 14:38

In response to newcomer

‎02-27-2018 14:38 - edited ‎02-27-2018 14:38

@jlyke,

 

We looked into the stats based on provided encoded client  id. You api subscriber is being disable because we receive lots of 500s from you. Here is the example of response:

Subscriber id=XXXX; Received bad HTTP status: 500. Elapsed time: 148. Response headers: Content-Type=text/html; Date=Tue, 27 Feb 2018 16:19:26 GMT; Server=nginx; Content-Length=192; Connection=keep-alive {4}
Response Body: <html>
<head><title>500 Internal Server Error</title></head>
<body bgcolor="white">
<center><h1>500 Internal Server Error</h1></center>
<hr><center>nginx/1.8.0</center>
</body>
</html>

Here are some (not all) timestamps (GMT) when it happened: 

2018-02-27 16:19:22

2018-02-27 16:20:17

2018-02-27 16:20:27

2018-02-27 16:20:36

 

Could you please check any errors on your side? 

 

Thanks,

Oleg

Best Answer
0 Votes