Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Branch Status, Dedicate Agent not working on Bamboo Server 6.5 after HTTPS change

We updated Bamboo server to uses HTTPS. Since the change, when we go to Build->Branch Status and try to add a plan to build a branch, we get the following error

An error occurred - not all plans added successfully.

In addition, when we try to dedicate a remote agent to a build plan, clicking the Add button does not do anything.

Please advise.


1 answer

0 votes
Victor Debone
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 22, 2019

Hello @Rizwan Choudrey welcome to the community! :)

Did you make changes on Bamboo or Tomcat configuration after you've installed your HTTPS certificate? If yes, can you give a short description of what was changed?


Hi Victor, thanks!

Our IT made the changes. This is what they say:

Main change was to add an additional virtual host to the apache configuration (something like /etc/httpd/apache2.conf from memory). At the bottom is a vhost for port 443, which proxies to the real bamboo server on port 8085. 

Only other change was firewall-related: we blocked access to port 8085 and then opened it back up for the remote agent boxes (GARBLA*).

Configured the application path in Bamboo itself to https://bamboo.garrison.local/ aintead of  http://bamboo.garrison.local:8085/.


Hope that helps?




Victor Debone
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 23, 2019

Surely do! From what you have described, there is a missing step.

You will also need to change the proxy configurations in Bamboo's Tomcat, you can find more details here.

Did that help?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events