#brdata_unexpected
vestal birchBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1496220586542891058
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
crude swift
This has been working fine for the last year. We havent made any recent changes at all.
All the sudden stopped working at 12am last night
thin cobalt
Hello, can you send me the ID of an event (evt_123) that your endpoint didn't receive?
thin cobalt
That is, though I am not seeing an event with that ID. Can you double check to see if any characters were cut off?
If you can send me your account ID (acct_123) or the webhook endpoint ID (we_123) that would also work here.
Webhook endpoints can be found here: https://dashboard.stripe.com/workbench/webhooks
Account IDs can be found towards the bottom of this page: http://dashboard.stripe.com/settings/user
crude swift
evt_3TOgMIEFStFkSVDP1QDCIWqI
There that should work!
Let me know if it does
acct_1NL3nhEFStFkSVDP
thin cobalt
That event ID does work for me! I can see that we tried to send that event to your endpoint three times but there was a TLS error. I think we should show those attempts on your dashboard page:
https://dashboard.stripe.com/acct_1NL3nhEFStFkSVDP/events/evt_3TOgMIEFStFkSVDP1QDCIWqI
Trying to find more detail or what that means you should change
crude swift
What protocol is used for this?
thin cobalt
My understanding is that TLS is a part of the initial handshake to start the HTTPS connection
If you enter the domain name into this tool it can show you the issues with your certificate:
https://www.ssllabs.com/ssltest/analyze.html
thin cobalt
Yep, it looks like the issue is higher up on that page, it mentions your certificate change is incomplete
crude swift
What protocol does stripe use to send the webhook?
thin cobalt
Ah gotcha, looking up the TLS version
So it looks like the incomplete chain is the issue
crude swift
Is there a way to try and send the webhook request again that has failed
It says it will auto do it in an hour
But can I force retry manually - I made a change and want to see if that fixed it
thin cobalt
Our CLI has a command for resending events. I thought there was a button on the dashboard page for doing it but I'm guessing that's not there.
https://docs.stripe.com/cli/events/resend
Testing to see if there is a good way to do this from the dashboard
In the "Deliveries to webhook endpoints" section there should be a "Resend" button that you can click
