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: 

Occasional 400 errors

‎10-28-2015 17:25 - edited ‎10-28-2015 17:26

‎10-28-2015 17:25 - edited ‎10-28-2015 17:26

Since October 23rd, my Fitbit Low Battery Notifier app is getting occasional 400 API errors when requesting user profiles to get battery levels.  It doesn't happen for every request, it's never the same users, and only happens on a few requests of an hourly batch.

 

The full response is:

<html>
<head><title>400 Bad Request</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
<hr><center>cloudflare-nginx</center>
</body>
</html>

I notice you're using CloudFlare; is it possible I'm hitting some kind of rate limit triggering CloudFlare's DoS protection?

Best Answer
0 Votes
14 REPLIES 14

‎10-28-2015 17:32

‎10-28-2015 17:32

@jcs_ wrote:

I notice you're using CloudFlare; is it possible I'm hitting some kind of rate limit triggering CloudFlare's DoS protection?

Most likely. I will tell Fitbit's ops team to check on the IP addresses of your app's servers.

Best Answer
0 Votes

‎11-02-2015 07:36

‎11-02-2015 07:36

I'm experiencing the same type of problems across different api calls. This has been happening for at least a month and happens about 1 out of every 1000 calls.

Best Answer
0 Votes

‎11-02-2015 17:50

In response to ScottQ

‎11-02-2015 17:50

@ScottQ: What is the content of the response when you get the error? If you're seeing a CloudFlare error, please contact us privately with your client id.

Best Answer
0 Votes

‎11-02-2015 18:31 - edited ‎11-02-2015 18:32

In response to JeremiahFitbit

‎11-02-2015 18:31 - edited ‎11-02-2015 18:32

@JeremiahFitbit wrote:

 

Most likely. I will tell Fitbit's ops team to check on the IP addresses of your app's servers.

 

@JeremiahFitbit: Will this take some time to resolve?  I am still getting 400 errors every hour.

Best Answer
0 Votes

‎11-03-2015 06:41

In response to JeremiahFitbit

‎11-03-2015 06:41

@JeremiahFitbit We are also getting occasional 400 Errors. Here is the HTTP response we are getting:

 

Http Status Code: BadRequest
HTTP Content: 400 Bad Request - cloudflare-nginx

 

 

Here is the list of errors from the last 2 weeks (Pacific Time):

 

11/2/2015 8:32 PM
11/2/2015 1:50 PM
11/2/2015 12:54 PM
11/2/2015 7:19 AM
11/2/2015 7:09 AM
11/1/2015 10:39 PM
11/1/2015 3:27 PM
10/31/2015 12:10 PM
10/31/2015 7:32 AM
10/30/2015 11:34 PM
10/30/2015 10:26 PM
10/30/2015 9:46 PM
10/30/2015 10:46 AM
10/30/2015 8:09 AM
10/29/2015 11:46 AM
10/29/2015 10:31 AM
10/29/2015 9:05 AM
10/29/2015 7:18 AM
10/28/2015 12:03 AM
10/27/2015 9:02 PM
10/27/2015 1:52 PM
10/27/2015 1:51 PM
10/27/2015 12:27 PM
10/27/2015 12:17 PM
10/27/2015 12:04 PM
10/27/2015 12:04 PM
10/27/2015 11:33 AM
10/27/2015 11:33 AM
10/27/2015 11:32 AM
10/27/2015 11:15 AM
10/26/2015 1:05 PM
10/26/2015 9:00 AM
10/26/2015 7:05 AM
10/26/2015 12:59 AM
10/26/2015 12:50 AM
10/25/2015 9:15 PM
10/25/2015 1:56 PM
10/25/2015 12:24 PM
10/25/2015 10:58 AM
10/25/2015 10:29 AM
10/25/2015 10:14 AM
10/25/2015 10:04 AM
10/25/2015 9:12 AM

Best Answer
0 Votes

‎11-03-2015 10:43

In response to FedericoArg

‎11-03-2015 10:43

@FedericoArg: Please contact Web API support privately with your client id.

Best Answer
0 Votes

‎11-12-2015 06:46

In response to JeremiahFitbit

‎11-12-2015 06:46

@JeremiahFitbit I have submitted this issue privately on Nov 3 and have not received any response from yet.

 

For over a month we have been receiving occasional 400 Bad Request errors. Is this error being investigated? Are there any plans to address this?

 

Thanks!

 

Best Answer
0 Votes

‎11-16-2015 14:19

In response to FedericoArg

‎11-16-2015 14:19

I also sent an e-mail to api@fibit.com a week ago and received an auto-reply but no follow up from anyone.  These errors are still persisting as of this afternoon.

 

Best Answer
0 Votes

‎11-16-2015 14:35

In response to jcs_

‎11-16-2015 14:35

I think I follow up with your email on Friday but the gist of it is we are troubleshooting this issue with Cloudflare and our operations team. We will let you know both via email and here once we have an update or resolution. Sorry for the inconvenience.

Best Answer
0 Votes

‎11-23-2015 09:40 - edited ‎11-23-2015 09:40

In response to SunsetRunner

‎11-23-2015 09:40 - edited ‎11-23-2015 09:40

@jcs_@FedericoArg We've received a response and resolution from Cloudflare on this issue. Are you still seeing this problem?

Best Answer

‎11-23-2015 10:01

In response to SunsetRunner

‎11-23-2015 10:01

@SunsetRunner Looks like the last Bad Request error we received was from 3 days ago (11/20/2015 10:08 AM Pacific).

 

Looks like the solution worked. I'll let you know if we encounter this issue again.

 

Thank you very much for looking into this!

 

Federico

Best Answer
0 Votes

‎11-23-2015 10:01

In response to FedericoArg

‎11-23-2015 10:01

@FedericoArg wrote:

@SunsetRunner Looks like the last Bad Request error we received was from 3 days ago (11/20/2015 10:08 AM Pacific).

 

Looks like the solution worked. I'll let you know if we encounter this issue again.

 

Thank you very much for looking into this!

 

Federico

Thanks for the quick reply!

Best Answer
0 Votes

‎11-23-2015 10:50

In response to SunsetRunner

‎11-23-2015 10:50

I haven't seen any today, not sure about the past weekend. If I see any, I'll make sure I post here.

Best Answer
0 Votes

‎11-23-2015 12:30

In response to ScottQ

‎11-23-2015 12:30

@ScottQ wrote:

I haven't seen any today, not sure about the past weekend. If I see any, I'll make sure I post here.

Thank you for the report!

Best Answer
0 Votes