Confluence 7.6 Upgrade Notes

Here are some important notes on upgrading to Confluence 7.6. For details of the new features and improvements in this release, see the Confluence 7.6 Release Notes

On this page:

Upgrade notes 

Unlocking Data Center potential

When clustered, Confluence generally uses a distributed cache, which means data is evenly partitioned across all the Confluence nodes in a cluster, instead of being replicated on each node.

In order to improve cluster resilience, and unlock further horizontal scaling capabilities, we have switched some specific caches to local caching with remote invalidation. 

The default cache configuration in Confluence is still a fully-distributed cache, so these changes should not affect your plugins.

Changes to mobile login 

The Confluence Server mobile app needs to check that you're running a compatible version of Confluence before it can log your users in. If you've configured a custom filter in your VPN or firewall to prevent unauthenticated requests to your server, Confluence can't perform this check. Previously the solution was to allow <confluence-base-url>/server-info.action  and several headers and cookies.

From Confluence 7.6, you will only need to allow <confluence-base-url>/rest/nativemobile/1.0/info/login.  

See 'Can't check compatibility' error in the Confluence Server mobile app and Problems with logging in because of missing headers or cookies for more information. 

Upgrading from 6.3 or earlier

If you are upgrading from Confluence 6.3 or earlier, there's a known issue where spaces do not appear in the space directory. You'll need to reindex your site after upgrading to fix this. 

End of support announcements

No end of support announcements at this time. 

Infrastructure changes 

Head to Preparing for Confluence 7.6 to find out more about changes under the hood. 

Known issues

If you encounter a problem during the upgrade and can't solve it, please create a support ticket and one of our support engineers will help you.

Upgrade procedure

Note: Upgrade to a test environment first. Test your upgrades in your test environment before rolling them into production.

If you're already running a version of Confluence, please follow these instructions to upgrade to the latest version:

  1. Go to > Support Tools > Health Check to check your license validity, application server, database setup and more.
  2. Before you upgrade, we strongly recommend that you back up your installation directory, home directory and database.
  3. If your version of Confluence is earlier than 7.5, read the release notes and upgrade guides for all releases between your version and the latest version.
  4. Download the latest version of Confluence.
  5. Follow the instructions in the Upgrade Guide.
  6. Use the Confluence Post-Upgrade Checks to ensure that everything works as expected.

Update configuration files after upgrading

The contents of configuration files such as server.xml, web.xml , setenv.bat / setenv.sh and confluence-init.properties change from time to time. 

When upgrading, we recommend manually reapplying any additions to these files (such as proxy configuration, datasource, JVM parameters) rather than simply overwriting the file with the file from your previous installation, otherwise you will miss out on any improvements we have made.

Last modified on Jul 1, 2020

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.