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 Monday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

446 views 0 9
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you