You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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
... 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:
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.
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?
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 :)
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
parameter things start to work