I upgraded to Bitbucket Server 5 from 4.latest and cannot get the SSL part configured in the new bitbucket.properties file which migrated from server.xml. I'm getting a SSL protocol error when trying to go to my site in Chrome, etc. Here are my configs, first the server. xml file and the new bitbucket.properties file. I'm using Windows Server 2012 R2.
Can someone please tell me how to setup the bitbucket.properties file for my former connectors?
I just resolved this issue, short story, I needed to have both ssl.key-store-password and ssl.key-password (in addition to ssl.enabled=true). While probably not necessary I also re-exported my wildcart cert from IIS to a pfx, left it as a pfx and updated my config to use pkcs12 as the type. I used the keytool command to get the aliax from the pfx which is a guid. Here is my complete new config that now works. Many thanks to Atlassian support for the help and Jeff above.
It's a shame we don't have comments inline with the documentation like in the past as that's always been a huge help. There is a lot lacking in the documentation, I had to take a stab at server.address as you can see I set a port and IP address as do all my atlassian products on one server.
Full day lost on this one! :( But I'm glad it's fixed.
EDIT: I changed the config above, using the pfx / pkcs12 did not work, maybe for lack of using an alias in my config, I don't know. While it worked to connect from the web site Bamboo could not get a valid SSL connection to clone git repos. I changed to the JKS cert and added the alias and now it works for me for all endpoints.
What is the SSL error that you're seeing?
It looks like the ssl.enabled property is missing. Can you try adding the following and see if it resolves the error?
If you were following a guide for this, can you let me know which one? I want to make sure that property is included in the documentation.
Update: Looks like you may be following Migrate server.xml customizations to bitbucket.properties which is missing this property. I'll get it updated.
When I add that the windows service will fail and stop.
APPLICATION FAILED TO START
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.
Verify the connector's configuration, identify and stop any process that's listening on port 443, or configure this application to listen on another port.
2017-05-05 14:40:16,166 INFO [main] c.a.b.i.boot.log.BuildInfoLogger Bitbucket 5.0.0 has shut down
I'm also having the exact same same issue. It's obviously a bitbucket.properties configuration issue but I can't at all find what's wrong.
My keystore is in pkcs12 format and my bitbucket.properties entries are:
And I get the exact same error as above, when I attempt to stop and restart BB 5.5.0.
Is it possible that your key alias is a custom one?
If that's the case, you would need to explicitly define it in the bitbucket.properties file.
Here is how you can check it:
- Find the correct alias: run this command against your keystore to list the keys and look at the value of the "Alias name" field
keytool -v -list -keystore <keystore> | grep Alias
- Add the key alias to your config: In $BITBUCKET_HOME/shared/bitbucket.propertie, add the key alias from step 1 to your main connector configuration
Here's how I did it.
Alias needs to match the name in the keystore
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