Hi
we are running version 5.6, and have a valid .jks file completed.
The bitbucket.properties config for our setup to enable SSL is :
server.port=443
server.ssl.enabled=true
server.ssl.key-alias=xxxxxxx (hidden for sec)
#server.ssl.key-store=D:\Atlassian\ApplicationData\Bitbucket\shared\config\ssl-keystore\bitbucket.jks
server.ssl.key-store-password=xxxxx(hidden for sec)
server.ssl.key-password=xxxxxx(hidden for sec)
Nice and simple. No. The service fails to start as soon as we enable SSL. In the logs it complains that a port is already in use, which is a false positive as this is not the case as its a standalone server. The logs also states the location for key-store is not the applied one above :
\Atlassian\Bitbucket\5.6.0\app\AtlassianApplicationDataBitbucketsharedconfigssl-keystore (The system cannot find the file specified)
In my mind, the system is not looking for the actual key-file stated above but Im not sure of anything at this stage.
Any help on this would be great as its delaying our deployment to live status.
Many thanks in advance.
Barney
