You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi I have Bamboo running with a firewall and I am trying to setup the remote agent that also has a firewall. I can correctly configure the bamboo server's firewall to allow communication with the remote agent. However, I am unable to figure out which ports are required to be open on the server running the remote agent. I have reviewed https://confluence.atlassian.com/bamkb/troubleshooting-remote-agents-216957427.html but it only specifics ports for the server side and says nothing about ports on the remote agent side. Any ideas?
This is a few years' old but since there isn't an answer, I'll throw my partially-informed perspective in.
As I understand it, the Remote Agent initiates all the connections and the Bamboo server simply responds. The server side never initiates connections with the Remote Agent (Atlassian folks, please correct me if I'm wrong).
Therefore, the Bamboo server host machine needs to be able to receive requests on the ports listed on the that "Troubleshooting Remote Agents" page and the Remote Agent needs to be able to initiate connections on those ports from its host. Network firewalls and host-resident (see below) need to have been configured to allow this.
Where I've had the most problems (and perhaps this is what the OP was encountering) is when the Remote Agent is installed on Windows. The culprit (apart from me occasionally forgetting an installation step) is usually Windows' in-built firewall (AKA Windows Defender Firewall) so always check to see what that's up to because 9/10 times when my Remote Agent on a fresh host is failing to connect to the server, it's the Windows firewall blocking out-bound connections.