#LucasIsola - SSL Protocol Error

1 messages · Page 1 of 1 (latest)

stray cloak
#

Interesting. What call exactly is the console making when it sees that error?

#

Adding your other messages for context:

Has anyone seen this before?
For clarity, another workstation on the same network can call out to a different P400 reader.

untold bronze
#

It actually seems like a perfectly normal call and the reader's local IP matches that domain name.

#

The only theory I have at the moment is the business router has an IP Address Reservation for the reader's MAC address and the reader is using an IP that mismatches that reservation

stray cloak
#

Thanks for the clarification. Is that coming from some Stripe API call in your code? I am looking in to this but I am not immediately familiar with when that POST request is made

untold bronze
#

From the Stripe Terminal SDK

#

It handles that POST on its own. Normal behavior but I cannot find the root cause for this SSL error. Normally if the reader can't be reached it says name not resolved.

wild siren
#

👋 @untold bronze not sure for now but I asked my team internally

#

Are you doing this in Chrome? Does it happen in another browser?

untold bronze
#

Chrome and Edge. Same result. Some fun stuff we tried:

#
  1. Check time zone. It's synced with a time server.
  2. Flush DNS cache
  3. change to Stripe recommended 1.1.1.1 and 1.0.0.1 DNS servers.
  4. Reset browser completely
#

Nothing seemed to work and we're pretty savvy on my team with these issues because we've run into almost every permutation. This one has stumped my whole team.

#

@wild siren Thanks for checking in

wild siren
#

What operating system are you on and what exact version?

#

(sometimes it's a problem with the OS being old and not trusting the root certificate)

untold bronze
#

Hmmm. Interesting suggestion that I hadn't thought of. We were on live-screenshare with the business for an hour and change. We just hopped off. But we're scheduled to chat with them again tomorrow or Monday. I will add this to my list. That theory holds water though because via NSLOOKUP the computer reaches the reader.

wild siren
#

basically we had a user hit the same thing and they were on Mac is 10.11.6 which is El Capitan and they couldn't trust the cert

untold bronze
#

Ahhh. Good share. But they're on a version Past XP. The doc states "Windows >= XP SP3". I think this is ruled out.

wild siren
#

ah so they are on Windows?

untold bronze
#

Yeah yeah.

#

I failed to take note of Windows version but this is a business with 5 point-of-sale windows stations. Station 1 dubbed "POS 1" successfully talks to one of the P400's. All 4 P400's share the same SW version and all 4 appear online in Stripe. We tried POS 2 and POS 3. Both have the same SSL protocol error in the Chrome console.

#

But all Windows PC's are using the Stripe-recommended 1.1.1.1 and 1.0.0.1 for DNS servers.

#

Sorry. I'll add some clarity. "successfully talks" = starts a new payment intent and the reader requests SWIPE, INSERT, TAP.

wild siren