08-14-2022 05:21
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

08-14-2022 05:21
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I am trying to implement a subsciber endpoint. But when I click on the verify button in the app configuration, it fail.
Checking my server log, I see no requests at all to the endpoint happening at all to https://webhook.x2.energy/fitbit
I see requests I make with a browser comming in just fine. It looks like fitbit server isn't even trying to access the URL at all when I click verify.

- Labels:
-
Subscriptions API
08-15-2022 17:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



08-15-2022 17:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @innoEnergy,
Welcome to the forums!
Can you DM me your client id so I can take a look at our logs?

09-01-2022 14:45
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



09-01-2022 14:45
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @innoEnergy,
I've taken over this problem and I've been reading up the progress from John. It sounds like the problem is currently with the certificates from your internet/host provider. Are you still having a problem verifying your subscriber? If so, do you know if the certificates are self-signed?
Thanks!
Gordon
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

09-18-2022 03:58
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

09-18-2022 03:58
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hello Gordon
Thank you for looking into our problem. We are using a GoDaddy Certificate (Go Daddy Secure Certificate Authority - G2). It seems like you are using curl or something similar which is not accepting GoDaddy certificates. They using different certificates like openSSL or other mechanismn. If you add GoDaddy Certificates or call curl with -k option it will not make problems.
Error while "curling":
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html

09-19-2022 18:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



09-19-2022 18:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi @innoEnergy
I'm going to send you a private message to collect some information from you.
Gordon
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

09-23-2022 08:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



09-23-2022 08:11
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
According to the site digicert.com, it is determined the certificates being used from GoDaddy are not trusted. I suggest reaching out to GoDaddy to fix the untrusted certificates or use another certificate authority that provides trusted certificates.
Gordon
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

09-26-2022 02:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

09-26-2022 02:50
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
I spoke with GoDaddy and they asked for more Information. They are one of the biggest certification companys and be also trusted by the most other certification companys… which kind of certificate is required? A special company validation?

09-27-2022 12:53
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



09-27-2022 12:53
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
It might be a good place to start by asking them why their certificate is showing as untrusted. I'll send you a private message with the information I received.
Senior Technical Solutions Consultant
Fitbit Partner Engineering & Web API Support | Google

