02-18-2020 13:00
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

02-18-2020 13:00
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
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

- Labels:
-
Subscriptions API
02-24-2020 11:54
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



02-24-2020 11:54
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
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
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

02-24-2020 12:42 - edited 02-24-2020 12:44
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

02-24-2020 12:42 - edited 02-24-2020 12:44
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
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

02-26-2020 16:38
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



02-26-2020 16:38
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
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.
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

