07-15-2022 15:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-15-2022 15:18
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I recently switched my server to a DigitalOcean droplet and now my subscriber won't verify. It works as expected when I test it from my home computer, but fitbit won't verify it. Is there a way to see the logs for my attempts? It's odd, because my server log doesn't even show the fitbit servers trying to talk to it. Almost like it doesn't like my domain name or certificate. Any help would be greatly appreciated.
Info:
OauthID: 2388TJ
Subscriber ID 4
Answered! Go to the Best Answer.

- Labels:
-
Subscriptions API
Accepted Solutions
07-19-2022 13:05
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-19-2022 13:05
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I switched to a regular DNS provider and everything worked fine. Thanks for
the follow up. No action needed at this time.
Marty

07-19-2022 12:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



07-19-2022 12:59
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @Martys320
Would you please try to verify the subscriber again? I'm having trouble finding the information in our logs.
Thanks!
Gordon
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

07-19-2022 13:05
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

07-19-2022 13:05
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I switched to a regular DNS provider and everything worked fine. Thanks for
the follow up. No action needed at this time.
Marty

