#oops365

1 messages · Page 1 of 1 (latest)

round abyssBOT
daring cloud
#

If you print all the headers, do you see Stripe-Signature at all?

brisk eagle
#

I have the logs printing what I believe is the correct header, judging from the docs:
t=1701247401,v1=4509...4ff,v0=e40...a92

#

(printout of the signatureHeader variable from the code above)

brisk eagle
# daring cloud If you print all the headers, do you see `Stripe-Signature` at all?

actual log looks like this

2023-11-29 02:43:21.412 CST
Stripe Error: The expected signature was not found in the Stripe-Signature header. Make sure you're using the correct webhook secret (whsec_) and confirm the incoming request came from Stripe.
2023-11-29 02:43:21.412 CST
whsec_dm8...Yx
2023-11-29 02:43:21.412 CST
      
2023-11-29 02:43:21.412 CST
SigSecret: t=1701247401,v1=4509..84ff,v0=e40b..7a92 End Sig

Ellipses added by me

round abyssBOT
brisk eagle
thin steppe
#

Hi! I'm taking over this thread.

#

First, can you triple check that you are using the correct whsec_xxx?

brisk eagle
#

is it okay to do that in here

#

or in a dm?

thin steppe
brisk eagle
#

Ah, if it's not a security issue here is fine

#

acct_1LuRtRLFVWaHr9FE

#

And yeah I have the right secret printing out

#

It's quite a bit shorter than the CLI secret I noticed

#

but the printout matches the text when I click Reveal under Signing secret

thin steppe
#

Are you using the CLI for testing? Then are you using the whsec_xxx that is printed in the CLI (and not the one in your dashboard)?

brisk eagle
#

We'd previously used the CLI for testing, but that's a different secret

#

the dashboard secret, which we're using, and which shows up on the logs is ~38chars long, while the CLI secret was ~70 chars long, if that helps

thin steppe
#

yes, all of that sounds correct.

brisk eagle
#

the one that adds the var stripeEvent = EventUtility.ParseEvent(json);? I actually did have when I was first troubleshooting the error

#

I removed it during troubleshooting though