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.

Please remember to create a backup with a virtualization snapshot or data backup/export before attempting any upgrades.

Upgrades from HipChat Server 1.4.x require extra command line steps before upgrading.

HipChat Server 2.2.2 – March 9, 2017 - Production channel

Promoted from beta to production on March 9th, 2017.

This is a critical security update.

Deploying:

Changes: 

Known Issues:

  • Difficulties connecting from HipChat clients to HipChat Server may occur after upgrading to v2.2.2  HCPUB-2805 - After HipChat Server upgrade to 2.2.2, clients can no longer connect In Progress
  • iOS users will need iOS 9 or later if SAML single sign-on is enabled
  • Upgrades from HipChat Server 1.4.0 - 1.4.2 requires command line steps before upgrading:
  • If you're upgrading from HipChat Server version 1.3 or older:
    • you will need at least 5GB of free disk space on the root partition
    • it will take at least 60 minutes to complete, and will require a reboot afterwards.
  • The system monitor (monit) might send service restart emails during a service restart or upgrade; these can be safely ignored
  • The SSH welcome text will show an older version.
  • When having trouble: hipchat upgrade --force-upgrade

HipChat Server 2.2.1 – February 15, 2017

Promoted from beta to production on March 3rd, 2017.

Changes: 

  • Updated SSL configuration to only allow ciphers which support forward secrecy
  • Improved performance and memory consumption for the BOSH service

Known Issues:

  • iOS users will need iOS 9 or later if SAML single sign-on is enabled
  • Upgrades from HipChat Server 1.4.x require command line steps before upgrading:
  • If you're upgrading from HipChat Server version 1.3 or older:
    • you will need at least 5GB of free disk space on the root partition
    • it will take at least 60 minutes to complete, and will require a reboot afterwards.
  • The system monitor (monit) might send service restart emails during a service restart or upgrade; these can be safely ignored
  • The SSH welcome text will show an older version.

HipChat Server 2.2.0 – January 25, 2017

Promoted from beta to production on February 6th, 2017.


Happy New Year! To celebrate the start of 2017, we bring you SAML single sign-on for HipChat Server. You're welcome. 

Deploying:

Changes: 

  • You can now connect HipChat to a SAML 2.0 identity provider (including OneLogin and Okta) for user management and single sign-on. 

  • We've moved where you configure an external user directories (including Active Directory, Crowd and JIRA) to Group Admin > Authentication.

  • Upgraded linux kernel to 3.13 (kernel upgrades are not applied until the next system reboot)

Known Issues:

  • iOS users will need iOS 9 or later if SAML single sign-on is enabled.
  • The system monitor (monit) might send alert emails during a service restart or upgrade; these can be safely ignored
  • The SSH welcome text will show an older version
  • The web admin interface will show the older version until the upgrade is complete
    • This will take between 5 to 60 minutes (depending on server version that is being upgraded)
  • Upgrades from HipChat Server 1.4.0, 1.4.1, 1.4.2 require command line steps before upgrading:
    • 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'
      hipchat upgrade --upgrade
  • If you're upgrading from HipChat Server version 1.3 or older:
    • You will need at least 5GB of free disk space on the root partition
    • It will take at least 60 minutes to complete, and a reboot is required
    • It must be upgraded from the command line:
      • hipchat upgrade --force-upgrade

HipChat Server 2.1.3 – December 8, 2016

Promoted from beta to production on December 9th, 2016.

(HipChat.ova 4.9GB sha512sum f1585eb5786b5402390f85f838bfc0e9342e7bddd92b5e2493628c7493655b91f1e23c8b79f97921712828f6d51ded392bb137db79cff2cfce8cb8786562aa29)

HipChat Video is now in production! We're celebrating with a minor version number bump from 2.0.7 to 2.1.3. This release ends support for the old AddLive-based video service.

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

Changes: 

  • HipChat Video (group chat, desktop sharing) has replaced the older AddLive based video service
  • Fixed upgrade issue from 1.4.x that left curler services in a bad state.

Known Issues:

  • Upgrading to this release will rotate the SSH host keys
    • A host key validation error is expected the first time you SSH to an upgraded HipChat Server
  • If you're currently using AddLive, we'll switch you over to HipChat Video automatically
    • Users will need to restart their HipChat desktop clients before they can start a video chat
    • Some users may also need to log out of their client (and hit 'Forget this account' for OSX clients) then log back in to start a video chat
  • iOS 10 users may need to disable and re-enable notifications

  • In the iOS app, the Files list view will not open images if the app is configured to "open in HipChat" (i.e. not Safari)

  • The system monitor (monit) might send service restart emails during a service restart or upgrade; these can be safely ignored
  • The SSH welcome text, /etc/issue, will show an older version.
    • Refer to the file /etc/hipchat-release to check the build and release version.
  • Upgrades from HipChat Server 1.3 and older:
    • Will take at least 60 minutes to upgrade, some customers have reported hours
    • Require a reboot after the upgrade (for a new kernel and core libraries)
  • Some of our customers have reported issues when upgrading from HipChat Server 1.4.1 and 1.4.2  via the web UI. We recommend upgrading using the CLI instead.
  • Previous 1.4.x and 2.x versions attempting hipchat upgrade --check may incorrectly receive "The system is up to date", the workaround is to run hipchat upgrade --force-upgrade

