Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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
Community showcase
Published in Bamboo

Bamboo Data Center on Kubernetes

Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...

51 views 0 3
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you