Invalid response from WooCommerce

Invalid response from WooCommerce


You are receiving the following error message in CartRover:

Invalid response from WooCommerce.

CartRover only uses the native functionality built into WooCommerce without modifying it in any way. CartRover does not need nor provide a WooCommerce Plugin.

Solution - Status 500

This is caused by an error in your WooCommerce site (status code 500). The most common reasons are a plugin you installed or a customization made to your WooCommerce installation. Because CartRover does not modify WooCommerce and WooCommerce is hosted on your own servers, you must find and resolve this issue yourself or with the help of your existing IT/Support. However the information below can help to diagnose the problem.

  1. Turn on WooCommerce debugging. This will allow CartRover and others to see the exact error message WooCommerce is reporting.
    1. Lean how to turn on debugging here:
    2. Be sure to turn off debugging after the issue is resolved.
  2. Check the WooCommerce error logs as well as the web server error logs on your server. They will contain the error message and usually point to the location in the WooCommerce code causing the error.

This information will help you identify the plugin or change causing the error. You will then need to do one of the following:

  1. Disable the plugin
  2. Contact the plugin's support and report the issue so they can fix it
  3. Work with your IT team or WooCommerce support to fix the issue in WooCommerce.

If you determine which plugin was causing your issue, please let CartRover support know.

Solution - Status 403

This is caused by a misconfiguration with your WooCommerce server (status code 403). Please work with your server admin or other IT resources to ensure you have properly configured both WooCommerce and your web server.
403 means that your web server is refusing access to certain URLs. Make sure that your server is allowing access to the following endpoints and all subdirectories:
  1. /wc-api/
  2. /wp-json/wc/

Solution - Status 301 or 302

This is caused by a redirect on your site. When CartRover attempts to connect, we are redirected to a different URL. To solve this, the URL entered in CartRover must be corrected. You can test this by adding "/wp-json/wc/v2" to the end of your store URL and visiting it in a browser. Check if the browser URL changes to a different address.
This is most commonly caused if you enter your Store URL as http:// when it is actually https:// or including/excluding the www. portion of your URL when your site expects it the other way around.

    • Related Articles

    • Error adding notes to order - WooCommerce

      Problem After orders ship, CartRover is raising the following alert: Error adding notes to order Could not add tracking note to order: XXXX You do not have permission to create order notes Solution In the left pane of the WooCommerce Dashboard hover ...
    • WooCommerce reported a file not found error

      The following is an error that may display when testing your WooCommerce cart credentials: Test failed Server Said: Please check server settings. WooCommerce reported a 404 error (file not found) at: https://<storename>/wc-api/v2/orders [http status: ...
    • Sorry, you are not allowed to create resources - WooCommerce

      Problem CartRover is raising the following alert when trying to mark your orders as shipped: Subject: Error adding tracking to Tracking Extension Message: Could not add tracking data to order: XXXXXX woocommerce_rest_cannot_create: Sorry, you are not ...
    • Cannot communicate securely with peer - WooCommerce

      Problem CarotRover displays the following error message when trying to communicate with WooCommerce: Could not confirm order: Cannot communicate securely with peer: no common encryption algorithm(s). Solution If you see this error, go into you ...
    • Fix WooCommerce Permissions

      In the left pane of the WooCommerce Dashboard hover over "WooCommerce" and click on Settings Click on the API tab Click on Keys/Apps and then click on the existing API Key Set the permissions to "Read/Write" and save changes.