Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WP 6.4 update causing potential Stripe API, WP-Admin, and performance issues #2751

Closed
wpniall opened this issue Nov 8, 2023 · 22 comments
Closed

Comments

@wpniall
Copy link

wpniall commented Nov 8, 2023

Describe the bug
After the WP 6.4 update, several people have reported issues with the Stripe plugin:

Live mode:

Your customers cannot use Stripe on checkout, because we couldn’t connect to your account. Please go to your settings and, set your Stripe account keys.

Test mode:

There was a problem connecting to the Stripe API endpoint.

The backend also slows down and some merchants can't even access the WP-Admin. Downgrading WordPress solves the issue.

To Reproduce
Steps to reproduce the behavior:

  1. Update WordPress to v6.4
  2. Error appears either in live or test mode

Note: It's yet unclear what's causing the issue but several people have the same issue and a few said conflict testing didn't help. Myself and a few colleagues are unable to replicate the issue (all on different hosting platforms).

Expected behavior
Existing Stripe keys should work after updating to WP 6.4

Screenshots
N/A

Environment (please complete the following information):

  • WordPress Version
  • WooCommerce Version
  • Stripe Plugin Version
  • Browser [e.g. chrome, safari] and Version
  • Any other plugins installed

Additional context
N/A

@wpniall wpniall changed the title WP 6.4 update causing potential API connections, WP-Admin, and performance issues WP 6.4 update causing potential Stripe API, WP-Admin, and performance issues Nov 8, 2023
@mustardBees
Copy link

We're seeing this too on a client site. A quick look with Query Monitor, there is a ~70s HTTP call which appears to be related.

@shameemreza
Copy link

@shameemreza
Copy link

Another report here: https://wordpress.org/support/topic/plugin-causing-error-wp-admin

7278707-zen

Side note: A user claimed that after manually disabling the Stripe plugin, they were able to access the dashboard.

@rob-vandenberg
Copy link

Same problem here. Site became extremely slow after upgrade to 6.4.
Disabling the Stripe Gateway plugin makes the site fast again.
Enabling it and it is slow again.

Not saying it’s a bug in the plugin, after all it was working fine before the upgrade to 6.4, but there is definately a compatibility issue between the plugin and WP 6.4.

@faroutride
Copy link

I'm having the same issues after upgrade to WP 6.4.

  1. "Your customers cannot use Stripe on checkout, because we couldn’t connect to your account. Please go to your settings and, set your Stripe account keys".
  2. Backend extremely slow.

Deactivating the plugin solves the issue.

@shameemreza
Copy link

@74MR47
Copy link

74MR47 commented Nov 8, 2023

Another report:

ZD: 7279156

Forum Thread: 👉 Activating Apple pay crashes last WP

@survivalrealty
Copy link

survivalrealty commented Nov 8, 2023

Screen Shot 2023-11-08 at 10 13 23 AM Experiencing similar issue. WP backend has been extremely laggy, occasional server errors, and getting:

Your customers cannot use Stripe on checkout, because we couldn't connect to your account. Please go to your settings and, set your Stripe account keys.

Going to /wp-admin/admin.php?page=wc-settings&tab=checkout&section=stripe&panel=settings, I only see blank boxes where the Stripe credentials and other fields should be.

This fix needs to be high priority, I'm sure I'm not the only person losing revenue right now.

@faroutride
Copy link

faroutride commented Nov 8, 2023

This fix needs to be high priority, I'm sure I'm not the only person losing revenue right now.

This. I enabled PayPal now, as I don't want to revert back to WP6.3 to make Stripe work again.

@dingod
Copy link

dingod commented Nov 8, 2023

I am also having this bug. Losing mad sales. Ultra-high priority please! I am reverting to 6.3.2.

@74MR47
Copy link

74MR47 commented Nov 8, 2023

Another report:

ZD: 7279724

Forum Thread: 👉 WordPress 6.4 version and issues with this plugin

@beaulebens
Copy link

This is likely being caused by a change in WordPress, which is being reverted/hotfixed here. As soon as that is available (or if someone wants to apply the PR directly), please confirm if you're still seeing this issue on impacted sites.

@beaulebens
Copy link

WordPress has a release candidate available in case anyone is in a position to test/confirm: https://make.wordpress.org/core/2023/11/08/wordpress-6-4-1-rc1-is-now-available/

@mostafasoufi
Copy link

I even tried to set a proxy WP_PROXY_HOST but didn't work, just fixed by rolling back to the previous version by:

wp core update --version=6.3.2 --force

@Obesepete
Copy link

Had the same issue, rolled back to 6.3.1, immediately everything worked again. Updated all API keys also.

@rob-vandenberg
Copy link

I tried the new version 6.4.1 and it solved the problem for me.
The site is fast again and the Stripe Gateway is working normally.

@faroutride
Copy link

Same here, issue solved with WP 6.4.1.

@shameemreza
Copy link

Another report here: 7280641-zen.

Suggested to upgrade WordPress to 6.4.1.

@shameemreza
Copy link

Perhaps Another report here: https://wordpress.org/support/topic/major-issue-with-curl-28-timeouts/

7281239-zen

@shameemreza
Copy link

Another report: 7281493-zen

@james-allan
Copy link
Contributor

Thanks everyone for the reports and your work to test can confirm the issue and fix.

WordPress 6.4.1 has now been officially released and by all accounts that has resolved the performance issues. Please update to WordPress 6.4.1 as soon as possible.

If you continue to experience problems, slowdowns or connectivity issues, please get in contact.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests