Webhook Endpoint Error Email from Stripe

Hi @heartharmony,

Initially it sounds like the URL found via WooCommerce > Settings > Payments > Stripe > Webhook Endpoints you’ve added to Stripe via https://dashboard.stripe.com/account/webhooks may possibly not match this screen from your Stripe settings exactly:

Image Link: https://cloudup.com/c1rwp3fhOKN

Can you please double-check that those match to be sure? We’ve also sometimes seen certain plugins like security plugins preventing webhooks from working as expected too!

Same issue here, everything was working fine and stopped working since the last update. I’ve double checked (even deleted and re-added the webhook) and the issue persists.

I just want to say I’m having the same issue as well. I did start a new post myself before this one was made, but I want bump this thread as well as I think this issue is affecting many users.

I deleted and re-added the webhook (which had been working perfectly fine for a year before the 2nd December), and there was no change.

If it helps, we use the paid version of Wordfence on the site.

Hey @heartharmony,

Do you notice any change if you temporarily deactivate WordFence on your site as when cross-testing today for us I’ve not personally been able to replicate the behaviour as yet on my test installs using the latest version of Stripe which is rather frustrating?

@squaredpx @davemclean Thanks for contributing to the conversation and if you revert to the previous version of Stripe does the behaviour persist for either of you?

https://github.com/woocommerce/woocommerce-gateway-stripe/releases

Note: There was also another topic related to this from @davemclean which I’ve set to resolved so we can all communicate within this one to save any duplicate replies.

Thanks

Hey Stuart

Stripe had deactivated the webhook endpoint on the account due to repeated failures, so I re-enabled it prior to testing.

The message we received on the deactivation was:

“Here is the summary of errors we have received when sending you webhooks:
* 43 requests returned HTTP 503, which is an indicator of a server error on your end.”

I deactivated Wordfence and then tested re-sending a few of the failed webhook attempts. This time they showed as succeeded on the Stripe dashboard webhook attempts log.

However, when I refreshed the Stripe dashboard page, they went back to displaying as failed.

If I tried resending the attempt again, then the ones that previously showed as succeeded when resent re-appeared as successful, but then revert back to failed when the page is refreshed and the webhook attempts log filtered.

Anything else I should test?

Thanks for doing those tests – it can take a few minutes for the webhooks to update.

From here, I’m wondering about two different things:

1. Is any information showing up in the Stripe log?

Please make sure logging is enabled under WooCommerce > Settings > Payment > Stripe and then try resending the webhooks. Check to see if anything shows up under WooCommerce > Status > Logs, selecting the Stripe log from the dropdown in the top right.

2. Could this be a plugin conflict?

You mentioned that things worked (briefly) when you disabled WordFence. I’m wondering if there are other plugins that might be interfering. It’s worth ruling out as a potential cause. You can find a more detailed explanation on how to do a conflict test here.

Please do let us know how those tests go!

Solved it.

The site had been getting spammed silly via the contact form and Recaptcha3 was making no difference, so with Wordfence Pro we had tweaked the settings to block access not only to the login form but the whole site for certain countries. This must have included the country where Stripe’s servers were located, triggering the webhook issue, and the hosting server cache was adding to the woes.

Glad to have this bit resolved at least – now to find an alternative for the spam issue.

Hey there,

I’m so glad to hear you found it – thanks for letting us know, as well as what the solution was!

Thanks for your info Ingrid. I’ll try to look at it as we aren’t using Wordfence. I’ve downgraded to the previous plugin release but the issue persist.

Deleting and re-adding the webhook secret key seems to work, ?I’ve just done it and for now it’s working. Thanks for the support.