HipChat Server 2.0 build 2.0.7 – November 8, 2016 - Production channel

Promoted from beta to production on November 16th, 2016.

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

Fixes:

  • Upgraded internal Atlassian Crowd to 2.10.  See Crowd 2.10.1 Release Notes  for more information.
  • Upgraded bundled android client to version 3.15.054.
  • TLS 1.0 fallback support has been removed.

Changes: 

Known Issues:

  • The system monitor (monit) will send service restart emails during a service restart or upgrade; these can be safely ignored.
  • The ssh welcome text will show an older version, until reboot.
  • Upgrades from HipChat Server 1.3 and older:
    • Will take at least 60 minutes to upgrade, some customers have reported hours.
    • Require a reboot after the upgrade (for a new kernel and core libraries).
  • Previous 1.4.x and 2.x versions attempting hipchat upgrade --check may incorrectly receive "The system is up to date", the workaround is to use hipchat upgrade --force-upgrade

HipChat Server 2.0 build 2.0.6 – October 11, 2016 - Production channel

(HipChat.ova 4.4GB sha512sum 473c2ed7454c15914eb324361fb883ca74b19862763ffcbf5c7bd1ca82377b0a61051013e7dd9468af119ce57f1720a6a12e8915de79a77d95402b7b159cbfc1)

Promoted from beta to production on October 17th, 2016.

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

Fixes:

  • Improved error messaging for the new HipChat Video
  • OpenSSL updated for two issues

Known Issues:

  • The system monitor (monit) will send service restart emails during a service restart or upgrade; those can be safely ignored
  • The ssh welcome text will show an older version, until reboot
  • Upgrades from HipChat Server 1.3 and older:
    • Will take at least 60 minutes to upgrade, some customers have reported hours
    • Requires a reboot after the upgrade (for a new kernel and core libraries)
  • Previous 1.4.x and 2.x versions attempting hipchat upgrade --check may incorrectly receive "The system is up to date", the workaround is to use hipchat upgrade --force-upgrade

HipChat Server 2.0 build 2.0.5 – October 5, 2016

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

New features:

  • Beta launch of our new video platform, HipChat Video. Read more about the announcement on our official blog. HipChat Video will replace AddLive Video. We will continue to support the AddLive Video service until the 17th of January, 2017.
    • New selection web UI at /server_admin/video allows selection of the default legacy AddLive-based video service, the new HipChat Video and, sadly, None to disable video
      • You need to select the new HipChat Video and sign out completely (clicking "forget this account" in OSX) in the HipChat clients to start using the new service
      • Desktop clients must be version 4.26 or newer to be compatible with HipChat Video
      • HipChat Video is a cloud service, and requires a working connection to the internet. See our system requirements page for more details.
    • Group video
    • Screensharing
    • Secure video sessions
    • Anonymous video session sharing
  • Updated HipChat Clients
    • OSX to 4.28.0-716 to fix reconnection issues and support HipChat Video 
      • HCPUB-1471 - Mac client can get stuck in Offline state after waking from sleep Closed
    • Windows to 4.27.1.1658

    • WebWeb to 4.29.0
  • Imports will now restore 1:1 notification messages

Fixes:

  • Fixed corruption of some user UTF8 user properties imported from AD and LDAP directories
  • https://blog.hipchat.com/2016/10/05/feels-good-man-emoticon-will-now-feel-better/
  • a bug from the 2.0.4 beta where trial licenses were not correctly working with Directory Integration 
    • HCPUB-1685 - Adding users from external directory fails when using evaluation license Closed
  • a bug where available updates would intermittently not appear when running "hipchat upgrade --check"

Known Issues:

  • The system monitor (monit) will send service restart emails during a service restart or upgrade; those can be safely ignored
  • The welcome text (/etc/issue) is not updated by the upgrade and will show an older version when logging in
    • Run cat /etc/release-hipchat or  at the command line to verify the running version
    • A reboot will update the issue text to report the correct version
  • Upgrades from HipChat Server 1.3 or older
    • Will take at least 60 minutes to upgrade, some customers have reported hours
    • Requires a reboot after the upgrade (for a new kernel and core libraries)

HipChat Server 2.0 build 2.0.4 – August 16, 2016

This release fixes a number of bugs, usability issues and incorporates several security fixes.

Note the build number has jumped from 1.0.x to 2.0.x to match up with the "HipChat Server 2.0" version number.

Scalability is enhanced by this release and includes a new web endpoint for the chat clients, known as the BOSH proxy, that can be optionally enabled at the command line. If you're experiencing interrupted chat sessions with thousands of users connected please consider using the new BOSH service. If the new BOSH proxy works well for many sites we'll make it the default in a subsequent release.

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

New features:

  • The Reset Password URL is now configurable in /admin/preferences  
  • Android and IOS mobile devices can now use the web chat client without having to install the HipChat application: https://<your HipChat server>/chat 
  • TLS 1.0 has been disabled for web access (port 443) 
  • The appliance customization example scripts in ~admin/startup_scripts/ have been updated

