Hi @bizmatebiz – This kind of problem is usually caused by either a conflict with your theme or with another plugin.
The best way to determine this is to:
- Temporarily switch your theme to Storefront
- Disable all plugins except for WooCommerce
- Repeat the action that is causing the problem
If you’re not seeing the same problem after completing the conflict test, then you know the problem was with the plugins and/or theme you deactivated. To figure out which plugin is causing the problem, reactivate your other plugins one by one, testing after each, until you find the one causing conflict. You can find a more detailed explanation on how to do a conflict test here.
– Joey
hi Joey
Thank you for the reply but a “Time out connecting to remote host” should not be an application error. It is like Stripe just cannot connect out from their server to reach my domain.
I have still investigated your suggestion. I disabled every plugin apart from Woo, its services and stripe. I also disabled the custom theme and activated storefront.
The error stays the same.
The Site Health plugin does not show any issue apart from the inactive plugins and themes warnings. Also my site does not use dropins.
I have asked Stripe to look into this as it looks more like a DNS issue they might have when connecting to my domain, and subdomains as i tested this with a staging environment. “Timed out connecting to remote host” is likely a TCP error. So I suspect their client does not even get a response back from my site as it cannot even connect.
However if in the meantime you have any further suggestion please let me know
Joey, just to follow up on another test i did.
I have seen some of the webhook notifications failing with errors 400.
Such as
2020-11-11T03:04:57+00:00 DEBUG
====Stripe Version: 4.5.3====
====Start Log====
Incoming webhook failed validation: {
“id”: “evt_1Hm6oe…….a”,
But these are indeed returning error 400 to Stripe. In case of time outs from stripe I do not see any request logs under woocommerce logs
/wp-admin/admin.php?page=wc-status&tab=logs
i hope they can figure out if the problem is on their end.
Hey @bizmatebiz,
Have you tried setting up the webhook again over on your Stripe account to make sure that’s all present and correct with Receive All Events having been selected? Also, make sure the webhook URL which you’ve added to your Stripe Dashboard > Webhooks is HTTPS and not HTTP and your website domain is also using HTTPS too.
https://docs.woocommerce.com/document/stripe/#webhooks
Also if you add this ?wc-api=wc_stripe to the end of your domain name sites domain name and click the link you should see a -1 which would indicate your webhook URL from WooCommerce is reachable.
Image Link: https://cloudup.com/cafKAtLvgFM
In relation to webhook validation failing Stripe details this information below with regards to that.
https://stripe.com/docs/webhooks/best-practices
Receive events with an HTTPS server
If you use an HTTPS URL for your webhook endpoint, Stripe will validate that the connection to your server is secure before sending your webhook data. For this to work, your server must be correctly configured to support HTTPS with a valid server certificate.
It might be worth checking your SSL certificate is configured correctly and working as intended too.
We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.
