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

Authorized agent requires reauthorization after server restart

James Brown
Contributor
September 27, 2019

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

0 votes
zaro-atlassian
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 1, 2019

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
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 30, 2019

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
TAGS
AUG Leaders

Atlassian Community Events