Hi @shanodesign,
There are several cases of the same issues, WordPress 6.4 has this annotation “Your customer cannot use Stripe at checkout because we could not connect to your account. Please go to Settings and set up a Stripe account key.” And the backend of the site is very slow. One action takes a long time. I’m currently downgrading WordPress as a workaround.
From what I understand, you’re experiencing issues with the WooCommerce Stripe Payment Gateway plugin following the WordPress 6.4 update. Specifically, you’re seeing an error message stating, “Your customer cannot use Stripe at checkout because we could not connect to your account. Please go to Settings and set up a Stripe account key,” and you’re also noticing a significant slowdown in the backend of your site.
We’re sorry to hear about the inconvenience this has caused. We’ve noticed similar reports from other users experiencing potential Stripe API, WP-Admin, and performance issues after the WP 6.4 update. Our team is aware of this issue and is currently working diligently to find a solution. 👉 WP 6.4 update causing potential Stripe API, WP-Admin, and performance issues.
In the meantime, as a workaround, you might consider reverting your WordPress to a previous version. This could potentially resolve the issue temporarily until we provide a fix. You can do this by using plugins such as 👉 WP Rollback or Rollback Auto Update.
📌 Quick heads-up: It’s really important to backup your full site and database before making any changes. This will ensure that if anything goes wrong, you can easily restore your site to its previous, working state.
Again, we apologize for the inconvenience and appreciate your patience as we work to resolve this issue. We will keep you updated on our progress.
Official woo authorize.net plugin is experiencing the same issues – timeouts – so we’re going to go back a version in WP.
Thank you @britonleap,
The issue appears to have been resolved with the released 6.4.1 update.
Hi @shanodesign and @britonleap
We are aware of this as it is a known issue with WordPress 6.4, particularly when invoking cURL. However, the WordPress core team resolved the problem in the newest version, WordPress 6.4.1, and everything appears to be working properly based on user reports.
To fix your problem, we recommend updating WordPress to version 6.4.1.
Meanwhile, I’ll mark the thread as solved for now, but feel free to open a new one if you have any other questions.
Thanks!
Hi @shameemreza,
Thank you for the great news.
I was relieved!