BugWP logo BugWP
Back to Community
Home / Community / Plugin → Woocommerce stripe payment gateway

Troubleshooting Common Stripe Connection Errors in WooCommerce

32 threads Sep 17, 2025 Plugin → Woocommerce stripe payment gateway

Content

Why Your WooCommerce Stripe Gateway Suddenly Stops Connecting

Many WooCommerce store owners rely on the Stripe Payment Gateway plugin for seamless credit card processing. However, a common and frustrating issue is when the plugin, which worked perfectly for years, suddenly stops connecting to Stripe's servers. This manifests in errors like "A valid URL was not specified," "Error saving account keys," "cURL error," or "problem connecting to the Stripe API endpoint." This guide will walk you through the most common causes and their solutions.

Common Error Messages and What They Mean

Based on community reports, these are the typical errors users encounter:

  • "A valid URL was not specified" / "No valid URL provided" (WP_Error)
  • "Error saving account keys" / "Error retrieving account data"
  • "cURL error XX" (e.g., cURL 77, 28, 7, 6)
  • "There was a problem connecting to the Stripe API endpoint" on checkout
  • Fatal Errors like "Uncaught TypeError: array_merge(): Argument #2 must be of type array, bool given"
  • "Seems like the live keys we’ve saved for you are no longer valid" (even with correct keys)

Top Troubleshooting Steps to Regain Your Connection

1. Investigate cURL and Server Configuration (The Most Common Cause)

A vast majority of connection problems stem from the server's ability to make outbound calls using cURL, a library used by WordPress to communicate with Stripe's API.

  • Check if cURL is installed: Your server must have cURL installed and enabled. Some users have reported seeing a notice that "cURL is not installed." Contact your hosting provider to confirm cURL is active on your server.
  • Check PHP Version: Ensure you are running a supported, non-end-of-life PHP version. Older PHP versions can have compatibility issues with newer plugin updates and lack critical security updates.
  • Check for SSL Issues: Errors like cURL error 77: Unable to initialize NSS often indicate a problem with the SSL certificates on the server. Your hosting provider can often fix this by updating or correctly configuring the certificate path.
  • Check for Firewalls or Blocked Ports: Your server must be able to communicate with api.stripe.com on port 443. Hosting providers can sometimes change firewall rules. Request they verify that outbound connections to api.stripe.com:443 are not blocked.
  • DNS Resolution: Errors like cURL error 6: getaddrinfo thread failed to start point to a DNS problem, meaning your server cannot resolve the Stripe API's domain name. A server reboot or a DNS flush by your host may resolve this.

2. Perform a Conflict Test

A theme or plugin conflict can break functionality without causing an obvious fatal error.

  1. Temporarily switch your theme to a default WordPress theme like Twenty Twenty-Four or Storefront.
  2. Disable all plugins except for WooCommerce and WooCommerce Stripe Payment Gateway.
  3. Attempt to re-save your Stripe keys or test the connection.
  4. If it works, re-enable your plugins one-by-one, testing after each, to identify the conflicting software.

3. Reinstall the Plugin

A faulty update can sometimes leave the plugin installation incomplete or corrupted, leading to errors like missing files (failed to open stream: no such file or directory).

  1. In your WordPress dashboard, navigate to Plugins > Installed Plugins.
  2. Deactivate and delete the "WooCommerce Stripe Payment Gateway" plugin. Do not worry; this will not delete your saved settings or keys.
  3. Go to Plugins > Add New Plugin and reinstall Stripe Payment Gateway fresh from the WordPress repository.
  4. Reactivate and reconfigure the plugin.

4. Address the "array_merge()" Fatal Error

This specific error, often occurring during the OAuth connection process, is a known bug that has been reported in the plugin's GitHub repository. The 'WooCommerce Stripe Payment Gateway' team has addressed this in more recent versions.

  • Update the plugin: Ensure you are running the absolute latest version of the WooCommerce Stripe Payment Gateway plugin, as this fix may have already been released.
  • Manual Key Entry: If updating doesn't help, you can bypass the OAuth connection process. In the Stripe settings, click "Enter account keys (advanced)" and manually paste in your Publishable and Secret Keys from your Stripe dashboard.

5. Gather Information for Your Host or Community

If the problem persists, you will need to gather detailed information to get further help from your hosting provider or the community.

  • System Status Report: Navigate to WooCommerce > Status. Click "Get system report" and then "Copy for support." This provides critical data about your environment.
  • Stripe Logs: Enable logging in the Stripe settings (WooCommerce > Settings > Payments > Stripe). After reproducing the error, check the logs at WooCommerce > Status > Logs and select the latest wc-stripe log file.

Conclusion

A sudden loss of connection between WooCommerce and Stripe is almost always caused by a change in the server environment (cURL, PHP, SSL) or a plugin conflict. Methodically working through these steps—starting with a conflict test and verifying server configuration with your host—will most often lead you to the solution and get your payment processing back online.

Related Support Threads Support