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

SSL securing remote agents

I'm trying to get my remote agents to phone in via SSL (via this guide), but I can't seem to get them to work, my current bamboo config defines the broker urls as:

broker url: 
ssl://0.0.0.0:54663?wireFormat.maxInactivityDuration=300000
 
broker client url:
failover:(ssl://bamboo.mydomain.com:54663?wireFormat.maxInactivityDuration=300000)?initialReconnectDelay=15000&maxReconnectAttempts=10

 

However the guide only says what to says to set "bamboo.jms.broker.uri" to, what should "bamboo.jms.broker.client.uri" be set to?


Bamboo runs on a server behind nginx, which is doing the SSL termination, and proxies the request to Bamboo. Is there incoming traffic to nginx on port 54663, or does all incoming traffic happen on HTTPS and bamboo opens a connection over port 54663 to the remote agent?

I'm guessing there may be some kind of incoming traffic to nginx on port 54663, because in the bamboo remote agent log I see:

WARN [Thread-0] [BambooActiveMQConnectionFactory] Broker URI: ssl://bamboo.mydomain.com:54663?wireFormat.maxInactivityDuration=300000 is invalid: java.net.ConnectException: Connection refused

But I don't think nginx will proxy any traffic besides http/https, so how does the 'jms' traffic bamboo sends get back to bamboo when nginx/apache are proxying?

3 answers

0 votes
rsperafico Atlassian Team Aug 25, 2015

Hello Justin,

Thank you for your question.

At the moment, Bamboo remote agents connectivity can be secure at this level: How to secure your remote agent (Bamboo Server), however, a feature to run Bamboo with client certificates will become available in Bamboo v5.10 as per https://jira.atlassian.com/browse/BAM-15451.

If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.

Thank you for your understanding.

Kind regards,
Rafael P. Sperafico
Atlassian Support

0 votes

At the moment, the Bamboo agent requires direct access to the JMS port of Bamboo, you can't proxy that.

Hi,
are there any updates yet and the jms port is proxy-able or still isn't?

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 ...

250 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