Fixes:

  • Fixed message uploads larger than 20MB for some upgraded systems 
  • Updated core components for security and reliability
    • Apparmor, libc, libexpat1, libnss3, libxml2, NTP, OpenJDK-7, OpenSSH, graphite2
  • Tuned the kernel network setting tcp_challenge_ack_limit to mitigate CVE-2016-5696
  • Improved web chat reliability at more than 4 thousand simultaneous user sessions

  • Upgrade failures due to an "lvm2" dependency error  

  • Fix for some upgrades that limited HipChat Server to only 100 emoticons  

  • Purging export archives now works as expected 

  • Improved push notification reliability 

  • Integrations preference "Only global admins" now behaves as documented

  • When a user directory (AD, LDAP, etc.) is offline HipChat will no longer report an incorrect password error

Known issues:

  • Upgrades from HipChat Server 1.0 (builds 1.3.9 or older) may prompt you to retry the upgrade with the following error message:
    •  ERROR during upgrade Your system appears to have been only partially upgraded, please ensure you have correctly configured your network or optional outbound proxy, and retry with "hipchat upgrade --force-upgrade" or contact server-support@hipchat.com"
    • If the above error is encountered, run: hipchat upgrade --force-upgrade as instructed
  • The hipchat upgrade --check and hipchat upgrade --show commands do not show the full version and release numbers
    • To view the build number run: cat /etc/hipchat-release

HipChat Server 2.0 build 1.4.3 – July 11, 2016

(HipChat.ova 4.6GB sha512sum dfb86421103015cc2bb8fbac35a336a8605b24890ad49ea2546b45d26e123c26d5319bfa257338cfa0ebf971447e61d32f6918f796767e8a70000f5b1b6f5946)

Promoted from beta to production on July 21st, 2016.

This is a minor update from Server 2.0 build 1.4.2. This is a major upgrade from older (pre 1.4.0) builds.

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

New features:

  • sha512 replaces md5sum as the checksum verification during the upgrade process

Fixes:

  • HCPUB-1045 - HipChat Server Chef run fails with 'Ran /etc/init.d/nginx start returned 1' Chef error Closed
  • HCPUB-1083 - Race condition in initial boot prevents login after HipChat Server setup Closed
  • An edge case upgrade bug when the 3rd party dependency libpam is upgraded

Known issues:

HipChat Server 2.0 build 1.4.2 – June 17, 2016 

(HipChat.ova 4.6GB sha512sum 454447af756211f940804d0e8bb6a73971bf49274ca2e68f8a8f6a5daee3b7fabd0d54c5ba152c26daa7999f8bfaeb2b0146aadc03e99304af1d3cb3f9a16d59)

Promoted from beta to production on June 22nd, 2016.

This is a minor update from Server 2.0 build 1.4.1 for security and stability only. This is a major upgrade from older (pre 1.4.0) builds.

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

New features:

  • None

Fixes:

  • The docker interface is taking 172.xx.x IP range   
    • HCPUB-814 - The docker interface is taking 172.xx.x IP range CLOSED  
  • HipChat CLI did not correctly set the static IP address for OVA deployment 
    • HCPUB-896 - HipChat Server: Admin cannot configure Static IP address CLOSED
  • When using a self signed certificate the CN does not match your FQDN (e.g. impacts using self-signed certificates with integrations)  
    • HCPUB-815 - hipchat certificates selfsign option generates a certificate without the server's correct hostname CLOSED
  • Upgrades that encountered issues may see the older UI  
    • HCPUB-997 - 4.0.x clients in HipChat Server 1.4.x are missing the 'three-dots' button CLOSED
  • Cannot add Phone Number to SMS Notifications in User Profiles 
    • HCPUB-881 - Cannot Add Phone Number to SMS Notifications in User Profiles CLOSED
  • HipChat Server global video disable 
    • HCPUB-835 - HipChat Server option to disable video globally doesn't work CLOSED
  • "Save" in /server_admin/notifications was clearing the fields
    • HCPUB-854 - HipChat Server: Fields are being cleared out after hitting "Save" in Server admin > Notifications CLOSED
  • Upgrade in 1.4.0 and 1.4.1 did not correctly support the hipchat upgrade --proxy setting
  • After disabling global Guest URL access the UI in each room incorrectly indicated it was still enabled
  • Cleaned up legacy monitoring and init scripts
  • The calendar picker bug in chat history is fixed
  • Invite URL is automatically disabled for 1.4.0 and 1.4.1 releases upon upgrade
  • Importing a new SSL certificate required a reboot to apply to the service for older than the 4.0 clients
  • Emoticons with low res can't be deleted  
    • HCPUB-44 - HipChat Server: Emoticons cannot be deleted - it keeps spinning CLOSED

Known issues:

  • Upgrades from HipChat Server 1.3 or older
    • Will take at least 45 minutes to upgrade, some customers have reported hours
    • Require a reboot after the upgrade (for new kernel and core libraries)
  • /home/admin/oem/content/login.html is overwritten (but is backed up and can manually be restored)
    • This file can be used to provide extra HTML content in the login UI /sign_in 
  • The system monitor (monit) will send service restart emails during a service restart or upgrade; those can be safely ignored
  • Customers using unsupported Xen or KVM virtualization may need an extra workaround after rebooting (How to fix a damaged grub boot partition through re-installation of grub2)
  • Some customers report after upgrade they receive alert emails with "Desc: failed to start (exit status 0) – /etc/init.d/user-sync: Starting user-sync... ok", this is a deprecated service and there is a KB to disable those alerts: Admin received alerts email "failed to start (exit status 0) – /etc/init.d/user-sync: Starting user-sync... ok"  
  • Some customers deploying a fresh OVA or upgrading to 1.4.2 have reported the inability to login  HCPUB-1045 - HipChat Server Chef run fails with 'Ran /etc/init.d/nginx start returned 1' Chef error Closed

HipChat Server 2.0 build 1.4.1 – May 4, 2016 

(HipChat.ova 4.6GB md5sum 968cdb059b2e71e6ea6ad3f56e821a14)

Promoted from beta to production on May 5th, 2016.

This is a minor update from Server 2.0 build 1.4.0 for urgent security and stability only. This is a major upgrade from older builds.

If you're upgrading from HipChat Server version 1.3 or older you will need at least 5GB of free disk space on the root partition and it will take at least 45 minutes to complete, and will require a reboot afterwards.

If you're upgrading from HipChat Server version 2.0 then you're in for a treat because the upgrade process is much simpler and faster now, though the download is a chunky 1.4GB.

New features:

  • None

Fixes:

  • Applies a mitigation to the ImageMagick library
  • OpenSSL updated for two major and three minor issues
  • OpenSSH drops support for arcfour ciphers, requiring AES-CTR as the sole cipher set
  • Removes the unloved greeter bot and a related offline upgrade crash for some customers
  • The system monitor (monit) will no longer stop monitoring some services during upgrade
  • Fixes an edge case for mobile notifications not working with high multi-second latency network connections

Known issues:

  • Upgrades from HipChat Server 1.3 or older
    • Will take at least 45 minutes to upgrade, some customers have reported hours
    • Require a reboot after the upgrade (for new kernel and core libraries)
  • The calendar picker in history does not work
  • /home/admin/oem/content/login.html is overwritten (but is backed up and can manually be restored)
    • This file can be used to provide extra HTML content in the login UI /sign_in 
  • The system monitor (monit) will send service restart emails during a service restart or upgrade; those can be safely ignored
  • Customers using unsupported Xen or KVM virtualization may need an extra workaround after rebooting (How to fix a damaged grub boot partition through re-installation of grub2)
  • Some customers report after upgrade they receive alert emails with "Desc: failed to start (exit status 0) – /etc/init.d/user-sync: Starting user-sync... ok", this is a deprecated service and there is a KB to disable those alerts: Admin received alerts email "failed to start (exit status 0) – /etc/init.d/user-sync: Starting user-sync... ok"
  • When using a self signed certificate the CN does not match your FQDN (e.g. impacts using self-signed certificates with integrations)   HCPUB-815 - hipchat certificates selfsign option generates a certificate without the server's correct hostname Closed
  • There is an issue when configuring the VM with an IP Address in the 172.17.x.x   HCPUB-814 - The docker interface is taking 172.xx.x IP range Closed

HipChat Server 2.0 build 1.4.0 – April 15, 2016

This major upgrade adds HipChat Connect, a new Delegated Admin user role, improved memory utilization, new clients, and a handful of bug fixes and improvements.

We've included import/export compatibility with HipChat Server 1.3 to make it easy for existing sites to test this new release prior to upgrade. Simply export from 1.3 and import to 2.0.

This upgrade requires at least 5GB of free disk space, at least 45 minutes to complete, and will require a reboot afterwards.

New features:

Fixes:

  • Openssl, libssl, and libc libraries updated with security fixes
  • OpenSSH upgrade from version 5.9 to 6.6 (stock Ubuntu packages)
  • PHP libraries updated with security fixes
  • Upgraded the internal caching service for performance and security fixes
  • Improved performance by reducing "global presence storms"
  • Design tweaks to make the WebUI a little more useful and pleasing
  • An issue that prevented larger than 10MB file uploads (the file upload size limit is 50MB)
  • An issue deleting custom emoticons HCPUB-44 
  • An issue with cookies with a special character HCPUB-73 

Known issues:

  • It will take at least 45 minutes to upgrade
  • reboot is required after the upgrade (new kernel and core libraries)
  • The calendar picker in history does not work
  • /home/admin/oem/content/login.html is overwritten (but is backed up and can manually be restored)
    • This file can be used to provide extra HTML content in the login UI /sign_in 
  • The welcome bot is not running on fresh deployments (@hipchat in-chat help is not present)
  • The system monitor (monit) will send service restart emails during a service restart or upgrade; those can be safely ignored

HipChat Server 1.x releases

Server 1.3 build 1.3.9 – March 24, 2016

