- This topic has 19 replies, 3 voices, and was last updated 4 years, 2 months ago by
.
-
Posts
-
I have 2 identical subscription plans but one is in Test mode and the other is in Live mode. I had used the Test plan back when I was building and testing everything. Once we launched, I turned on Live in General Settings and all the actual subscriptions indicated that they were made for the Live version of the plan. So I think I did everything right when I set this up initially (months ago).
When I did my test webhook earlier today, I did forget to uncheck Live mode in the plugin General Settings before doing it, so I guess that would account for the subscription not found error.
But just now, I DID go in and uncheck Live in the General Settings (so it should be in Test mode) and ran the test webhook again but I still get the same results:
[08/29/2020 1:45:13 AM] – [Sub] Webhook signature successfully checked.
[08/29/2020 1:45:13 AM] – [Sub] Processing “customer.subscription.updated” hook.
[08/29/2020 1:45:13 AM] – [Sub] Searching for subscription sub_00000000000000
[08/29/2020 1:45:13 AM] – [Sub] FAILURE: Subscription not found. Aborting.How can I know the live webhook is going to work with the live subscription plan when the plugin is in Live mode?
Also, why did the webhooks stop working even though the plugin was showing me green check marks like everything was happy?
I want to feel confident that when we relaunch this program this fall that webhooks will be working and customers will not get charged more times than the plan said they should.
I’m not sure why the webhooks weren’t working. Perhaps you changed API keys after webhooks were created? Or changed signing secrets in the settings. It would show error in the log though if you did. We never had such situation in the past. Few other issues related to webhooks that our customers had were caused either by their server config that was blocking webhooks from Stripe or by improper manually configured webhooks (when those were created via Stripe Dashboard by the customer instead of using “Create Webhook” buttons on add-on settings page).
Create a plan in test mode in the plugin, but make it “daily for 3 days” instead of monthly. Then create a product with this test plan and make a test purchase using one of these test cards: https://stripe.com/docs/testing#cards. It should automatically “end” itself in 3 days, you can see that by watching the subscription on Subscriptions page of the plugin.
If test mode webhooks are working, then, most likely, Live webhooks would be working as well. When you have a first live purchase, just find the subscription on Subscriptions page of the plugin and see if events are properly populated (e.g. “regular payment made” should be right after “subscription created” event). Just look how it goes with your daily test plan, same events should be there for your live plan (except that it would happen monthly, not daily).
Thank you. I don’t think I changed API Keys or Signing Secrets. However, it is entirely possible that I created the Webhooks on Stripe rather than using the button in the plugin. I don’t recall for sure because it’s been awhile since I set this up, but as I have experience creating webhooks in Stripe for other things (that don’t have such a button) it’s very possible I did it that way.
We are migrating the site to a new server next week. I think I will complete that move before doing the further testing you’ve suggested as then I can also make sure everything is working well on the new server.
If we can keep this topic open for now, I should be able to get back in a week or so with the (hopefully successful) outcome!
Thank you again. Your support has been really good!
Hi! Just checking back in to say that we completed the migration to the new server last week and then this week I did the 3 day test subscription as you suggested and everything worked perfectly. After 3 payments, the plugin backend says Subscription Ended. So I think we are back on track. Thank you for all your very patient and helpful assistance with this issue!
- You must be logged in to reply to this topic.