Ionic Wallet Setup Failure on Android, SSL Error 1407742E

[SteveMcFly]

Trying to set up the wallet. After reading this: https://community.fitbit.com/t5/Ionic/Wallet-setup-error/m-p/2386501#M23261

And checking this: https://help.fitbit.com/articles/en_US/Help_article/2236

I ran into a repeatable problem, where I get an SSL protocol error caught by the fitbit app. Preceding messagebox says "setting up your wallet". Rebooted both Ionic & Android, and repeated with same results.

I have a supported credit card, but never made it to CC # entry. Whazat?

p.s. the bluetooth sync is pretty dodgy compared to the Alta HR and Flex2. Seems like I only slept 3.5 hoours last night on Ionic, AltaHR normally reads me at 7.5. Swimming on Ionic is dead-set accurate lap recognition. Wallet failure is a deal-breaker, I can cope with 5 retries to sync.

[USAF-Larry]

@SteveMcFly, this would appear to be a WiFi problem with the Ionic.  Is there a firewall on your network that prevents connection to servers by the Ionic?

[SteveMcFly]

Thank you for your response @USAF-Larry 🙂

Just to test your theory, I unplugged the LAN cable from my computer, and used wifi to access a random secure site. My computer uses the same wifi SSID and routers that I connected the fitbit (and Android device) to. I had no issue connecting to an HTTPS site, or other sites for that matter.

For the wider community's info (from wikipedia):


"HTTPS uses a default port number of 443 (80 for HTTP) and that HTTPS automatically performs SSL negotiation and thus always sends data in encrypted form, i.e. web servers accessed through https:// have to be "secure web servers". The 443 is the default TCP port used for HTTPS."

So my routers are clear for connections through to the Internet on port 443.

However, I'm not even sure that the Ionic itself is the device trying to connect to the servers. That may in fact be my Android device.

I turned off wifi on the Android device. Doing the same action to set up the wallet in the fitbit app, I got an error associated with DNS: Unable to resolve host: "des.payables.co".

I tried to access https://des.payables.co/ from my web browser, and got an error 401, which may or may not be related.

This means (from wikipedia):


401 Unauthorized (RFC 7235)

Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication.[34] 401 semantically means "unauthenticated",[35] i.e. the user does not have the necessary credentials.

Note: Some sites issue HTTP 401 when an IP address is banned from the website (usually the website domain) and that specific address is refused permission to access a website.

Now, the info from the error message on the fitbit app suggests that the Android app is having trouble connecting in the initial SSL handshake exchange, with an error around the version support. Could be the fitbit app, my Android SSL library (though I can't change that!), or could be the server.

Whazat, fitbit devops?