Atlassian public facing

Phil Jackson October 19, 2016

Hello,

I am looking to possibly separate my Atlassian systems on their own servers, but I need to figure out how to be able to allow the localhost:7990 to be able to be publicly faced as bitbucket.companynamt.com. Can anyone point me to the right article, on what I need to do fo certs, and having the tomcat allow that to be read properly? Or should I use IIS?

2 answers

0 votes
Phil Jackson October 20, 2016

I tried the IIS way, and I have everything setup, but for some reason, when I go to the link it doesn't do anything. Just shows blank page. internally, I can go to the link but with port number added at the end, and it then gives me an error that the url is being directed to the wrong port. These are the settings I have set for JIRA

 

<Service name="Catalina">

<Connector port="8080"

maxThreads="150"
minSpareThreads="25"
connectionTimeout="20000"

enableLookups="false"
maxHttpHeaderSize="8192"
protocol="HTTP/1.1"
useBodyEncodingForURI="true"
redirectPort="8443"
acceptCount="100"
disableUploadTimeout="true"
proxyName="bitbucket.domain.com" proxyPort="80" scheme="http"/>

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 21, 2016

That looks correct on the Tomcat side, so the problem is something in IIS.  I don't know IIS well enough to guide you outside what the documentation says.

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 20, 2016

The usual way to do this is to use a proxy.  You expose the proxy to the internet and then tell it to route traffic back to your internal servers.  In theory, you could just allow Tomcat onto the internet, but proxies have many advantages (e.g.  routing everything through a standard port, allowing multiple applications to run under one url, better logging, caching etc etc etc)

Generally, you find people use Apache to do this, although Nginx is popular too.  See https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-apache-http-server-mod_proxy_http-806032611.html   If you're not familiar with them, or prefer IIS,  then IIS can do the same - see https://confluence.atlassian.com/kb/proxying-atlassian-server-applications-with-microsoft-internet-information-services-iis-833931378.html


I
usually recommend that you get the http side working first

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events