03-05-2021 11:53
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-05-2021 11:53
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
- Who Voted for this post?
I am assuming the problems you had yesterday made it necessary to add some new infrastruture. Any chance you can add them so FCrDNS works.
03-08-2021 12:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-08-2021 12:12
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Facing similar problem with IP address: 34.67.42.66

03-09-2021 10:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

03-09-2021 10:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Ok , so if you are not doing anything about this then remove from your documentation. We corrected this our side when we saw the problem Friday evening, basically removing the FCrDNS validation totally and now just use the X-Fitbit-Signature.
It has now been 4 days since I reported it and no comment / status / acknowledge of the problem. If you offered a better contact model for your system problems then I am more than happy to inform you when you systems are down / having problems. We were alerted instantly when we got an increased error rate on Thursday and again on Friday evening.
regards Paul

03-22-2021 09:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



03-22-2021 09:16
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi everyone,
This problem should be resolved. If you're still having a problem, please let us know.
Gordon
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

