_applinks_recent_upgrade
If your application links have stopped working after a recent upgrade it's possible that your customizations to the application's server.xml file were overwritten. Custom changes can include reverse proxy configuration and HTTPS configuration. You should check that the upgraded server.xml file matches the pre-upgrade server.xml.
The location of your server.xml file depends on your application, operating system, and installation location.
Common default installation locations for Atlassian applications are:
- Linux:
/opt/atlassian/<application-name> - Windows:
C:\Program Files\Atlassian\<application-name> - Windows:
C:\Atlassian\<application-name>
Locations in Atlassian application's folder structure:
| Application | server.xml location |
|---|---|
| Bamboo | <install-path>/conf/ |
| Confluence | <install-path>/conf/ |
| Crowd | <install-path>/apache-tomcat/conf/ |
| Crucible | As for Fisheye. |
| Fisheye | The Fisheye configuration file is config.xml, see Configuring the Fisheye web server and How to enable Fisheye/Crucible to listen to web requests on additional ports. |
| JIRA applications | <install-path>/conf/ |
| Bitbucket Server 5.0 | N/A, replaced by Please read through Migrate server.xml customizations to bitbucket.properties |
| Bitbucket Server 4.0 – 4.14 | <Bitbucket home directory> /shared/server.xml |
| Stash 3.8 – 3.11 |
If you are on any of these later releases but your We recommend that you copy |
| Stash 3.7 and earlier | <install-path>/conf/ |
<install-path> refers to where the application was installed on your system.