11-03-2014 14:42
11-03-2014 14:42
I cannot seem to find the correct setup for my SSL cert on MS Azure Websites that will make Subscriptions function correctly. I can authenticate just fine (oauth) and http (non-ssl) subscriptions work fine.
However, when I enable https, I get the following:
When I try the free, built-in cert for https://mywebsite.azurewebsites.net (SSL Cert for *.azurewebsites.net), I get SSLPeerUnverifiedException.
When I try a GoDaddy SHA-2 SSL cert, I get SSLException. I read in this forum there are known issues with GoDaddy's SHA-2 certs, so I switched to Starfield SHA-2. I also get an SSLException.
I see that GoDaddy also offers SHA-1, but I have not tried that yet.
In Azure websites, there are SNI and IP based SSL bindings. I tried both, neither work. I have read that SNI is not supported, so that is not a surprise.
Any ideas?
Best Answer11-03-2014 18:26
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
11-03-2014 18:26
What's your app's URL?
Best Answer11-03-2014 18:36
11-03-2014 18:36
Best Answer11-04-2014 02:09
11-04-2014 02:09
Just to document the current setup (I've switched things around many times in the past couple days):
- Azure Website
- GoDaddy SSL Cert, using Starfield SHA-2 algorithm
- IP Based SSL binding for fxwell.com and www.fxwell.com (not using SNI SSL right now)
- "A name" record setup using dedicated IP
- https://fxwell.azurewebsites.net uses the Azure wildcard cert
- Current Error (from fibit subscriber report): SSLPeerUnverifiedException
I am able to authenticate and pull data manually. Problem is only with webhooks.
Best Answer11-05-2014 02:55
11-05-2014 02:55
Any advice from Fitbit? I have tested the site and ssl cert with about 10 different SSL checkers....all passed.
Best Answer