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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Need to configure additional TCP port

We have a need to connect to our Bitbucket 7.2 instance running in Ubuntu 18.04 on an additional TCP port. I entered the following into the file, and restarted the server, verified Bitbucket was operational but the port is not listening. We CAN successfully connect on ports 22 and our server port of 7999. Is there another way to do this or am I missing something in this configuration? Thank you. 


1 answer

1 accepted

0 votes
Answer accepted

Hey @Cameron Shove 

Just to confirm - are you looking to add an additional port for connecting to Bitbucket over HTTP, or over SSH? The ports you listed (22 and 7999) are SSH ports - meaning that the "server.additional-connector.1.port" property that you specified, which adds a new HTTP(s) port, won't work for your purposes.

At this time, there's no way to set up multiple SSH ports for Bitbucket to use on the Bitbucket layer. If your team would like to see something like that implemented in the product, I'd recommend raising a suggestion with our devs over at Otherwise, your best bet would be to see if you can set up something like a load-balancer or reverse proxy in front of Bitbucket - and then port forward from your desired ports over to your Bitbucket node(s) at port 7999. 

Hope this helps!


Evan Slaughter

Senior Support Engineer | Atlassian Support - Development Tools

Thanks so much for the input, and yes I didn’t realize the property I was trying to add was limited to HTTP. I appreciate the response.

Like Evan Slaughter likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events