Hi
I have installed Jira Software, Bigbucket and Confluence on our Windows Server 2012 R2 Essential. Now these products / services are using URLs:
http://server-name.our-internal-domain.local:8080
http://server-name.our-internal-domain.local:7990
http://server-name.our-internal-domain.local:8090
Is there a way(s) to set them to use URLs and the default TCP port 80 like:
http://jira.our-internal-domain.local
http://bitbucket.our-internal-domain.local
http://confluence.our-internal-domain.local
or make them like
http://atlassian.our-internal-domain.local/jira
http://atlassian.our-internal-domain.local/bitbucket
http://atlassian.our-internal-domain.local/confluence
For your information, our computers' DNS is set to a DNS service running internally. I can add or change the DNS settings.
Regards
Harry
A better procedure to setup reverse proxy on IIS:
Proxying Atlassian server applications with Microsoft Internet Information Services (IIS)
After this is done, the HTTP URLs below are working fine. The Application Links between them are working as well.
http://jira.our-internal-domain.local
http://bitbucket.our-internal-domain.local
http://confluence.our-internal-domain.local
We use our internal CA to sign the SSL certificates for these three Atlassian Applications Web Portals. I follow this web page below to import our CA certificate into the Java CA Store.
Gadgets do not display correctly after upgrade to JIRA 4.0
Only one problem, I need to find out which Java version / installation that these Atlassian Applications are actually running on. It could be the Java version that is installed on the server, or the one bundled with the Atlassian Application. For Jira and Confluence, I can find it by looking at the java.home System Property in the System Info page in the Settings. But I could not find this information in the Bitbucket's Settings. I have both JDK and JRE installed on our server. I import our CA certificate into both versions' CA Stores. All the HTTPS URLs are working fine. Recreate the Application Links using the HTTPS URLs. The new links are working as well.
Both of your naming schemes are not only possible, but fully supported.
Given that, the question becomes what tech you'd prefer to use to do it. For most people I've worked with, the best answer is "do it with a proxy". The standard config I can do from memory is an Apache proxy doing https://<domain>/<application> but there's not a lot of work to do https://<application>.<domain>. Proxies are the best option because it's "get SSL working once, and each application becomes a handful of lines of config".
You can also do it at the Tomcat level - get the various Tomcats to serve the applications on the right urls, but this is more fiddly and probably fragile.
As a windows estate, I'd ask your people what scheme they would prefer and then set up IIS as a proxying front-end to the (mostly) off-the-shelf Tomcats.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you, Nic. I have successfully setup reverse-proxy on IIS for Jira by following the procedure in https://techcommunity.microsoft.com/t5/iis-support-blog/setup-iis-with-url-rewrite-as-a-reverse-proxy-for-real-world/ba-p/846222
Now I can use http://jira.our-internal-domain.local to access it. But it comes up with an a potential problem "Dashboard Diagnostics: Mismatched URL Hostname". It also provides some links for the solutions.
The following articles describe the issue and the steps you should take to ensure that your web server and app server are configured correctly:
Is there an easier way to fix the problem?
I have setup Application Links between Jira, Confluence and Bitbucket. Do I need to change the Application URL and Display URL in each link?
Regards
Harry
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Three things I'd want to look at here:
What is the base url set to in each application? For example, in Jira, is it set to http://jira.our-internal-domain.local ?
Have you started on any of the SSL configuration yet? Https config is usually easier to do if you get http right first and then do all the SSL config, ending with changing the base url to https last.
Your application links need to be using the base urls of the systems they will connect to. I tend to get the http link tested before I move on to https, as then I know the applications are set up right and it's the SSL I've messed up
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Our Windows Server 2012 has one internal IP address only. It has a few spare NIC adapters. If we need to add IP address, it would be better to have an approach that just uses one IP address for all Atlassian products / services.
Regards
Harry
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.