#hoffemberg_api
brazen muralBOT
halcyon knollBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- hoffemberg_java-webhook-handler, 1 hour ago, 21 messages
- hoffemberg_api, 3 days ago, 28 messages
brazen muralBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1252327205472571484
đ Have more to share? Add details, code, screenshots, videos, etc. below.
woeful sparrow
We can't really help with diagnosing these errors. They occur on your server and we have no visibility into that unfortunately
acoustic spear
Okay. One of the problems I'm having is that when I trigger an event and then look in the dashboard, I can see the event in the Events tab but when I look in the Webhooks tab it's not showing up so I can't see what additional information there is for the error.
woeful sparrow
You'll need the webhook enpoint to be active in order to see webhook attempts to it. Currently it looks like your webhook endpoint has been disconnected
acoustic spear
Don't understand that. On my end I can still trigger events in one terminal window and then see the response in the 'listening' window.
woeful sparrow
What's the output of the listener when you trigger an event?
acoustic spear
Well, it changed while I was talking to you. Before I was always getting the 403. Now I'm getting [ERROR] Failed to POST: Post "http://local.fundycentral.com:8080/client-order/stripe-webhook": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
It's a different error, so at least that something, though I don't know what I did to "fix" it.
woeful sparrow
It sounds like your server isn't responding. You need to make sure your server is running and your server's webhook handler code is sending back a HTTP 200
brazen muralBOT
acoustic spear
It responds when I hit it with Postman (though I'm getting a 500) but it's back to the 403 when I hit it with stripe trigger payment_intent.succeeded
woeful sparrow
Yeah, it sounds like your webhook handler is misconfigured. Or your server is. We can't really troubleshoot that with you unfortunately. You're going to need to dig into that on your own.