- This topic has 4 replies, 4 voices, and was last updated 5 years, 7 months ago by .
Viewing 5 posts - 1 through 5 (of 5 total)
Viewing 5 posts - 1 through 5 (of 5 total)
- You must be logged in to reply to this topic.
Stripe payment plugins for your WordPress site
· ·
Home › Forums › Stripe Payments Plugin › Stripe Subs Webhooks configuration error
Tagged: stripe, Subscriptions, webhooks
Hi there
Occasionally I am getting errors saying:
Stripe Payments Subscriptions Addon: webhooks seem to be not configured properly. Please go to settings page to configure them.
When I go to the settings page, the webhooks status loads and then appear fine (A message says webhooks exist) – the error message then disappears.
I have tried deleting webhooks and clearing the cache but the error notice persists.
Will this interfere with subscription plans being made?
Is there a reason this is happening?
Thanks
G
Hi.
It might be a bug in the webhook check cron job.
I will test this and get back to you.
To answer your question: no, it shouldn’t interfere neither with existing payments nor with future payments.
Good Morning,
I have the same problem
Hi.
It was fixed the same day I replied to the message. It was a bug in webhook check, which displayed error message regardless if webhooks are ok or not.
Please update Subscriptions addon to the latest version.
Hey guys,
I see this as marked resolved, but I just recently purchased this plugin (a few days ago) and after getting all our stripe keys set up and keys for the webhooks, I’m getting this message:
“Stripe Payments Subscriptions Addon: webhooks seem to be not configured properly. Please go to settings page to configure them.”
On the subscriptions tab the web hooks status on both live and test is just saying “checking…” and nothing else. I have triple checked the signing secrets for the webhooks as well as the pk/sk live and test keys. The debug log is telling me nothing and when I made test calls from Stripe, the logs said that the process completed successfully. I checked for updates this morning and there was one available, so I updated the plugin and still have the same issue.
Plugin version I have: Version 1.4.7
If anyone has any suggestions, I’m all ears. Thank you for your time
~J