It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Our instance will no longer start, with this error in the logs:
The Tomcat connector configured to listen on port 443 failed to start. The port may already be in use or the connector may be misconfigured.
I followed the guide to move things to bitbucket.properties; something is askew. I use the keystore method for connecting to cert in the past:
protocol="org.apache.coyote.http11.Http11NioProtocol" keystoreFile="D:\namehere.pfx" keystorePass="passhere" keystoreType="PKCS12"
Do I need to include keystore Type and Protocol in the bitbucket properties? Where do I find those keywords?
Hi Eric! Have you checked that there's no other application running on port 443? It could be that the older version of Bitbucket is running still there.
You should be able to find the keystore Type and Protocol in the bitbucket.properties.
For more information, you can refer to Migrate Server XML customizations to Bitbucket properties.
Hope that helps!
Ana
Hi Eric,
If you're using a different type of keystore you can specify that in bitbucket.properties using server.ssl.key-store-type=pkcs12.
Cheers,
Christian
Premier Support Engineer
Atlassian
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreBitbucket 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 groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.