Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Context changed after Confluence upgrade

Ben Daniels June 3, 2014

We recently upgraded Confluence. We have done this in the past and are running the EAR/WAR version. We went from version 5.1.2 and stepped through the path and guide up to version 5.5.2

The issue arose when we first moved to version 5.2.0, and when we attempted to access Confluence only had a blank white screen. I searched and found existing references to a "context error".

The original URL was http://confluence.x.x/dashboard.action to land, now you need to manually add a "/confluence" so it ends up being http://confluence.x.x/confluence/dashboard.action

Since we're running under Tomcat I've adjusted the confluence.xml file under our Catalina/localhost and the path="" (so, no context path)

This was working prior to our upgrade. Has anyone encountered this scenario before? I'm really hesitant to change the context path or the Base URL because we have Confluence highly integrated with our JIRA instance.

Thanks.

1 answer

1 accepted

0 votes
Answer accepted
William Zanchet [Atlassian]
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.
June 4, 2014

Hi Ben,

This problem happened, because the context path is held by server.xml from the installation folder. Once you do the upgrade, you'll not use the old install folder, so it will replace from a brand new one. So everytime you need to bring your server.xml that is located in the <install-folder>/conf folder. That way your context path configuration will go with it.

Cheers,

WZ

Ben Daniels June 9, 2014

Thanks William! That did the trick.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events