Netstat shows that Stash is using port 1397, 1443 and 8006 for local connections. But I cannot find out how to free up port 1443 for a SQL Server install.
Netstat result example:
TCP 0.0.0.0:5701 0.0.0.0:0 LISTENING 1156
TCP 0.0.0.0:7999 0.0.0.0:0 LISTENING 1156
TCP 0.0.0.0:9008 0.0.0.0:0 LISTENING 1156
TCP 127.0.0.1:1397 0.0.0.0:0 LISTENING 1156
TCP 127.0.0.1:1443 0.0.0.0:0 LISTENING 1156
TCP 127.0.0.1:8006 0.0.0.0:0 LISTENING 1156
TCP [::]:5701 [::]:0 LISTENING 1156
TCP [::]:7999 [::]:0 LISTENING 1156
TCP [::]:9008 [::]:0 LISTENING 1156
Edit: I can't reply to your comment due to the 24 hour restriction.
A few issues:
- I can't find the server.xml in the home directory: https://confluence.atlassian.com/stash/changing-the-port-that-stash-listens-on-321257990.html#notfound . Is it because I'm using Stash 3.6.0?
- I've updated my questions with the full netstat result. The top three open port 5701, 7999, and 9008 are configurable using the Stash Server Settings. The other ports appears to be used internally by Stash.
To change stash ports you need to edit the
conf\server.xml file in the
<Stash installation directory>.
See page below for more details on the lines you will need to change to accomplish that:
Hope this helps you.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot