404 Oops, you've found a dead link, after JIRA update to 7.4.3

Question

Version7.4.3Build Number74005Build DateMon Aug 21 00:00:00 EDT 2017Build Revisiond9f4f070125e6f53d367dd8169afdb727b8e7897Atlassian Partner Installation TypeStandalone

Health Check Fails, cannot even run it because of the dead link!

Can''t do anything after the recent update to 7.4.3 without getting an OOPS error.

Stopped Jira. deleted the .bundled-plugins and .osgi-plugins directories, restarted JIRA. all to no avail.

Still broken links everywhere. Now,  I wish I would nowhave updated because it was working fine before the update.

Desperately need help.

Andy Heinzer · Answer

These files exist in the $JIRAINSTALL directory.  Any file in that path can be altered by an upgrade.

Douglas Gaskell · Answer

This was my problem upgrading to 7.11.x, along with all my other proxy settings being cleared on upgrade. Why is Jira doing this?

Andy Heinzer · Answer

We found in a support case that the JIRAINSTALL/conf/server.xml file appears to have been changed or reverted to the default values. However in this case, Elicia's Jira instance was being accessed on a context path of http://hostname:8080/jira/ The problem here is that since Jira's Tomcat instance was not defined at the time to server Jira in the context of that '/jira/' path, the site did not load as expected in some browsers. What was strange here was that other browsers did not appear to have this problem, and the logs in Jira did not clearly show any errors in regards to Jira not working as expected. In that server.xml file, it looked like this: And we changed it to this: Once you make that change and save your changes, you will need to restart JIRA for your changes to take effect.