Cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Subscriber Failing on new Server

ANSWERED

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

Best Answer
0 Votes
1 BEST ANSWER

Accepted Solutions
I think the issue was with my DNS. It was actually a DDNS name that I had.
I switched to a regular DNS provider and everything worked fine. Thanks for
the follow up. No action needed at this time.

Marty

View best answer in original post

Best Answer
0 Votes
2 REPLIES 2

Hi @Martys320 

 

Would you please try to verify the subscriber again?   I'm having trouble finding the information in our logs.

 

Thanks!

Gordon

Gordon Crenshaw
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google
Best Answer
0 Votes
I think the issue was with my DNS. It was actually a DDNS name that I had.
I switched to a regular DNS provider and everything worked fine. Thanks for
the follow up. No action needed at this time.

Marty
Best Answer
0 Votes