01-12-2016 08:25 - edited 01-12-2016 10:29
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post

01-12-2016 08:25 - edited 01-12-2016 10:29
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Hi,
My company has two servers receiving calls and making calls to your API.
One for testing https://staging.mydomain.com
One for our production environment https://mydomain.com
The SSL certificate was recently switched from a standard SSL to a wildcard SSL on the staging server. E.g. staging.mydomain.com has been changed to *.mydomain.com, since the update we get the following error:
2016-01-06 16:00:18:000 +0000 SSLHandshakeException
Is it possible the name change is causing the issue? Or might it be something else? Any ideas are appreciated.
The cert is issued by Entrust if that makes a diffrence.
Thanks!

- Labels:
-
Subscriptions API
01-12-2016 14:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post



01-12-2016 14:51
- Mark as New
- Bookmark
- Subscribe
- Permalink
- Report this post
Fitbit supports wildcard TLS certificates. It's likely that there is a problem in your TLS certificate installation. Fitbit is more strict about your certificate being installed than your browser.
To identify the most common issues, try these two TLS certificate verification tools:

