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

Authorized agent requires reauthorization after server restart

I am currently experiencing an issue with a bamboo agent requiring it to be authorized after a server restart.

The agent was previously authorized before the server was restarted. The agent configuration is the same and was not uninstalled from the server it was installed on. It additionaly has the same IP address and UUID?

Has anyone experienced this issue and found the cause and solution to this issue?

2 answers

Hey @James Brown 

This could also happen if your reverse proxy (if you have one) settings were changed since the agent was approved the first time. As an example, if you change the X-Forwarded-Host configuration on your proxy, Bamboo may see a different IP even if the IP of the agent host did not change.

0 votes

Hi @James Brown

The agent identification/authorization is processed based on UUID and IP address.

  • Do you mind checking if your Bamboo server or agent changed the IP while the server was restarted?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events