The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Additional HTTPS Port

IT Master
May 14, 2020

Hello,

actually we use Bitbucket with HTTP access (e. g. http://servername:7990) which is working fine but we want to add an additional HTTPS port for external access.

How we can do that? In this article it's only described for HTTPS only:

https://confluence.atlassian.com/bitbucketserver/securing-bitbucket-server-with-tomcat-using-ssl-776640127.html#SecuringBitbucketServerwithTomcatusingSSL-configuretomcat

At the moment if I try to access bitbucket using https://servername:8443 I get an error message that the webiste not available.


Thank you in advance!

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Jeremy Paltrow
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 19, 2020

Try using HAproxy to terminate your SSL and proxy to Bitbucket.

slitherio

0 votes
Dave Theodore [Coyote Creek Consulting]
Community Champion
May 14, 2020

You're going to have problems if you are trying to access Bitbucket via two URLs.  I would recommend not setting up your SSL in the method described in that doc either.  Rather, use HAproxy to terminate your SSL and proxy to Bitbucket. HAproxy can proxy TCP as well as HTTP, so you can use it to proxy your ssh connections, if you use that. You can also set up a redirect from http://servername:7990 -> https://servername in HAproxy.

DEPLOYMENT TYPE
SERVER
VERSION
7.1.0
TAGS
AUG Leaders

Atlassian Community Events