#Mackan-webhook
1 messages · Page 1 of 1 (latest)
Yup! One sec, lemme just find it
Right, the ID in the dash is evt_1Jf4eeK5jxshYNYAHl1PNS2o, and according to the dash, it hasn't even tried sending to my webhook
Thank you
Does the fact that I'm using the CLI to forward events matter?
I am a bit confused because on one screen I see that it says we successfully sent that webhook but from another view I see what I think you are seeing where it says "No recent webhook attempts"
Is the CLI reacting at all here?
It should be able to work for this
It is, but not to the checkout event
Bottom left is stripe forward, bottom right is stripe listen
@sick slate the Stripe CLI can be a bit finicky with some events. Does it happen even after a restart of the CLI entirely?
As in ctrl-c and starting it again?
yes
Can you share more details? How did you start the cli/forward, what exact command and what's your current config?
Command is stripe listen --forward-to localhost:3001/hook/stripe
try restarting with --verbose
stripe config --list shows the following (With keys redacted by me, can't go sharing those :P)
color = ""
[default]
account_id = "acct_1..."
device_name = "MacBook-Pro-som-tillhor-Max.local"
display_name = "discorddungeons.me"
live_mode_api_key = "rk_live_..."
live_mode_publishable_key = "pk_live_..."
test_mode_api_key = "rk_test_..."
test_mode_publishable_key = "pk_test_..."
and then try doing 2/3 sessions in a row and then share the info
hum sorry, try without it for now and do 2/3 sessions in a row
Aight, checkout sessions?
Triggered the checkout.session.completed event with stripe trigger 3 times, still not receiving the event.
All other events that triggered are here though
Oh! I tried using the --latest flag according to https://github.com/stripe/stripe-cli/issues/600#issuecomment-789890143 and it worked!
Was I somehow running an old api version or something?
hum --latest shouldn't matter
but yes you are on an old API version today (2017-04-06)
I see, how come? Is it because my live mode isn't using the latest yet?
it's just a default API version set globally on your account, likely because you have a really old integration from years ago
@sick slate are you unblocked overall?
Aye! I'm good now, ty!