02-05-2018 04:47 - edited 02-06-2018 02:36
02-05-2018 04:47 - edited 02-06-2018 02:36
Hi everyone, @JeremiahFitbit, @AndrewFitbit, @DavidSFitbit, anyone (please help, also thank you!) 🙂
I am wondering why in the dev web application console, it would be not possible to verify some servers and not others.
Are there any limits, are there blacklists?
I have verified that the test server in question is:
- open for inbound requests
- receives requests from other sources
Also I have verified that:
- other servers with the same domain can receive verify requests
- there is already a working, verified subscription working with our production servers
The only conclusion, I have come to is that there is a blacklist on Fitbit's side, as on our side, we can see in our access logs that:
- Fitbit is able to reach our production servers
- is unable to reach our test servers (irrespectively of the verification token)
- any non-Fitbit verification request is able to reach our test servers
I appreciate any help you can provide! 🙂
Thanks,
Piotr.
02-08-2018 15:10
02-08-2018 15:10
@piotr-zywien please PM to me your app id and I'll be able to check your subscription urls.