fbpx

WooCommerce Error: an error occurred in the request and at the time were unable to send the consumer data.

You are here:
  • Main
  • Errors and issues
  • WooCommerce Error: an error occurred in the request and at the time were unable to send the consumer data.
< All Topics

There are a few possible causes to this issue:

  • The most common cause of this problem is that your store’s is using WooCommerce version 3.5 or earlier. Make sure you upgrade to the latest WooCommerce version before installing our plugin.
  • Your store doesn’t have a valid HTTPS/SSL certificate. Make sure you install and activate one so our app can communicate with the WooCommerce API.
  • For the plugin to work WordPress needs to be installed at domain or subdomain level, not at page level. For example, say you’re developing a store for a client and you’re creating a mockup on www.example.com/devstore/. Our server will try to connect to the WooCommerce API at subdomain level, on www.example.com but the store is on www.example.com/devstore/. As an alternative, you can install the development store on the devstore.example.com subdomain, that it will work.
  • Your website is password protected, or you’re using a “coming soon” or “site under construction” plugin that’s disabling public access to your store. This also disables API access and our app needs it to work.
  • You have a caching plugin on your store that strips the “Authorization” header. Try disabling your plugins one by one to find the one that’s causing the issue.

If you’ve tried all the above, your server is stripping the “Authorization” header.

Authorization – step 1
Authorization – step 2 – error

Important: As this pertains to configuration of your webserver and/or other WordPress plugins, RevenueHunt cannot provide support in these cases. You can try the suggestions below at your own risk. Please always consult with a web developer when making configuration changes.

In some cases adding the following to your .htaccess file might help:

SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1

If that does not help, please review the configuration of your caching plugin and look for settings that pertain to caching or not caching headers.

If that does not work, contact your hosting provider.


Table of Contents