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

Private Bamboo Server behind AWS ELB, trouble connecting / registering a remote Mac agent

Gonzalo Arce September 30, 2020

Hi all, 

 

I hope you can provide some help for this issue I'm currently having....

 

My setup is currently like this:

 

- 1 single Bamboo Server Ec2 Instance (Private IP only) behind a public facing AWS ELB

- I have HTTP/HTTPS/ TCP 54663/ TCP 8085 listeners set up on the ELB which forward to the related ports on the host

- We have a bunch of private agents that connect and register to the server just fine using the private IP. Also may I say that currently the Broker URI is set to the host's private IP, whereas the main Bamboo endpoint is the ELB DNS.

 

The Issue:

 

- I can't get to register a new mac device that is outside our network. It does connect to the Bamboo server initially, but it then fails when trying to negotiate with the Bamboo broker URI (expected , as the remote device can't reach the private IP from outside).

 

Actual relevant config:

 

Bamboo Server URL: https://my.bamboo.url.com

Broker URI: tcp://private_ip:54663?wireFormat.maxInactivityDuration=300000

failover:(tcp://private_ip:54663?wireFormat.maxInactivityDuration=300000)?initialReconnectDelay=15000&maxReconnectAttempts=10

What I tried:

1 - atlassian-bamboo-agent -0 - the BROKER URL is set to tcp://0.0.0.0:54663?wireFormat.maxInactivityDuration=300000.

 

INFO   | jvm 1    | 2020/09/17 12:45:40 | 2020-09-17 12:45:40,350 ERROR [ActiveMQ Task-1] [FailoverTransport] Failed to connect to [tcp://0.0.0.0:54663?wireFormat.maxInactivityDuration=300000] after: 10 attempt(s) Wrap

2 - atlassian-bamboo-agent -1 - the BROKER URL is set to tcp://my.bamboo.url.com:54663?wireFormat.maxInactivityDuration=300000.

INFO   | jvm 1    | 2020/09/17 12:52:01 | 2020-09-17 12:52:01,279 WARN [AgentRunnerThread] [FailoverTransport] Transport (tcp://my.bamboo.url.com:54663?wireFormat.maxInactivityDuration=300000) failed , attempting to automatically reconnect: java.io.IOException: Wire format negotiation timeout: peer did not send his wire format. Wrap

3- SSL is only terminated at the ELB right now, and I still have 54663 open as an ELB listener, so the below wouldn't make sense? but also tried:

atlassian-bamboo-agent -2 - the BROKER URL is set to ssl://my.bamboo.url.com:54663?wireFormat.maxInactivityDuration=300000

INFO   | jvm 1    | 2020/09/17 13:21:44 | 2020-09-17 13:21:44,473 ERROR [ActiveMQ Task-1] [FailoverTransport] Failed to connect to [ssl://my.bamboo.url.com:54663?wireFormat.maxInactivityDuration=300000] after: 10 attempt(s)

 

 

 

Any suggestions appreciated...

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events