This seems to be related to SSL Error while installing addon - #5 by piotr.patrzek1. But that thread said it was solved and it did not include the client-side error. So I created this new topic.
When I use the official Atlassian Connect Express to register an APP, there is a big chance (> 50%) that it errors out with the following error (note the highlighted subcode: ump.pluginInstall.error.ssl line):
Failed to register with host https://zenuml-stg.atlassian.net/wiki (200)
{"type":"INSTALL","pingAfter":300,"status":{"done":true,"statusCode":200,"contentType":"application/vnd.atl.plugins.task.install.err+json",
**"subCode":"upm.pluginInstall.error.ssl"**,
"source":"https://air.zenuml.com/atlassian-connect.json","name":"https://air.zenuml.com/atlassian-connect.json"},"links":{"self":"/wiki/rest/plugins/1.0/pending/e3789319-ea75-4c9b-83fa-29590926c998","alternate":"/wiki/rest/plugins/1.0/tasks/e3789319-ea75-4c9b-83fa-29590926c998"},"timestamp":1617797921094,"accountId":"557058:0a2e245b-f5cd-42f7-bf07-a53b8d17e94f","id":"e3789319-ea75-4c9b-83fa-29590926c998"}
Add-on not registered; no compatible hosts detected
It normally works if I kill it and rerun. I am using cloudflare’s argo tunnel to expose my local service. ( https://www.cloudflare.com/en-au/products/argo-tunnel/). I used this command to start the local service: AC_LOCAL_BASE_URL=https://air.zenuml.com node -r esm app.js, where air.zenuml.com is my public hosting name.
I have no idea what I should check as it is not 100% reproducible. Can someone please help?
By the way, when I install it manually from the ump page, I also see this error often.
Hi @eagle.xiao ,
Please refer to Connect troubleshooting guide in the first instance to see if that helps you pinpoint the problem.
I tried to run Qualys SSL Labs - SSL Server Test for your domain but got Unable to resolve domain name, so I suppose your app is down at the moment.
I also found this cloudflare-specific discussion that looks like it might be relevant to your issue.
Hope that helped.
Regards,
James Hazelwood
Senior Developer, Ecosystem Platform, Atlassian
Hi @jhazelwood , thanks for your help. The error is still happening. I noticed this error message, but sure it is important: “Authentication verification error (401): Could not find authentication data on request”.
I said it was not 100% reproducible, but I think it is now. All the re-registration fails, so I have to kill the command line and re-run.
I also tested my domain with Qualys SSL Labs. Here is the result. Detailed report
https://www.ssllabs.com/ssltest/analyze.html?d=air.zenuml.com&s=104.21.30.143
https://www.ssllabs.com/ssltest/analyze.html?d=air.zenuml.com&s=172.67.173.40
Authentication verification error (401): Could not find authentication data on request is a different error, which usually indicates that the site where you’re installing your app has no record of a previous installation, but your app does have a record of a previous installation, and so won’t accept another.
Assuming it’s just a test app and you can clear the database, that should fix it.
This is my “store” configuration. Is it not cleared automatically if it using memory DB?
"store": {
"adapter": "sequelize",
"dialect": "sqlite3",
"logging": false,
"type": "memory"
}
Yes, if you restart it it should be cleared automatically.
