Cert problem

[wmohanlon]

Certificates for internal fitbit sites have an issue.  Perhaps they expired?  I didn't dig hard enough to see if it was the Lets Encrypt issues from earlier this month.  Once I discovered that https websocket connections were failing, I lost interest in chasing the problem further.

This is causing problems connecting to the developer portal, along with issues with connecting to Pandora

https://https://035-v3-client.fitbit.com/

Someone could be trying to impersonate the site and you should not continue.

Websites prove their identity via certificates. Firefox does not trust 035-v3-client.fitbit.com because its certificate issuer is unknown, the certificate is self-signed, or the server is not sending the correct intermediate certificates.

Error code: SEC_ERROR_UNKNOWN_ISSUER

View Certificate

[wmohanlon]

Oops

https://035-v3-client.fitbit.com/

[wmohanlon]

Thought about it more, and I suppose the chain could be self-signed on purpose?  Cert chain might be OK from the perspective of my watch, then.

[alexanderrr15]

Apple neither trusts the cert either, check in the details for more information 

[JonFitbit]

That domain in theory is a non-public one using our own root CA. I don't think that is related to your specific issue.

[wmohanlon]

Thanks, that makes sense.

The confusing part is that I've got both a Versa 2 and a Versa.  The Versa 2 is new, and I cannot get it to connect to the developer portal without throwing the "Connection error 1006".  I switched back to the Versa, and it can still connect to the portal just fine.

I can see that it is connecting to that 035-v3-client.fitbit.com host briefly multiple times before it throws the 1006 error. 

[Guy_]

Possibly the certificate expired.

Also suddenly getting cookie requests in browsers, so something changed.

See post on SSL perhaps related.