Hipchat Server Release Notes

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.

Before you upgrade...

  • Remember to create a backup before you upgrade, either with a virtualization snapshot or using a data backup/export. See Back up and restore Hipchat Server for more details.
Upgrading from Hipchat Server 1.3 or older?

If you're upgrading from Hipchat Server 1.3 or older, you'll need at least 5GB of free disk space on the root partition. The upgrade will take at least 60 minutes to complete, and will require a reboot once it completes.

If you're having trouble upgrading from 1.3, you may need to upgrade from the command line using

hipchat upgrade --force-upgrade
Upgrading from Hipchat Server 1.4.x?

Upgrades from Hipchat Server 1.4.0 - 1.4.2 requires you to run some extra command line steps before you upgrade.


wget https://s3.amazonaws.com/hipchat-server-stable/utils/chat-113.tar.gz
tar -zxvf chat-113.tar.gz
cd chat-113 && sudo dont-blame-hipchat -c './install.sh'
 

Then, run hipchat upgrade --upgrade as usual.

If you're having trouble upgrading from the web UI, we recommend upgrading using the CLI instead.

Upgrading to 2.1.3 or later for the first time?

Hipchat Server version 2.1.3 retires an older video chat solution called AddLive, and replaces it with Hipchat Video. Users may need to disconnect and reconnect, or perform other troubleshooting steps to properly accept these changes.

In particular, macOS users may need to completely log out: see the related Hipchat Knowledge Base article for more details.

Other clients may also require troubleshooting. See version 2.1.3 Known Issues for details.

Upgrading from v2.2.7 or earlier? Worried about Meltdown and Spectre?

Versions 2.2.8 and later include changes in the underlying Ubuntu binaries which address the Meltdown and Spectre vulnerabilities. (You can read more in general about Ubuntu security releases here.)

To complete this upgrade, you must reboot your server to apply the changes. You will need to schedule the appropriate downtime for production deployments.

During this upgrade, you might see some No such file or directory warning messages in the console log. These messages can be safely ignored.


Good to know:

  • If your upgrade fails with a "Mismatch of expected sha512sum" error, your upgrade binary may be out of date, corrupted, or might have only been partially downloaded. See the related Hipchat Knowledge Base article for more information.
  • After the upgrade completes, the system's ssh welcome text will show an older version until you reboot. To check the build and version number without rebooting, look for the version number in the file at /etc/hipchat-release .
  • During the upgrade and reboot processes the system monitor (monit) might send service restart emails. You can safely ignore them.
  • The Hipchat iOS app requires iOS 9 or later to enable SAML single sign-on.

Looking for Hipchat Server 2.3 or Hipchat Data Center beta?

The most recent stable release of Hipchat Server is below. If you're looking for Hipchat Server v 2.3.0 or 2.3.1, those were beta releases of Hipchat Data Center and are no longer available, but you can read their historical release notes below. 

Hipchat Data Center is now out of beta, so if you want to deploy it, check out the Hipchat Data Center deployment guides!

ℹ️   Read the old Hipchat Data Center BETA release notes

Hipchat Server 2.3.1 - May 17, 2017 - Beta Channel

This release is a minor version change that improves functionality introduced in Hipchat Data Center - BETA. (The OVA SHAs usually found in these release notes have been updated in the Beta documentation.)

Existing Hipchat Server deployments should not upgrade to this Beta version. Install this version as a separate deployment only.

New SAML settings

You can now override the default SAML attributes used by Hipchat to create user accounts. Look for these new fields in the SAML authentication settings screens.

Changes

  • We fixed an issue that prevented some SAML authentication source providers from connecting to Hipchat Data Center.
  • We updated the version of PHP that ships with Hipchat to v5.5, and updated all of our third-party packages that had security updates, including libssl.

Known Issues

(warning)  As in version 2.3.0, there is no upgrade path for this Beta version of Hipchat Data Center. Install this version as a separate testing deployment only.

Hipchat Server 2.3.0 - May 3, 2017

This release is a minor version change that introduces functionality for Hipchat Data Center - BETA.

Existing Hipchat Server deployments should not upgrade to this Beta version. Install this version as a separate deployment.

Changes

  • A new hipchat datacenter CLI command is now available for configuring nodes in a Data Center cluster.
  • The compressed files created by log rotation now use a timestamp in the filename.
  • The BOSH service's performance and memory consumption have been improved.
  • Fixes  HCPUB-2767 - Getting issue details... STATUS  and related issue  HCPUB-2319 - Getting issue details... STATUS .
  • We've made some changes to how messages and server configurations are stored, but they shouldn't affect you at all.

Hipchat Server 2.4.3 - October 25th, 2018 - Production channel

Published to Production channel on 25th of October 2018


Compatibility Warning: 2.3.x -> 2.4.2

2.3.x versions of Hipchat Server cannot be upgraded to version 2.4.3.

The HCS 2.3.x versions were a beta version of Hipchat Data Center, and as such contained architectural changes which are not compatible with the 2.4.3 version.

Reboot required

This version includes changes in the underlying Ubuntu binaries. To complete the upgrade, you must reboot your server to apply the changes. Be sure to schedule the appropriate downtime for production deployments.

Binaries

New Feature - Changes to License Counts

In version 2.4.3, we've changed how we count the number of people using your Hipchat instance towards your license.

Previously, all users synchronized from your authentication system into our internal directory were counted towards your license count. This lead to some difficulties with directory filtering rules, and a long list of possible users when starting a new chat or @-mentioning someone.

If you're upgrading to 2.4.3, we'll count all existing synchronized users towards your license count, so that everyone who used the service before can continue to use it without any changes to who they see in the "new chat" or @-mention lists. You can manually disable or remove some of these synchronized users if you need to free up seats on your license. When you add new users, they'll only count towards the license once they log in to Hipchat.

Changes

  • We’ve updated the Linux kernel on the appliance to use the Ubuntu LTS enablement stack.
  • We've improved performance and stability of the internal authentication system in case of big directories synchronization.

  • We've updated the internal authentication system.

  • We've updated several third-party libraries for security purposes.

Known Issues

  • You will need to reboot to apply this upgrade.
  • The unread state known issues from v2.2.7 (below) still apply.
  • The  'hipchat upgrade' command displays 'InsecurePlatformWarning'. This does not impede the upgrade functionality. HCPUB-29257 - Getting issue details... STATUS

Hipchat Server 2.4.1 - September 4th, 2018 - Production channel

Published to Production channel on 4th of September 2018


Compatibility Warning: 2.3.x -> 2.4.1

2.3.x versions of Hipchat Server cannot be upgraded to version 2.4.1.

The HCS 2.3.x versions were a beta version of Hipchat Data Center, and as such contained architectural changes which are not compatible with the 2.4.1 version.

Reboot required

This version includes changes in the underlying Ubuntu binaries. To complete the upgrade, you must reboot your server to apply the changes. Be sure to schedule the appropriate downtime for production deployments.

New Features

  • We added support for Mutual Authentication / Assertion Encryption to Hipchat Server's SAML implementation.
      HCPUB-2725 - Getting issue details... STATUS
  • We added an option on the SAML configuration screen to force users to always authenticate with SAML even if the web browser or Hipchat application has a valid IDP session.
  • We added an option to limit the number of months of rooms and 1:1 messages history exported to both Hipchat CLI and Hipchat administrator interface.
  • We added support for a new Amazon EC2 instance type - c5.

Fixes

  • The users with expired sessions in single sign-on only setup are no longer redirected to internal login page.
    HCPUB-3599 - Getting issue details... STATUS
  • We fixed an issue that prevented automatic storage up-scaling from working in some scenarios.
    HCPUB-2798 - Getting issue details... STATUS
  • The users no longer get erroneous invite messages during some data imports.
  • We bundled the latest version of the Windows client.
  • Special symbols in attachment file names no longer prevent room history from loading.

    HCPUB-5393 - Getting issue details... STATUS
  • The users with a single character in their domain name are now correctly synchronized from external directory.
    HCPUB-10994 - Getting issue details... STATUS
  • The uploading of .zip archives with multiple emoticons is now handled correctly.

Changes

  • We updated the internal authentication system.
  • The export process memory utilization was improved.
  • We updated the underlying Ubuntu 14.04 binaries to include updates and security fixes.

Known Issues

  • You will need to reboot to apply this upgrade.
  • The unread state known issues from v2.2.7 (below) still apply.

Hipchat Server 2.4.0 - May 10th, 2018

Promoted to Production on 23rd of May, 2018.

tip/resting Created with Sketch.

Hipchat Server 2.4.0 - extended life

This version contains stability fixes and changes to increase the longevity of Hipchat Server deployments. Because this is a new major version, this extends the EOS date for Hipchat Server to two years from May 10th 2018.

Compatibility Warning: 2.3.x -> 2.4.0

2.3.x versions of Hipchat Server cannot be upgraded to version 2.4.0.

The HCS 2.3.x versions were a beta version of HipChat Data Center, and as such contained architectural changes which are not compatible with the 2.4.0 version.

Reboot required

This version includes changes in the underlying Ubuntu binaries. To complete the upgrade, you must reboot your server to apply the changes. Be sure to schedule the appropriate downtime for production deployments.

New Features

  • We added an option that gives administrators more control over how notifications are displayed. This is useful for deployments that have privacy concerns. Administrators can now choose to display message text for both email and mobile push notifications, to hide the text for both email and push, or to show the message text for email notifications but remove it from push notifications.

    HCPUB-813 - Getting issue details... STATUS

  • We made some changes to our Redis stores to improve data recovery in the event of a failure.

Fixes

  • We fixed an issue that could sometimes prevent user sessions cleanup from running correctly.

    HCPUB-3104 - Getting issue details... STATUS

  • Fixed an issue that could sometimes prevent users from seeing a room they'd just been invited to when the invitation was made by APIv2 call.

    HCPUB-3431 - Getting issue details... STATUS

  • The hipchat email -r  command now correctly resets the password for the current Hipchat administrator, rather than the password for the first and original administrator.

    HCPUB-3079 - Getting issue details... STATUS

  • We fixed an issue that could prevent the ownership of a Hipchat Server instance from being transferred to another user.

    HCPUB-2622 - Getting issue details... STATUS

  • The hipchat network --t command now works correctly on AWS deployments.

    HCPUB-3029 - Getting issue details... STATUS

  • We fixed an issue that could prevent a user from being completely removed from a private room. Users who have been removed from a room no longer appear on the room's user list, and their access to the room history is correctly revoked.

    HCPUB-3432 - Getting issue details... STATUS

  • The file uploader now correctly ignores the DATA LINK ESCAPE character if it's accidentally included in a file name.

    HCPUB-5393 - Getting issue details... STATUS

  • The Customer Agreement and Privacy Policy links on the signup page now go to the correct URL.

    HCPUB-3793 - Getting issue details... STATUS

  • We removed duplicate monitoring on the Punjab TCP port.
  • We fixed an issue that prevented a headers in error messages from being correctly escaped.
  • We fixed an issue with our internal authentication system that could sometimes cause a NullPointerException while it was synchronizing with an external directory.
  • We added more reporting to the Hipchat runtime.log to help us better troubleshoot and support your deployments.

Changes

  • We updated the underlying Ubuntu 14.04 binaries to include updates and security fixes up to kernel revision 3.13.0-147.

  • We removed unused Docker modules from the Hipchat OVA and AMIs.
  • We removed some unused modules.
  • We updated the library we use in our emoticon shrink-ray to use a more secure framework.
  • We removed some outdated components for security purposes.

Known Issues

  • You will need to reboot to apply this upgrade.
  • The unread state known issues from v2.2.7 (below) still apply.

Hipchat Server 2.2.9 - January 23rd, 2018

Promoted to Production on 23rd January 2018.

This release contains fixes, and supersedes the 2.2.8 Production release.

Reboot (maybe) required

If you are updating from v2.2.7 or earlier, this version includes changes in the underlying Ubuntu binaries. To complete the upgrade, you must reboot your server to apply the changes. Be sure to schedule the appropriate downtime for production deployments.

(If you're upgrading from v2.2.8, no reboot is required.)

Last modified on Oct 30, 2018

Was this helpful?

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