It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Hi,
I have been reading a lot of posts regarding how to change the Base URL but as I am quite new to this I allow myself to ask (to be on the safe side)
We have Confluence and JIRA installed on https://dev.<company>.com/confluence and https://dev.<company>.com/jira
We want to change the URL's to https://wiki.<company>.com and https://jira.<company>.com
As far as I can understand this is what I need to do. Correct?
Do I need to edit the bandanakey aswell or would step 2 take care of that?
Thanks in advance!
Rgds
Thomas
That looks right to me, you do not need to mess with databases or anything like that. DNS and the base url via the admin GUI are enough.
Except... if you have used application links, you'll want to update those as well (again via the gui). And any other applications that are pointed to JIRA or Confluence.
Unfortunately I ran into some issues trying to do this now. I changed base url and removed application links between the two servers before starting. I also changed server.xml from the old to the new as shown below. When trying the new link https://wiki.<company>.com I just received a 404 from the old address https://dev.<company>.com/confluence (same for jira). We are using a Netscaler frontend which routes calls to our Nginx. Nginx has also been edited to reflect the change but no success I am afraid. Suggestions much appreciated.
<Server port="8000" shutdown="SHUTDOWN" debug="0"> <Service name="Tomcat-Standalone"> <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="8090" minProcessors="5" maxProcessors="75" enableLookups="false" redirectPort="8443" acceptCount="10" debug="0" connectionTimeout="20000" SSLEnabled="false" scheme="https" secure="true" proxyName="dev.<company>.com" proxyPort="443" useURIValidationHack="false" URIEncoding="UTF-8"/> <Engine name="Standalone" defaultHost="localhost" debug="0"> <Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="false"> <Context path="/confluence" docBase="../confluence" debug="0" reloadable="false" useHttpOnly="true"> <!-- Logger is deprecated in Tomcat 5.5. Logging configuration for Confluence is specified in confluence/WEB-INF/classes/log4j.properties --> <Manager pathname="" /> </Context> </Host> </Engine>
<Server port="8000" shutdown="SHUTDOWN" debug="0"> <Service name="Tomcat-Standalone"> <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="8090" minProcessors="5" maxProcessors="75" enableLookups="false" redirectPort="8443" acceptCount="10" debug="0" connectionTimeout="20000" SSLEnabled="false" scheme="https" secure="true" proxyName="wiki.<company>.com" proxyPort="443" useURIValidationHack="false" URIEncoding="UTF-8"/> <Engine name="Standalone" defaultHost="localhost" debug="0"> <Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="false"> <Context path="" docBase="../confluence" debug="0" reloadable="false" useHttpOnly="true"> <!-- Logger is deprecated in Tomcat 5.5. Logging configuration for Confluence is specified in confluence/WEB-INF/classes/log4j.properties --> <Manager pathname="" /> </Context> </Host> </Engine>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Found the error. I also had to edit this parameter in confluence.cfg.xml
<property name="confluence.webapp.context.path">/confluence</property>
When changed to
<property name="confluence.webapp.context.path">/</property>
it all works
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.