I am currently running SSL/HTTPS Stash using port 8443..
Because of the company policy.. I have to run this in 443 instead of 8443..
I configured server.xml
<Connector port="8443" to <Connector port="443"
but after this configuration.. the server is not starting at all..
When I run netstat -plten | grep java command.. I don't see 443 running.. (other than 443 is running)
Do I have to make any other changes?
Unless you run Stash as root, you can't (in most Linux distros) bind to port 443. Running Stash as root is not good practice because malicious code then as root access to the entire machine.
So the next best approach is to run Stash as a non-root use and use something like Apache to configure a reverse proxy. Apache runs as root and re-directs traffic to Stash running on the same server. This is documented here:
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot