401 error - Invalid signature - provided signature does not match
See original GitHub issueHi,
Following error gets returned when calling an endpoint.
{
code: 'woocommerce_rest_authentication_error',
message: 'Invalid signature - provided signature does not match.',
data: { status: 401 }
}
I am providing valid consumerKey and consumerSecret values.
Can someone take a look?
Thanks!
Issue Analytics
- State:
- Created 4 years ago
- Comments:16 (2 by maintainers)
Top Results From Across the Web
Woocommerce REST API Status: 401 - Invalid signature
As the error is self explanatory. This is clearly an authentication issue. It's clearly mention in the documentation. Over HTTPS.
Read more >Problem with Rest API's in woocommerce - WordPress.org
A Invalid signature – provided signature does not match message returned from the WooCommerce REST API indicates an authentication misconfiguration. This ...
Read more >Why do I receive a "401 Signature Invalid" response when ...
The signature will always be considered invalid if the time is incorrect on the server you're using to generate the Authorization header. Please...
Read more >401 Error - Invalid Signature - VitalSource Support
Users will see this error when during the initial LMS configuration with VitalSource the LTI Secret was incorrectly entered, there are too many ......
Read more >Wordpress > 0Auth 1.0 > Invalid signature > 401 - Gravity Forms
API access Issues Can someone help me figure out why I am receiving ... "message": "Invalid signature - provided signature does not match....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I had the same error. Fixed this by setting the Site Address in (Wordpress general settings) the same as WordPress Address
This worked for me: add
queryStringAuth: truein the config. Like this: