#natshirts-cli-listen-webhooks

1 messages ยท Page 1 of 1 (latest)

daring basalt
snow dawn
#

hope you wont bite me :p

weary wyvern
#

Haha, we definitely won't!

#

Could you elaborate a bit on what you're referring to when you mention sending events from the dashboard?

snow dawn
#

well i will reformulate all my question as i was a bit confused myself.
I can see that my application (including my webhook) works well in localhost while i forward the events to my localhost.
But when i test my application in a remote server, the webhook return always 400 bad request foreach events send.
I don't find why, as my code is working fine in localhost

weary wyvern
#

Just to make sure I understand, you were working on local host and your integration was working as expected. You then moved the project to a remote server, configured a new webhook endpoint for that, and now all the calls we're making to that endpoint are receiving a 400 response?

snow dawn
#

yes that's it

weary wyvern
#

Do you have the id for that webhook endpoint, should be a string that starts with 'we_'?

daring basalt
#

(deleted secret)

weary wyvern
#

Sorry about that, that was the webhook secret rather than the id for the webhook endpoint. We've deleted the message accordingly and encourage you to cycle the secret.

snow dawn
#

ah my bad : we_1JcRn6AEt55jQS9fjJF8i2Y6

weary wyvern
#

Thanks! Please bear with me while I see what I can find for that endpoint.

snow dawn
#

thanks

weary wyvern
#

Thanks for your patience, still checking.

#

I'm not seeing anything definitive from our end ๐Ÿ˜ฆ it looks like we're getting a 400 back from your server without any additional information to work with. I'd recommend trying to debug on the remote server if possible. If your codebase is the same on that server as on your local machine then there may be some environmental configuration to take into account.

If you could add additional logging into your server that may help give us some more insight. You could also try returning a 200 without doing any processing on your end to confirm that the communications are flowing as expected.

snow dawn
#

ok, yes i am adding some additionnal logging into my server to see what's going on. thanks anyway for the help. ๐Ÿ™‚

snow dawn
#

hey, i have the following message in my logs : "2021-09-22 17:20:55.3531|0|INFO|Backend.Controllers.StripeWebhookController|The signature for the webhook is not present in the Stripe-Signature header. |url: http://51.178.48.171/api/StripeWebhook"

#

@weary wyvern ๐Ÿ™‚

#

there should be one no ?

daring basalt
#

signature verification is a bit delicate -- you need to make sure you're access the request raw body, and the correct signing secret for the configured endpoint

#

if you just created an endpoint or rolled the signing secret, make sure you update the whsec_123 secret in your code too

snow dawn
#

oh f**k me, i missed to update my secret for this webhook endpoint. thx for the hint