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

Bind bamboo to specific interface

Hi folks,

I've been trying to lock down my installation and I'd really like to make Bamboo only bind to 127.0.0.1. Following advises such as: http://confluence.atlassian.com/display/DISC/mail/172056 I added an address="127.0.0.1" in the tomcat installations, and for Bamboo's Jetty I edited webapp/WEB-INF/classes/jetty.xml, uncommenting <Set name="Host">127.0.0.1</Set>

Interestingly, only Bamboo refuse to do that. Jira, FishEye and Confluence are all running on 127.0.0.1:8xxx

Anybody got any insight on this?

1 answer

0 votes

Just making sure: you've followed this guide first?

Also, not sure if it's an issue for you, but if you bind Bamboo to loopback interface, you will not be able to use remote agents.

You also need to change <property name="bamboo.jms.broker.uri">tcp://0.0.0.0:54663</property> to 127.0.0.1 in bamboo.cfg.xml

That's the broker URI and doesn't have much to do with the listener, in fact, that port isn't even open. But I'll take a look at that - I didn't know I have to tell it to use jetty.xml ~_~

Thanks a bunch!

i

Suggest an answer

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

Unable to add or edit Bitbucket Cloud repository in Bamboo

On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...

444 views 2 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