Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Remote triggers from Git, to Bamboo working - not allowed, even when in allowed list

We are have having trouble getting remote triggers from Git, to Bamboo working.

 

The message LOGGED IS:

2016-02-19 04:42:21,952 INFO [http-bio-8085-exec-287] [TriggerRemoteBuild] Build request for plan "PLAYGROUND - Deploy using Curl To Strategic BAMS Artifactory (runs but artifact does not appear)" originated from unknown,10.52.132.2 which is not an allowed address (one of[, 10.52.132.2]).

Bamboo version is 5.9.4 build 5919 - 15 Aug 15

 

This is of course odd, as the IP address is in the list of allowed addresses. Can I get this exact version of source code of this class and surounding classes? Or could someone suggest other methods of resolving this.

 

many thanks

 

Dwane

 

 

 

 

 

 

 

 

 

2 answers

1 accepted

0 votes
Answer accepted

It seems to me that your request comes from through a proxy with "unknown" origin. Since "unknown" is not host trusted by Bamboo, it will not let the request go through.

If you use proxy for remote triggers both proxy and origin server's IP must be allowed in Bamboo.

We have this issue too, but we don't use a proxy. What else can I try ?

Some more digging gave us the following cause and solution

There was a squid proxy between github and bamboo who's x-forwarded settings were changing the headers in the request to:

X-forwarded-for [unknown]

This proxy could not be changed, so a NEW squid reverse proxy (just for github webhooks) was installed on the bamboo server, which could override this setting, and then the webhooks were successfully

 

 

 

 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

227 views 4 6
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