Forums

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

Change base URL

Hannah Groseclose
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!
March 13, 2018

Hi all, 

So I recently installed Confluence 6.7.2 on Windows Server 2012 R2. Setup went fine but I'm hitting a roadblock attempting to change the Base URL for the product. When the base URL is changed from http://localhost:8090 to a FQDN like http://wiki.companyname.com, I'm not able to access the site from any browser internally.

I've created an internal A record for the site such that wiki.companyname.com points to the internal IP of the associated server and I still can't reach the site. Anything I'm missing here? I thought it would be as easy as changing baseURL in the product and then creating a DNS A record.

Thanks, 

Keith

1 answer

1 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 13, 2018

Does your DNS also map the port?  If not, then try http://wiki.companyname.com:8090 .  You'll probably need to check all the firewalls and network routing too - try a tracert to the FQDN to check if you can get there.

Hannah Groseclose
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!
March 13, 2018

Nic, 

Thanks for the quick reply. That was the trick to fix it, can't believe I missed something so simple. lol. Need more coffee :) Now to do some research to change the listening port and I should be good to go. 

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 13, 2018

You can persuade the Tomcat to run on port 80 (or 443 for https), which will make it work as almost every browser will make that assumption by default, based on the protocol!

However, it's generally better to use a proxy.  Apache, Nginx, Lighttpd etc can all take an incoming "port 80" and proxy it to "your confluence:8090" - it's easier to configure, keeps the proxy and Confluence server updates separate and independent, and allows you to run several services on different ports as part of the same site or as subdomains.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events