Stumped trying to get HAProxy and Bitbucket to work

I've got HAProxy working perfectly as an reverse proxy on my JIRA server.  However using almost the exact same haproxycfg file on my Bitbucket server (with the obvious changes due to hostnames and default ports, etc.)

The current settings in my Bitbucket server allow me to access it through https (8443) or via http (7990) fine:

server.port=8443
server.ssl.enabled=true
server.ssl.key-store=/etc/pki/tls/keystore/bitbucket.jks
server.ssl.key-store-password=<password>
server.ssl.key-password=<password>
server.ssl.key-alias=<alias>
server.ssl.protocol=TLSv1.2
server.ssl.key-store-type=pkcs12
#
server.additional-connector.1.port=7990
#server.secure=true
#server.scheme=https
#server.proxy-port=443
#server.proxy-name=myserver.corp.mydomain.com

However, as soon as I uncomment the four bold entries, that's when it all blows up.

Do I need to change the syntax of those entries to be associated with the server.additional-conector.1 lines?  Such as server.additional-connector.1.secure=true?

 

Environment

CentOS 7.4
BitBucket 5.5.0

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

423 views 5 9
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you