#.letscode
1 messages · Page 1 of 1 (latest)
anything i missed?
Hi there. Did everything work when you were testing with the same code in test mode?
Or did you just start in prod?
yes same code with different webhook id and url (dev server)
can i provide subscription id or signature,
?
Don't provide signature
Can you send the event id of the event that got the above error?
sure
evt_1NYVHVFG3Dh3H5V4t8tUfia4
can you please take high priority as it's in production? Sorry to bother
Looking now
@torn breach any update?
Discord is busy, so I'll get to you when I can
There's no response body for the request we made to your endpoint
Can you paste the exact error you saw in your server logs?
No signatures found matching the expected signature for payload
this is message i'm reciving in code
code block to print error
let me know if any changes need to get more details
And you confirmed the webhook signing secret you're using matches the LIVE mode one from the dashboard by printing it out in that block?
these two i'm printin
signature header printing long and ( t=1690472055,v1=cacd073d1************************23b3a765)
it matching with code and dashboard
Don't paste the endpoint secret, but does that match as well?
yes.. it's partial end point and matching with code and webhook
Can you check that there's no whitespace in the secret (like a trailing or leading space or some character)?
That's a common cause for signature verification errors
hope this is the right way to verify in code
event = Webhook.constructEvent(payload, sigHeader, endpointSecret);
verified space also, not found in keys
what are the alternative ways to verify this issue?
👋 hopping in here to help out
There isn't really a way to roll the webhook endpoint keys, so ifyou want to ttry changing keys you'd have to create a new endpoint in the dashboard
I have a couple of questions - did you confirm that the raw payload looks correct (when you log payload)
yes
and do you have an event ID I can take a look at (just want to see if I can see anything)
evt_1NYVHVFG3Dh3H5V4OZj9ddWw
Are you 100% sure this is failing at signature verification? Is it possible it's throwing the error after signature verification passes?
Aha, that would definitely do it