ERROR:- Installation verification error: 401 clientKey in install payload did not match authenticated client

I have created a add on for JIRA to connect to our app. once i am trying to start (npm start ) i am getting error (Installation verification error: 401 clientKey in install payload did not match authenticated client). previously it was working fine. i have not done any change suddenly error is showing. please suggest

Same here , it was working fine last week

GET /atlassian-connect.json 200 3.929 ms - 610
Installation verification error: 401 clientKey in install payload did not match authenticated client
POST /installed 401 352.346 ms - 63
Failed to register with host https://xxxxxxxx.atlassian.net/ (200)

Hi,
Did you try reinstalling the app?

I did retry with reinstalling app and also tried with new sample app with atlas-conncect command line but same issue.

Watching atlassian-connect.json for changes
App server running at http://xxxxx:3000
Local tunnel established at https://xxxx.ngrok.io/
Check http://127.0.0.1:4040 for tunnel status
Registering add-on…
GET /atlassian-connect.json 200 10.265 ms - -
Installation verification error: 401 clientKey in install payload did not match authenticated client
POST /installed 401 65.208 ms - 63
Failed to register with host https://xxxxxxxx.atlassian.net/ (200)
The app host returned HTTP response code 401 when we tried to contact it during installation. Please try again later or contact the app vendor.
{“type”:“INSTALL”,“pingAfter”:300,“status”:{“done”:true,“statusCode”:200,“contentType”:“application/vnd.atl.plugins.task.install.err+json”,“subCode”:“connect.install.error.remote.host.bad.response.401”,“errorMessage”:“The app host returned HTTP response code 401 when we tried to contact it during installation. Please try again later or contact the app vendor.”,“source”:“https://xxxxx.ngrok.io/atlassian-connect.json",“name”:“https://xxxx.ngrok.io/atlassian-connect.json”},“links”:{“self”:"/rest/plugins/1.0/pending/891d1498-abb9-4aff-9f99-27f6980b1930",“alternate”:"/rest/plugins/1.0/tasks/891d1498-abb9-4aff-9f99-27f6980b1930"},“timestamp”:1623055835505,“accountId”:“xxxxx”,“id”:"xxxxx”}
Add-on not registered; no compatible hosts detected

yes same here i also tried reinstalling the app. but same issue still there.

Same error here, and it was working fine last week too. Is it possible that the problem is not from our part?

GET /atlassian-connect.json 200 17.459 ms - 652
Installation verification error: 401 clientKey in install payload did not match authenticated client
POST /installed 401 480.196 ms - 63
Failed to register with host https://******************.atlassian.net/ (200)

1 Like

Hi,
This is affecting two of my apps that can’t be installed by new customers.
Jerry

1 Like

I ran into this problem today and it seemed to be issue with the version of Atlassian-connect-express that’s higher than 7.0.0. When I downgraded the version back to v6.6.0, it’s working again. There seems to be a bug during the installation process. It’s performing a check on matching clientKey when there’s NO record being returned from the settings table. Prior, it would check if a record is found before trying to test for a match of clientKey. If no match is found, it would allow for a new record to be inserted.

I tested it out in dev mode. Since I know the clientKey of my atlassian dev instance, I manually put a record in my table. Afterward, my installation would work.

1 Like

Same problem with our app. Rollback to 6.6.0 did not work, re-install of one of our test environments still failed, but upgrading to the recent 7.1.4 ace patch did fixed the problem for us.

1 Like

thanks Chris , it worked for me after upgrading ace to 7.1.4

thanks Chris , it worked for me…

had a similar issue on version 7.1.2.
Upgrading to 7.1.4 solved it as well. Thanks!

I am also having the same issue even though applied ACE to 7.1.4. Please suggest the solution.

Can someone confirm if this issue impacts customers installing from Marketplace, or is this just impacting local ngrok development?

(@jerry.laster - you mentioned it was affecting customers?)

Neither status.atlassian.com and developer.status.atlassian.com show any active related incidents, so can we assume this is a developer issue only, and there is no urgency for us to patch production apps?

We’re seeing the same error in dev with an app that uses ACE 7.0.1 (albeit a Confluence app); which was working OK previously until we tried to fire up the dev environment today and saw the 401 clientKey in install payload did not match authenticated client error, and a quick Google led us here.

We’re OK to upgrade to 7.1.4 if that’s the fix, but it is unclear if we need to push that out to production ASAP.

This affected apps using ACE 7.1.13. ACE 6.6.0 and 7.1.14 are not affected. There are some comments regarding sprinbot implementations.

1 Like

Thanks.

Interesting though that we’re seeing the error today (in Dev) with ace 7.0.1

It affects customer on Marketplace. Didn’t have any new installations after upgraded the ACE to 7.1.3 (for 7 days now). Got couple of support tickets about it.

@stepashka Atlassian said it’s fixed in ACE 7.1.4. You need to upgrade ACE urgently.

I know now. Already updated these. That’s disappointing that such major issues get to the library. Reminds me that improvements are needed in the verification pipeline on my side as well.