Hipchat Data Center release notes

Welcome to the Release Notes! Here, you'll find all the latest news about new Hipchat Data Center features, functionality, changes and bugfixes.

Before you upgrade...

If you're deploying Hipchat Data Center for the first time and are migrating from a previous version of Hipchat Server, use the instructions in the Hipchat Server to Hipchat Data Center migration guide to export your old data, deploy, and import the data to the new deployment.

On this page:

The update channels represent different software update sources. We first release software to the  Beta Channel  and if it performs well for many sites we may promote it to the  Production Channel  with well defined  Known issues . 

Hipchat Data Center 3.1.2 - December 6th 2017 - Production channel

Promoted to the Production channel 14th December, 2017.

This release contains new features, changes, and bug and security fixes.

Remember to use the instructions at Upgrade Hipchat Data Center to a new version to upgrade.  


New Features

  • We're now publishing our AWS AMIs in eu-central-1 ! Willkommen, bienvenue, welcome! (You can always see a list of which AWS regions we support by visiting the Supported Platforms page.)
  • You can now view your current Hipchat license from the web UI when you're logged in as an administrator.

Changes and Fixes

  • We updated Hipchat's internal authentication system. This shouldn't affect you at all.
  • We updated the macOS client that ships bundled with the Hipchat nodes for local download by users. The updated client contains a fix for the 22nd Nov 2017 Hipchat Security Advisory.
  • We also made some security fixes to the webcore library used in the web version of the Hipchat client (which is available through the web UI). This includes fixes to address the 22nd Nov 2017 Hipchat Security Advisory.
  • HCPUB-3507 - Getting issue details... STATUS  
    We fixed an issue that caused usernames (which are the user's email address) to be case-sensitive. This meant that for a short period, the usernames
    hello@example.com and Hello@example.com  were treated as totally different users.
  • We fixed an issue that could sometimes prevent Hipchat nodes from detecting when a user's chat session had ended, leading to inaccurate presence notifications and other problems. Hipchat now checks more aggressively to see if users are online, and refreshes presence status more quickly.
  • Logs from the internal authentication service and web frontend are now correctly stored in /var/log/hipchat, and are rotated along with the other logs.
  • We fixed a permissions issue that could prevent you from downloading a diagnostics bundle from a URL on the server.

Known Issues

  • If you're using retention settings, the database does not successfully delete chat messages that have passed your organization's retention limit. A workaround is available for deployments for whom this functionality is essential, please Contact Hipchat Data Center Support for more information.
  • HCPUB-3726 - Getting issue details... STATUS
    In version 3.1.1 and later, Hipchat does not mount its NFS share correctly after a reboot. To work around this, you can manually mount the NFS share using the instructions in this linked public ticket. 

Hipchat Data Center 3.1.1 - September 29th, 2017

Promoted to Production on 23rd October, 2017.

This release is a bump version that supersedes Hipchat Data Center 3.1.0 Beta, released September 26th, 2017.

Remember to use the instructions at Upgrade Hipchat Data Center to a new version to upgrade. 


This release contains all of the features and changes noted in 3.1.0.

This release also corrects a file share permissions issue introduced in version 3.1.0. The upgrade to version 3.1.1 corrects the file issue, and no extra administrator action is needed.

Known Issues

  • HCPUB-3507 - Getting issue details... STATUS  In version 3.0.0 through 3.1.1, usernames (email addresses) are case-sensitive. If users attempt to log in with a different capitalization than the one found in your organization's user directory, they will not be able to log in. If you are manually creating user accounts, you should check in the user list that the user doesn't already exist with in different case before creating a new user.
  • HCPUB-3726 - Getting issue details... STATUS
    In version 3.1.1 and later, Hipchat does not mount its NFS share correctly after a reboot. To work around this, you can manually mount the NFS share using the instructions in this linked public ticket. 

Hipchat Data Center 3.1.0 - September 25, 2017 

This Beta version was superseded by version 3.1.1 without being promoted to the Production channel.

This release contains our improved Hipchat Data Center setup wizard, and some stability and security updates.


  • You now configure new Hipchat Data Center deployment using a web-based setup wizard - no more running CLI commands! The wizard also helps validate your configuration as you go, so setup is clearer and smoother.
    (Are you a bash master? Did you like using the CLI? Don't worry, you can still use the hipchat configure command if you want to. Just check your configuration.json file against the updated documentationas  the allowed properties have changed.)
  • We're now publishing our Hipchat Data Center AMIs in  us-east-1! Welcome, mid-Atlantic friends!


  • If you're using the AWS CloudFormation template, the template no longer requests a license during configuration. I nstead, you can use the command line tool (hipchat license -i path/to/file ) or you can browse to the setup wizard once the cluster is running and apply the license from there.
  • We improved some error and log messages. Hopefully you won't ever see these, but if you do they should be easier to understand.
  • We updated the internal web server.  This change shouldn't affect you at all.

Known Issues

If you are upgrading to Hipchat Data Center from version 3.0.1 and earlier, you will have to reapply your license to each upgraded node before proceeding. The instructions in View or Update your Hipchat Data Center license will do the trick. The license is stored in the data stores node in 3.1.0 and later, so you won't have to do this again (unless you upgrade or change your license tier). 

Hipchat Data Center 3.0.1 - July 19, 2017

Promoted to Production channel August 14th, 2017.

This is a bugfix release. No new big features, just improvements!

Remember to use the instructions at Upgrade Hipchat Data Center to a new version to upgrade.

If you are deploying this version, you must use the configuration file method, which was superseded by the setup wizard in version 3.1.0. You may also need to use the CLI command to find your Server ID if you're requesting a new license.


  • The hipchat datacenter selfcheck  CLI now validates that the Hipchat nodes can be resolved by their DNS entires.
  • When an administrator removes an emoticon, it now stays removed even after you upgrade. No more deja-vu!
  • We made some internal improvements and simplifications which shouldn't affect you at all.

    • Simplified our configuration files and removed unused ones.
    • Improved how the internal authentication system stores and accesses records.
    • Removed some unused and duplicate log files.


  • We resolved an issue that prevented admins from deploying a Hipchat OVA on vSphere version 6.5.   HCPUB-3277 - Getting issue details... STATUS
  • We fixed an issue that could prevent a small subset of users from logging in to a deployment using SAML and Just In Time (JIT) user provisioning.
  • We fixed an issue with Crowd schema creation that could prevent Hipchat Data Center from restarting correctly.  HCPUB-3268 - Getting issue details... STATUS

Known Issues

If you are deploying Hipchat Data Center 3.0.1 or earlier, you can only use the configuration file method to deploy your server, and you'll require two additional keys in your configuration.json file. These extra keys are listed below the list of keys, and are not included by default in the example configuration file.

Hipchat Data Center 3.0 - June 22, 2017 - Generally Available

The Hipchat Server and Data Center team is thrilled to announce the release of the first Generally Available, production version of Hipchat Data Center.  If you already have a Hipchat Server, Atlassian Stack, or ELA license, you can use the existing license to deploy a Hipchat Data Center cluster. If you don't have an existing license, you can request evaluation license

New features

  • You can now deploy Hipchat Data Center as a cluster with multiple Hipchat nodes to provide high availability and scale improvements. If you don't need either of these things, you can also deploy a single-node Hipchat Data Center cluster. See the Deployment options and sizing guidelines for Hipchat Data Center and the Configuration requirements for Hipchat Data Center for more information.
  • The Hipchat web UI that was unavailable in the Beta versions of Hipchat Data Center has been replaced and improved. The UI now uses a left sidebar navigation, and the administrative screens have been sorted and re-grouped to make it easier to find the controls you're looking for. 
  • The Hipchat Data Center administrative UI also now contains a System status informational page, which includes information about the running Hipchat node or nodes, and the general statistics about system utilization.
  • Hipchat Data Center now uses a High Availability release of Crowd internally for user directory management.


Known issues

  • Importing a large Hipchat data archive might be slow. If your archive has more than 5 million messages  contact Hipchat Support before you begin.

Last modified on Dec 20, 2017

Was this helpful?

Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.