Circle 2.0 machine executor: port 5500 taken



While porting our main pipeline to 2.0 I noticed that port 5500 is bound by an extra sshd process (under the circleci user) on the machine executor VM instances.

a) What’s the reason for this?
b) Can it be changed? We have a service that we by default bind to


Our build agent (the thing that actually executes the build) listens on that port. Sadly this cannot be changed.

cc @michelle-luna might be worth documenting all “reserved” ports.


Makes sense, thanks for the feedback. Have switched ports on the dependent service. Ta.


This topic was automatically closed 41 days after the last reply. New replies are no longer allowed.