#vladislavmarinov_webhooks

1 messages ¡ Page 1 of 1 (latest)

pliant daggerBOT
#

👋 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/1251249723797671989

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

toxic pivot
light widget
#

I tried with all domains and all ips - nothing allowed the request

toxic pivot
#

Can you share the event id that was rejected? It should start with evt_123

light widget
#

evt_1PRUj7IOw5UGbAo18hdz03HB

#

most resent one

#

it is blocked by my API because the origin is not in the list

toxic pivot
#

As long as you've allowed these ips: https://docs.stripe.com/ips#webhook-notifications you should recieve these events. I'm afraid the response from that event is sent by you, "Forbidden: Access is denied" and it appears that we're able to reach your server.

light widget
#

what is the origin of the request

toxic pivot
light widget
#

10.244.1.17 that is the ip of the webhook request

#

it does not figure in

#

mb the connecting ip is 54.187.174.169

toxic pivot
#

Yeah, it all looks like you need to handle this on your end and respond with 200 instead of blocking the events.

light widget
#

i fixed it - you should mention to look for do-connecting-ip

#

not normal ip

#

its confusing a bit in my opinion

#

thank you for the help anyway