Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage
Highlighted

Cannot get SSL configured on Bitbucket Server 5

Hi,

we generated the CSR based on java key tool in linux and the ssl has imported to keytool “/home/ec2-user/ssl-keystores”successfully with the below commands. we need your help to resolve this.

 

[root@ip-172-31-5-38 bin]# ./keytool -import -alias root -keystore /home/ec2-user/ssl-keystores -trustcacerts -file /home/ec2-user/gd_bundle-g2-g1.crt

Enter keystore password:

Certificate was added to keystore

[root@ip-172-31-5-38 bin]# ./keytool -import -alias intermed -keystore /home/ec2-user/ssl-keystores -trustcacerts -file /home/ec2-user/gdig2.crt

Enter keystore password:

Certificate already exists in keystore under alias <root>

Do you still want to add it? [no]:  yes

Certificate was added to keystore

[root@ip-172-31-5-38 bin]# ./keytool -import -alias tomcat -keystore /home/ec2-user/ssl-keystores -trustcacerts -file /home/ec2-user/209134c24b7a184f.crt

Enter keystore password:

Certificate reply was installed in keystore

----------------------------------------------------------------------------------------------------------

We created a file bitbucket.properties with the below configuration and it wont works,

server.additional-connector.1.port=7990

server.additional-connector.1.redirect-port=8443

server.additional-connector.1.proxy-port=8443

server.additional-connector.1.require-ssl=true

server.additional-connector.1.secure=true

server.additional-connector.1.scheme=https

server.additional-connector.1.proxy-name=git.apptium.com

server.additional-connector.1.ssl.enabled=true

server.additional-connector.1.ssl.client-auth=want

server.additional-connector.1.ssl.protocol=TLSv1.2

server.additional-connector.1.ssl.key-store=/home/ec2-user/ssl-keystores

server.additional-connector.1.ssl.key-store-password=Apptium$123

server.additional-connector.1.ssl.key-alias=tomcat

server.additional-connector.1.ssl.key-store-type=jks

----------------------------------------------------------------------------------------------------

After doing all this we changed the base url to https://git.apptium.com/8443

Not working.

 

 

1 comment

..Both ssl.key-store-password and ssl.key-password require explicit configuration. Even if you did not configure both values in the server.xml file, values for both entries need to be explicitly set in bitbucket.properties to secure Bitbucket with SSL...

https://confluence.atlassian.com/bitbucketserver/migrate-server-xml-customizations-to-bitbucket-properties-897811761.html

Maybe the issue?

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Bitbucket

Powering DevOps with Bitbucket Server & Data Center

Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster   ! While we’re all excited about the new improvements to Bitbucket ...

2,100 views 0 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you