Problem with installing Atlassian connect add-on

[Brahim ESSALIH]

Hi every body

I developped an Atlassian connect add-on using spring-boot. I have two environments, the firsrt is my localhost and the second is my remote server. My add-on is an application spring-boot. In my local environment I use ngrok, secure introspectable tunnels to localhost, to generate a secure tunnel to my localhost:8080 and then using that like baseUrl to install my add-on in my cloud instance. That's work very good.

But when I try to install my add-on using the Url of my remote server,  JIRA cloud instance display me this error:

image2016-8-24 11:1:20.png

This is my add-on descriptor:

NB: 

1. "baseUrl": "https://f1f31ba2.ngrok.io"     //work fine   (local environment)

2. "baseUrl": "https://ts.my-remote-server.com:8080"        // not working  (production environment)

{
	"key": "com.company.mykey",
	"baseUrl": "https://ts.my-remote-server.com:8080",
	"name": "add-on-name",
	"description": "desc",
	"authentication": {
		"type": "jwt"
	},
	"lifecycle": {
		"installed": "/installed",
		"uninstalled": "/uninstalled",
		"enabled": "/enabled",
		"disabled": "/disabled"
	},
	"apiVersion": 1,
	"scopes": [
		"read",
		"write"
	],
	"modules": {
		"webPanels": [
			{
				"url": "/getTests?issueKey={issue.key}",
				"location": "atl.jira.view.issue.right.context",
				"conditions": [
					{
						"condition": "user_is_logged_in"
					}
				],
				"key": "issues-screen-right",
				"name": {
					"value": "title"
				}
			}
		]
	}
}

thank you  in advance

Best regards

[Petar Petrov (Appfire) · Accepted solution]

Have you enabled development mode on the instance? Also check that the json is accessible at the same URL via browser.

[Brahim ESSALIH]

Thanks @Petar Petrov [Botron]. Yes I active the developpement mode on the instance. Also

the json is accessible 

[Petar Petrov (Appfire)]

On the screenshot the URL is using the http protocol, while in the url you have https. Which one is correct? Https usually runs over 443 or 8443 (for tomcat). If those things are OK, you should open a support ticket with Atlassian.

[Brahim ESSALIH]

@Petar Petrov [Botron] this is the URL of my descriptor

https://ts.my-remote-server.com:60443/atlassian-connect.json

http://ts.my-remote-server.com:60445/atlassian-connect.json

[Petar Petrov (Appfire)]

And you get the same error with both these URLs?

[Brahim ESSALIH]

Yes the same error. But when I use ngrok and using the Url returned by ngrok, it works very well.

 ngrok http tst.oliverstore.com:60445

would you have any suggestions to solve this issue ?

[Robert Massaioli _Atlassian_]

I think that you may have issues trying to serve HTTPS over a port that is not 443; the standard HTTPS port.

[Brahim ESSALIH]

Thank you @Robert Massaioli , that was the problem.

it work now. This is a snippet of my URLs:

https://ts.my-remote-server.com/atlassian-connect.json
http://ts.my-remote-server.com/atlassian-connect.json
 
and my baseUrl is:
"baseUrl": "https://ts.my-remote-server.com"

I did the mapping of the port 8080 over the port 80 and I changed the mapping of the port 60443 to 443