Application links between Bitbucket and Bamboo

[Lasse Langhorn]

After connecting a Bamboo instance (version 6.2.5) and a Bitbucket instance (version 5.5.0) via Application links, I receive an error
in the Bitbucket UI and an error is shown in the log.

Caused by: com.atlassian.sal.api.net.ResponseStatusException: Unexpected status: 403
 at com.atlassian.applinks.internal.common.net.ResponsePreconditions.checkStatus(ResponsePreconditions.java:28)
 at com.atlassian.applinks.internal.common.net.ResponsePreconditions.checkStatus(ResponsePreconditions.java:17)
 at com.atlassian.applinks.internal.common.net.ResponsePreconditions.checkStatusOk(ResponsePreconditions.java:37)
 at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$2.handle(AppLinksManifestDownloader.java:177)
 at com.atlassian.sal.core.net.HttpClientRequest.executeAndReturn(HttpClientRequest.java:104)
 at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.doDownload(AppLinksManifestDownloader.java:165)
 ... 49 common frames omitted

The error only occurs on Bitbucket not on Bamboo. I can curl from the Bitbucket server to the Bamboo server and get a response from the manifest REST endpoint, so the network connection seems fine to me.
So the instances can see each other, but for some reason Bitbucket responds with an error in the UI. More specific the error in Bitbucket is something like this:

Unexpected response
We received an unexpected response from Atlassian Bamboo. If the remote application is behind a proxy, check that the application is operational. Troubleshoot this for other possible causes.
403: Forbidden
To see the full response content look at your application logs

The Bitbucket instance does not have http.nonProxyHosts parameter set.

Have anyone experienced something like this before?

Thanks. 

[Danyal Iqbal · Accepted solution]

Unexpected status: 403

means that the resource is forbidden.

Bitbucket user does not have rights for bamboo.

The 403 error is essentially saying "Go away and don't come back here." You can check these as well but I am sure, you need more rights to get rid of this exception :)

• Check the URL. Must be a valid page, not a directory on the server.
• Make sure the user has the permissions to access the resource.
• Clean cache.
• check proxy settings

[Lasse Langhorn]

Hi @Danyal Iqbal,

Thanks for the quick response.

It looks like a proxy setting issue. 

Best regards

Lasse

[Lasse Langhorn]

When you have several Atlassian apps communicating with each other, check the proxy settings.

In my case I did not had the correct proxy settings for the Bitbucket app applied. Check this link: https://confluence.atlassian.com/bitbucketserverkb/how-to-configure-an-outbound-http-and-https-proxy-for-bitbucket-server-779171680.html#HowtoconfigureanoutboundHTTPandHTTPSproxyforBitbucketServer-ApplicationLinks.

My loadbalancer caused the problems. After applying the 

-Dhttp.nonProxyHosts

parameter things start to work