Promoted from beta to production on April 6th, 2016.

This is a security patch release with minor fixes. 

If your version is earlier than 1.3.8 The server must be rebooted for this change to take full effect

Fixes:

  •  Fixed an intermittent issue where the database password update was not completely propagated during upgrade

Server 1.3 build 1.3.8 – February 19, 2016

Promoted from beta to production on March 10th, 2016.

This is a security patch release with minor fixes:

  • CVE-2015-7547 glibc getaddrinfo stack-based buffer overflow vulnerability
  • The customization scripts ~admin/startup_scripts/* are now executed after every configuration manager execution, not just at boot
    • An example ~admin/startups_scripts/firewall_hole was added to demonstrate how to make customizations to the appliance firewall
  • The outbound proxy password now works with mixed-case characters


Server 1.3 build 1.3.7 – November 18, 2015

Promoted from beta to production on December 14th, 2015.

New features:

  • Scrubbed mobile/email notifications (when that data has to be REALLY private, change the setting in admin/features)
  • Domain Restricted signups can now support multiple domains (example.com, example.pizza, example.beer in admin/features)
  • Exports now include 1-to-1 chats of "deleted" users
  • Diagnostic log bundling & convenient download
  • AES256 encrypted "hipchat diagnostics" on the CLI (see ~/diagnostics/readme.txt)
  • Upgraded internally to MariaDB 10 and passwords rotated

Fixes:

  • A bug that did not correctly delete expired sessions and therefore blocked some users (sadpanda)
  • Prevents "decompression bombs" from Files (attachments or emoticons) uploads (what was that User thinking?)
  • OpenJDK upgrade for Beta-aged deploys
  • Export handles very long unicode filenames
  • Export is missing some files with .gz file extension with error 'Received response with content-encoding: gzip, but failed to decode it'
  • Fixed a UI crash when accessing /server_admin/directory for LDAP directory types
  • APIv2 enforces domain restrictions when adding new user accounts
  • Resolved an issue with Active User count on the Status page

Known issues:

  • HipChat Servers initially deployed earlier than 2015 may have a monit config conflict upon upgrade:
    • Workaround/Resolution:
      sudo dont-blame-hipchat; rm -f /etc/monit.d/mysqld.monitrc; hipchat upgrade --force-upgrade
  • If Invitation URL is disabled "Invite your team" for admins in /chat will only send a broken URL.
  • After upgrade says "completed" Users cannot log in while an internal authorization service loads which can take up to 5 minutes
    • To follow along: tail -f /var/log/hipchat/atlassian-crowd.log until "Loading global messages from" appears (badpokerface)
  • Content previews are disabled for GitHub, Imgur, Twitter and YouTube, in order to comply with their service agreements please activate using How to Generate API Keys for Content Previews and Configure it in HipChat Server


Server 1.3 build 1.3.5 – September 29, 2015

New features:

  • Chat Message storage performance and stability improvements
  • Multi word User and Room search in the Admin WebUI
  • Group Admins cannot modify Group Owners via APIv1

Fixes:

  • API that returns recent history now includes the Topic messages
  • /commands that have similar prefixes won't confuse each other

Known issues:

  • HipChat Servers initially deployed earlier than 2015 may have a monit config conflict upon upgrade:
    • Workaround/Resolution:
      sudo dont-blame-hipchat; rm -f /etc/monit.d/mysqld.monitrc; hipchat upgrade --force-upgrade
  • Even if Invitation URL is enabled the "Invite Your Team" functionality from /chat will not send any invites (feelsbadman)
  • After upgrade says "completed" Users cannot log in while an internal authorization service loads which can take up to 5 minutes
    • To follow along: tail -f /var/log/hipchat/atlassian-crowd.log until "Loading global messages from" appears (badpokerface)
  • Content previews are disabled for GitHub, Imgur, Twitter and YouTube


Server 1.3 build 1.3.4 – September 17, 2015

This was the production release prior to 1.3 build 1.3.7

New features:

  • Web Client has Avatars next to the chats by default (so ensure your selfie or celeb-twin-lookalike image has been uploaded)

(Can be disabled in Settings -> Appearance if you really prefer just boring old text)

Fixes:

  • Improved some component service restarts when meteors, earthquakes, and other unanticipated events occur

Known issues:

  • Upgrades are typically over 8 minutes, for 1.2.3 and older it may take 20+ minutes
  • After upgrade says "completed" Users cannot log in while an internal authorization service loads which can take up to 5 minutes
    • To follow along: tail -f /var/log/hipchat/atlassian-crowd.log until "Loading global messages from" appears (badpokerface)
  • Content previews are disabled for GitHub, Imgur, Twitter and YouTube

Server 1.3 build 1.3.3 – September 14, 2015

The user directory service has received an overhaul. HipChat accounts are no longer associated to their remote directory sources by email address, but by a unique identifier instead. This solves a host of issues related to user management.

New features:

  • Directory integrations are now based on the directory username instead of email address
    • Authentication is still performed by email address in HipChat but mapped to directory username when authenticating to the remote directory

    • Changing a user's email address in the directory will update the email address in HipChat without creating a second account
  • Users and Rooms are now searchable in the web administrative controls: https://server/admin/usershttps://server/admin/rooms 
  • Exports can be interrupted at the command line: hipchat export --cancel
  • Higher performance APIv2 service with reduced database demands

Fixes:

  • Fixed a crash when the directory service encounters more than 25 thousand user accounts
  • User profiles no longer require the job title field to be filled

Known issues:

  • Carried over from Server 1.3 build 1.3.1


Server 1.3 build 1.3.1 – August 14, 2015

This release brings a fun emoticon interface with batch uploads and automatic image scaling. The platform gains performance, scalability and reliability improvements, increasing the chat connection rate by 500%.

New features:

  • Emoticons gain a new web interface at https://server/emoticons
    • Automatic image scaling with retina display support
    • Accessible by all users
    • Custom emoticon limit has been increased from 250 to 750
    • Emoticons can be uploaded in batches
  • Import & Export improvements
    • Exports can be purged by age, in days: hipchat export --purge-older-than 7
    • Export notifications can be sent to multiple email recipients: hipchat export --notify her@example.com him@example.com
    • Imports will now handle file attachments from deleted accounts for consistency
  • Improved performance
    • XMPP connection handling is now multi-process and CPU prioritized
    • XMPP services include new rate limiting and retry abilities
    • The data caching service (Redis) is utilized more efficiently and is CPU prioritized
  • API enhancements
  • XMPP encryption no longer implements the DES-CBC-SHA cipher
  • The terms of the open source software disclosure have been updated: https://server/open_source

Fixes:

  • APIv2 scalability with more than 8 CPU cores
  • Logjam security fix CVE-2015-4000 for Diffie-Hellman ciphers
  • OpenSSL has been upgraded from version 1.0.1-4ubuntu5.25 to 1.0.1-4ubuntu5.31
  • Invites from within the web chat client could crash
  • Disk capacity percentages on AWS deployments in the Status page: https://server/server_admin/

Known issues:

  • Content previews are disabled for GitHub, Imgur, Twitter and YouTube
  • CPU prioritization for the data caching layer (Redis) requires a server reboot or an explicit restart:
    • hipchat service --restart db; hipchat service --restart
    • Note this will cause a service outage of approximately two minutes
  • Personal admin privileged APIv2 tokens that were created before 1.3.1 did not get the new View_Room scope after upgrade
    • Workaround is to regenerate a new personal APIv2 token that has all of the scopes selected

Server 1.2 build 1.2.8 – June 18, 2015

Upgrades gain an aggressive retry to correct various ill conditions, hipchat upgrade --force-upgrade. The directory integration and data importer each pick up some polish. Otherwise, this release remains very close to HipChat Server 1.2 build 1.2.7. Thanks for upgrading. 

New features:

  • The HipChat server CLI upgrade utility has a more detailed diagnostic mode
    • hipchat upgrade --diagnostic
  • There is a force option has been added to the upgrade utility that is able to reapply the current version
    •  hipchat upgrade --force-upgrade
  • XMPP encryption no longer implements RC4-SHA and RC4-MD5 ciphers

Fixes:

  • Import of data handles additional timezone data variants
  • Improved upgrade logging in /var/log/hipchat/update.log
  • Scheduled synchronization of directory data is more reliable
  • The Delegated LDAP option has been removed from the directory integration
  • A bug related to downsizing the number of processors

Known issues:

  • Upgrades are still pretty slow, typically over 8 minutes, for 1.2.3 and older it may take 20+ minutes

Server 1.2 build 1.2.7 – June 4, 2015

This build enables much larger scale deploys. 36 CPUs and 64GB of RAM. Big iron! Upgrade reliability has been making a number of sites nervous so we've added some additional resiliency and retry capabilities. Big client changes round out the upgrades. Enjoy.

New features:

  • New Android client v3.0.0
    • Full rewrite implementing Android Material Design
  • New Linux and Windows clients v2.2.1373
  • Upgrade 
    • Adds an upgrade retry ability, via hipchat upgrade --force-upgrade
    • Improved logging
  • Scalability
    • New support for 16, 32 and 36 CPU core systems, i.e. c4.8xlarge
    • Support for up to 64GB RAM
  • Customizable web login page
    • Edit the file ~admin/config/oem/content/login.html to insert content on the web login page for compliance purposes

Fixes:

  • APIv2 1:1 history fetch of more than 50 messages

Known issues:

  • Upgrades are still pretty slow, typically over 8 minutes, for 1.2.3 and older it may take 20+ minutes
  • Imports will create messages with the current timestamp instead of their original sent timestamp

Server 1.2 build 1.2.6 – May 15, 2015

The directory integration has received some serious improvements. It's now more communicative about errors, is faster, more scalable, more event driven. We're continuing to work on directory integration with more functionality to follow. The release picks up a handful of fixes and polish:

New features:

  • Upgraded directory integration
    • Improved account validation
    • Improved logging and error reporting
    • Faster and more efficient using event-driven actions instead of polling
  • The custom emoticon limit has been raised from 100 to 250

Fixes:

  • YouTube previewing has been updated to use their v3 API
  • APIv2 improves handling of DNS errors for Add-On integrations
  • The Import/Export capability continues to evolve
    • Improved date handling
    • Retry capabilities for chat history fetch

Known issues:

  • Upgrades are still pretty slow, often over 5 minutes 
  • Some API and authentication errors occur on systems with 16 or more CPU cores


Server 1.2 build 1.2.5 – April 24, 2015

This release is the same as Server 1.2 build 1.2.4 with one fix for upgrades.

New features:

  • None

Fixes:

  • Upgrade fix for versions older than 1.2 build 1.2.3

Known issues:

Server 1.2 build 1.2.4 – April 20, 2015

This release is focused on reliability and security. Note that the group invite URL is disabled by this upgrade.

New features:

  • Group invite URLs are disabled by default

Fixes:

  • Native mobile notifications to some IOS devices has been restored
  • An internal library, libtasn.1 has been patched per USN-2559-1
  • Upgrades from Server builds older than 1.2.0

Known issues:

  • Upgrades will take longer than before, at least 5 minutes and sometimes longer
  • Customers that do not allow outbound access should contact server-support@hipchat.com for a patch before upgrading
  • The user count at /server_admin/status erroneously includes the number of guest users registered
    • Note that the user count used for license enforcement excludes guest user counts correctly
  • If you are unable to authenticate several minutes after upgrade please SSH in as the admin user and run
    • hipchat service --restart directory
    • Wait two minutes for the directory service to restart and attempt another login through the web or a chat client
    • The directory service log file is /var/log/hipchat/atlassian-crowd.log

Server 1.2 build 1.2.3 – April 16, 2015

The new generation web chat client has matured and is now the default. We've made good progress improving stability on directory integration and data import/export too. Platform compatibility and support is expanding with new disk management code.

New features:

  • New client versions
    • The new web chat client has been updated to version 3.0.3 and is now the default web client
    • The Windows and Linux clients have been updated to version 2.2.1361
  • APIv2 enhancements
    • Room lifecycle webhooks
    • User avatar controls
    • See /docs/apiv2 on your own HipChat Server deployment
    • User invite to rooms
  • OVA deployments will automatically scale /file_store and /chat_history partitions on reboot
  • The AWS image will automatically expand its virtual disk on reboot for HVM instance types (forxvd device types, also applicable to Xen)
  • There is a new maintenance mode to limit production access during maintenance events such as upgrade and boot
    • This is automatic and has no manual controls
  • Directory integration has improved documentation: Configuring User Directories
  • The Import/Export utility has been improved
    • Many-gigabyte datasets now work
    • Unexpected and duplicate values are handled more gracefully during import
    • Job summary emails now include nice logs and warnings
  • Service monitoring has been improved for higher availability
    •  NTP, Import/Export, the welcome bot, and the notifications daemon

Fixes:

  • SSL libraries have been patched per USN-2537-1
  • Directory integration is more reliable at scale by increasing some process limits
  • Directory integration removes options for read-write and delegated authentication capabilities as we're going to keep directory access read-only for ease, security & simplicity
  • Reducing the CPU core count assigned to the HipChat Server VM will no longer leave rogue processes behind
  • Rooms imported with guest access enabled are now able to disable that access
  • Redis data files have been moved from /mnt to /file_store/redis
  • The OSX chat client download now uses .zip format instead of .dmg for better download reliability
  • The log file rotations have been refined and now include /var/log/hipchat/auth.log

Known issues:

  • Upgrades from installations older than Server 1.0 build 1.2.0 can fail
  • Some IOS users are not receiving native mobile notifications


Server 1.2 build 1.2.1 – March 17, 2015

Our web UI for upgrade broke in Server 1.0 build 1.1.9 and Server 1.2 build 1.2.0. To upgrade to this release please SSH in as the user admin and run hipchat upgrade

New features:

  • HipChat Server Admins can now use the web interface to disable Video (notsureifgusta)
  • Smileys are now hi-res retina ready (awyiss)
  • The AWS image is compatible with more instance types

Fixes:

  • The upgrade web UI (/server_admin/upgrade) works again
  • 3rd party cookies with !, ? and ~ characters in their key names will no longer break web session handling
  • The setup wizard is more reliable at initial startup
  • libicu has been patched to resolve security issues USN-2522-3

Known issues:

  • The new web chat client is beta software and does not offer video chat, audio and screen sharing
  • Changing the email address of a user in a directory can create duplicate user accounts in HipChat
  • Downloading the .dmg from https://hipchat.example.com/download may sometimes return a damaged file.  This is a known issue with the Mac client for both Cloud and Server and the workaround is to use https://www.hipchat.com/downloads/latest/mac and get the .zip file

Server 1.2 build 1.2.0 – March 2, 2015

This release brings the next generation web chat client and many changes focused on reliability and security refinements.

New features:

  • Web chat client "v2"
    • Enable per-user by specifying the ?v=2 URL suffix, for example https://hipchat.example.com//chat?v=2
    • You can revert to the original web chat client at /chat?v=1
  • All web services (/admin, /chat, /files, etc) instruct search engines not to index
    • The specific header is X-Robots-Tag: noindex, nofollow, nosnippet, noarchive
  • Full scale images are rendered in the browser instead of downloaded
    • For jpg/jpeg, gif, gifv, and png file formats
  • Increased authentication timeout durations in some authentication paths, from 5s to 30s
  • The secure shell (SSH) configuration has been hardened
    • The following ciphers have been disabled: aes128-cbc, 3des-cbc, blowfish-cbc
    • The following message authentication codes (MAC) have been disabled: hmac-md5
  • The Android client has been upgraded to version 2.4.4

Fixes:

  • Reliability improvements in the user directory 
  • Import/Export scalability improvements
  • Duplicate accounts with varied case email addresses are handled to enable case insensitive logins
    • Relevant to users with local accounts and corresponding camel-cased directory data on Server 1.0 builds 1.1.7 and 1.1.8
  • IOS mobile notifications are working again

Known issues:

  • The new web chat client is beta software and does not offer video chat, audio and screen sharing
  • Changing the email address of a user in a directory can create duplicate user accounts in HipChat
  • Upgrade from the web interface is broken due to some new security measures implemented in 1.0 build 1.1.9
    • Please SSH in as the admin user and type the following to upgrade: hipchat upgrade -u
  • Downloading the .dmg from https://hipchat.example.com/download may sometimes return a damaged file.  This is a known issue with the Mac client for both Cloud and Server and the workaround is to use https://www.hipchat.com/downloads/latest/mac and get the .zip file

Server 1.0 build 1.1.9 – February 12, 2015

The release is driven by improvements to the directory integration, bug fixes and security hardening.

New features:

  • Bundled client upgrades
    • Windows & Linux at version 2.2.1328
    • OSX at version 3.2.1-160
  • Import/Export utility adds deleted user and guest account capabilities
  • Retina emoticons
  • Custom /etc/hosts and /etc/network/interfaces capability for users with special requirements
  • Stronger cross-site scripting prevention
  • Guest invite URLs now use SSL so that you can disable port 80 access to your installation

Fixes:

  • Login email addresses are no longer case sensitive
  • Directory integration will ignore the optional outbound proxy 
  • CVE-2014-6277, CVE-2014-6278 Upgraded the system shell (bash) to prevent privilege escalation from a theoretically compromised service
  • Import/Export handles additional character sets

Known issues:

  • We've seen some trouble upgrading images older than beta build 1.1.4
  • A reboot is advised after upgrade from builds older than Server 1.0 build 1.1.8
  • Login names (email addresses) will remain case sensitive if duplicate accounts are present by email address
  • The new Twitter integration has stopped working with Server, the crash is by the hosted code, not in Server
  • Mobile notifications for IOS clients stopped working
  • Upgrade from the web interface is broken due to some overly strict security measures implemented in 1.0 build 1.1.9
    • Please SSH in as the admin user and type the following to upgrade: hipchat upgrade -u

Server 1.0 build 1.1.8 – January 31, 2015

A security and compatibility release, of moderate importance.

New features:

  • bcrypt password hashing (replaces SHA-based hashing)
    • Passwords are rehashed automatically, transparently, at login
    • Not applicable to remote authentication

Fixes:

  • CVE-2015-0235 "ghost" glibc patch to fix gethostbyname* exploits
    • Please reboot the VM after applying this upgrade, a reboot is not automatic
  • Compatibility fix for licenses issued by my.atlassian.com on AWS deploys

Known issues:

  • Login email addresses remain case sensitive


Server 1.0 build 1.1.7 – January 27, 2015

Our production launch! See https://hipchat.com/server for details. 

New features:

  • Production versioning HipChat Server 1.0 with build numbering consistent with the beta program
  • Production licensing https://www.atlassian.com/customer-agreement/
  • Open Source disclosures have expanded to include the components used by Atlassian Crowd
  • Licensing and purchasing using existing Atlassian infrastructure 
    • Setup wizard bridges to license evaluation for easy configuration with a server ID (SID)
    • Purchase HipChat Server the way you do other Atlassian products such as JIRA or Stash
  • Error reporting has been added to the configuration system when run as hipchat upgrade --restart
  • Import & Export will now handle guest accounts and chat history
  • Add On enhancements
    • Filtered list of instructional add ons that are qualified 
    • Next-generation add on support for Atlassian products including JIRA and Confluence

Fixes:

  • Scalability fixes to the Import & Export for large teams
  • Directory integration changes for better global character sets
  • Directory integration fixes for accounts with missing email, mention and user names
  • New OVA deploys have a 4GB larger root partition
  • An email marketing opt-out option has been removed from the user profile page
     in the user

Known issues:

  • Login names (email addresses) are case sensitive, they were case insensitive in build 1.1.6, and we plan to restore that behavior
  • Fresh deploys of this build include the latest emoticons from hipchat.com but upgrades to this release do not. We'll get those emoticons updated in short order
  • Amazon AWS deployments are rejecting some licenses issued from my.atlassian.com. Please contact server-support@hipchat.com for a temporary license until we have this fixed.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport