tices-stripejs-tlserror | Stripe Developers | Page 1

flat hazelBOT Jan 4, 2023, 8:52 PM

#

grizzled pine Jan 4, 2023, 8:53 PM

#

Good question. Checking in to what might cause this

warm harness Jan 4, 2023, 8:53 PM

#

Thanks

grizzled pine Jan 4, 2023, 9:07 PM

#

Is there a public page where I could see this for myself? If so can you DM me a URL to that page?

warm harness Jan 4, 2023, 9:07 PM

#

Yeah, i'll send you the link. Odds are that you won't see the issue since it's only affecting a very small % of our users.

grizzled pine Jan 4, 2023, 9:09 PM

#

Much appreciated. And have you noticed any pattern to the browsers that see this or anything?

warm harness Jan 4, 2023, 9:10 PM

#

Yeah, Chrome and Safari on Mac.

#

Unfortunately, I don't know the versions, but i would assume fairly up to date.

grizzled pine Jan 4, 2023, 9:11 PM

#

Makes sense, thank you. I'm not seeing it, looking in to what has causes this error historically with stripe.js.

warm harness Jan 4, 2023, 9:12 PM

#

Thanks. Also, just a note that I've seen this happen on two different domains with slightly different stripe integrations.

grizzled pine Jan 4, 2023, 9:23 PM

#

Also quick question, when this happens does the Stripe code on your page not work for these users? Or does it work but also show this error?

warm harness Jan 4, 2023, 9:24 PM

#

It fails completely.

grizzled pine Jan 4, 2023, 9:36 PM

#

Gotcha, that is good to know. Unfortunately I am having trouble finding out what this means here. I am consulting my colleagues and will get back with what we can find

warm harness Jan 4, 2023, 9:36 PM

#

Sounds good. I have to step away for a bit but will check back here.

grizzled pine Jan 4, 2023, 9:38 PM

#

Thank you. Also quick question but do you know if this suddenly started happening recently or anything like that?

grizzled pine Jan 4, 2023, 9:56 PM

#

And going with your cache theory, do you know if the users' issues go away when they reload the cache?

limpid basin Jan 4, 2023, 10:03 PM

#

Jumping in: does it repeatedly fail for those customers? Or is it sporadic? Feels like a misconfiguration on their device not trusting certain certificates

warm harness Jan 4, 2023, 10:15 PM

#

Hey, the first report that we had of this was on Dec 19th. I don't know if the issue goes away on hard refresh or not, but using other devices does work. So it is local to the machine in some way. The issue is repeatable for the customers that receive this error.

limpid basin Jan 4, 2023, 10:27 PM

#

This can be super tricky to debug unfortunately and is quite technical. I've seen other developers mention this a handful of time in the past month but it's rare and we've never been able to get any kind of actionable information.

If you can get one of the affected customers to collaborate, I would ask them to visit https://js.stripe.com in the impacted browser, which should yield a TLS error page. I'd ask them to then click on the red "Not Secure" next to the address bar, then on the "Certificate is not valid" error in that menu, and then send you a screenshot of the "General" and "Details" tabs that pop up in the dialog box

#

Also ask them for their exact OS version and browser version + exact time on the device + timezone

#

tices-stripejs-tlserror

#

@warm harness you could also ask them if they see the same error on https://stripe.com as it's a different certificate and it would help narrow things down

warm harness Jan 4, 2023, 10:50 PM

#

Thanks. Sorry for the delayed response, I'm jumping in and out of meetings at the moment. I will see what I can do about getting the additional information. If I can get those details should I drop that info in this thread?

limpid basin Jan 4, 2023, 10:51 PM

#

the thread will be archived unfortunately but you can come back in #dev-help and mention the thread adn share the extra information. Feel free to @ me, if I'm not around someone on my team can find me

warm harness Jan 4, 2023, 10:51 PM

#

Sounds good.

limpid basin Jan 4, 2023, 10:52 PM

#

Sorry for the trouble, this has been quite elusive for us and we're hoping it's really rare and poorly configured devices but the more details you can find the easier it will be to narrow things down

warm harness Jan 4, 2023, 10:53 PM

#

Yeah, I can imagine. Thanks for helping me dig in.

#tices-stripejs-tlserror