Stripe Test Integration
I get the following response from the command line after authenticating with stripe CLI and didn't get the webhook signing secret: "Waiting for confirmation...No directory provided for file keyring"
7 Replies
Hi @jnrzxc. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Hmm, I don't know enough to give you a confident answer yet. However, based on the knowledge sources provided, it's important to ensure that you have followed all the directions in the guide and have the Stripe CLI running when testing. You can refer to this guide for Stripe testing: https://docs.opensaas.sh/guides/stripe-testing/
Also, if you're working with webhooks, you might need to set your webhook endpoint to your server domain in the Stripe Dashboard. It should look something like {your-fly-server-domain}/stripe-webhook. You can refer to Stripe's documentation on testing webhooks: https://stripe.com/docs/webhooks#test-webhook
If you're still encountering issues, it might be helpful to check your API version numbers or your webhook secret settings.
Remember, this advice is based on the information provided in the knowledge sources and might not directly solve your issue. For more specific help, consider reaching out to the Stripe support or community forums.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @jnrzxc, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
You can also find the webhook signing secret in your stripe dashboard > developer > webhooks, but It seems like the log in didn’t work correctly. I would do a google search for that specific error as it relates to stripe.
Yeah this sounds specific to your machine / OS / local setup! Now why would Stripe login produce that error on your machine, it is hard to say. Are you running it in some kind of peculiar setup?
After searching for solutions for this problem i finally found the answer. I'm using WSL and it seems that for this problem to be fixed i have to run this command with sudo:
You may refer to this thread: https://github.com/stripe/stripe-cli/issues/933
Oh wow! @Vinny (@Wasp) is this common enough so that we should be putting it in our docs?
Yeah for WSL users we should add a note for this
created a quick PR for it: https://github.com/wasp-lang/open-saas/pull/191
GitHub
Add note on
sudo for Stripe CLI by vincanger · Pull Request #191...A user on WSL encountered errors running the Stripe CLI: https://discord.com/channels/686873244791210014/1253545019785351180/1253951893877817527
The workaround was to append sudo to the commands as...