![credentials are invalid credentials are invalid](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/2043169520897/original/ke745oMQN5zZ3ePlBtS7Syrw3VXEBj3ijg.png)
Wp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
![credentials are invalid credentials are invalid](https://www.ibm.com/support/pages/system/files/support/swg/rattech.nsf/0/1454a25774474f12852576010036d7b6/Symptom/0.218.gif)
Wp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB Wp_woocommerce_sessions: Data: 1.02MB + Index: 0.02MB + Engine InnoDB Here is the WooCommerce status report: (By the way, Woo said they see nothing wrong here) All of this gets a little past my skill set. However, I’m unsure about which links you are referring to. Therefore, it is difficult to back track to pin point the time the error started or if the error was created by any updates.Īccording to the techs at GreenPay, the s are correct. And, I’m not sure when the problem actually started. RK, the site has had several updates in recent weeks. Unfortunately, it is out of our control since it is not related to the plugin but rather your website itself or the WooCommerce plugin’s functionality that our plugin simply relies on.” We did have one other merchant in the past report this problem to us but as far as we are aware, they reached out to WooCommerce directly and solved the issue though we were never told what resolution entailed or what web hosting platform they are on. However, in the same manner, calls to v2’s index passed unauthenticated (see test 2) but all calls to methods requiring authentication failed (see test 3 details). Both calls failed as a 401 Unauthorized indicating, as far as we are aware, that WooCommerce believes the REST API credentials to be invalid even though obviously both you and us have attempted generating them several times.Ĥ) As an additional measure, we also attempted to make the same calls to the v2 version of the WooCommerce API as sometimes we have seen sites respond differently. We attempted passing the authentication credentials via secure methods first using HTTP Basic Auth (required by our plugin) and when that failed we attempted using the less secure method of passing them via query parameters. We use the system_status for testing purposes since it doesn’t affect data in your store.
![credentials are invalid credentials are invalid](https://cdn.appuals.com/wp-content/uploads/2017/11/error-message.gif)
Calls to this URL responded in the way we expected by giving us the endpoint specifications.ģ) We then attempted to make calls to a authentication locked method of the API just as a test. The API is expected to respond to this call even when calls are not authenticated to prove that the API is live. To quickly clarify on all the troubleshooting we did to determine that:ġ) We generated a new set of API credentials to ensure that the values we had were correct as to what WooCommerce created.Ģ) We attempted an API call to the default endpoint as specified by WooCommerce’s documents which is at In your case, this was. “ At this point we’ve exhausted our troubleshooting capabilities and determined that the issue is not related to the Green plugin but is an issue related to the underlying WooCommerce API in your store specifically. Here is what GreenPay sent in their last email: GoDaddy says the issue is with WooCommerce or Avada. The tech at WooCommerce suggested the issue was with the server. Please double check your entry or generate new REST credentials.”Īfter several failed attempts to save new REST credentials, GreenPay tech support concluded that the issue is with WooCommerce. Error returned: WooCommerce REST API credentials and/or API URL are invalid. A few days ago my GreenPay app gave me the error, “ Green was unable to contact your store’s REST API using the given REST Client ID and Secret.