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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,552,588
Community Members
 
Community Events
184
Community Groups

Allow Bamboo trigger to be fired to any IP

Edited

Hi, i am trying to use Bamboo triggers to deploy to QA env when a pull request is merged on Bitbucket, since our servers are under firewalls i am receiving following error


"Build request for plan [my_pan] originated from x.x.x.x,0:0:0:0:0:0:0:0 which is not an allowed address"

 

It looks like trigger is receiving an IPv6 instead of IPv4, so, i would like to allow any IP to run my trigger.

 

Any suggestion?

 

NOTE.- since i am not server admin it could be a little be hard to modify any configuration at OS level

1 answer

0 votes
Steffen Opel _Utoolity_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 02, 2019 • edited

This sounds like you are affected by the long standing but meanwhile addressed lack of IPv6 support in Bamboo, the following bug matches your error message:

While BAM-5172 lacks a fix version, the linked Support IPv6 (BAM-14256) issue suggests that this has finally been addressed as of Bamboo 6.7 in October 2018.

Unfortunately this implies that you will need to persuade your server administrator to upgrade Bamboo to a respectively recent version, though BAM-5172 at least lists the following potential workaround as a short-term remedy:

If IPv6 is enabled on the Bamboo server, it can be disabled to workaround this issue.

Hi @Steffen Opel _Utoolity_  

yes, i already saw this quick fix, but as i mentioned i need to contact server admin in order to do this change, well let me try to go that way.

Thanks.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events