Upgrading using the web app

1. Open a web browser and browse to the URL for your Hipchat server web app. For example, browse to https://hipchat.yourcompany.com/
2. Click the Server admin tab at the top.
3. Click the Upgrade tab.  A message states whether your system is up to date.
4. Optional: If you want to upgrade to the Beta channel, click Beta, then Change upgrade channel.
5. Click Upgrade to the latest version.
   A message appears informing you Hipchat users will be disconnected temporarily while you upgrade.
6. Click OK.

Upgrade using the CLI

To check whether Hipchat Server is up to date:

hipchat upgrade --check

To view the current upgrade channel:

hipchat upgrade --show

To set the current upgrade channel to the Beta channel:

hipchat upgrade --channel beta

To set the current upgrade channel to the production channel:

hipchat upgrade --channel production

To upgrade using the current channel:

hipchat upgrade --upgrade

Use an outbound proxy server to upgrade

If your company requires use of a Proxy Server for outbound network traffic, you can configure Hipchat Server to check for updates using an outbound proxy server. This step is optional and is not required in order to upgrade.

Enter the following commands in the CLI:

hipchat upgrade --proxy http://user:password@proxy.example.com:portnumber
hipchat upgrade --check
hipchat upgrade --upgrade

If your proxy server does client SSL certificate validation, make sure to install your certificate before running the upgrade.

Verify your upgrade

You should always verify that the upgrade succeeded and that the server is functioning normally after the upgrade finishes. This section gives you a few steps to run once the upgrade is done.

1. Check for the upgrade success message in the logs and validate the new version is up: 

   grep -A1 "Upgrade Completed Successfully" /var/log/hipchat/update.log

2. Check that all services are up, running fine, and are monitored:

   monit status | grep -A2 "^Process "

3. Compare the package versions in the manifest to the Debian packages installed to verify that all the new Hipchat packages were installed.

   cat /file_store/archive/hipchat.server.manifest | grep hc- | rev | cut -d/ -f1 | rev > /tmp/manifest_packages.txt
   dpkg -l | grep hc-

4. Check that important Hipchat features are working: 
   1. Internal and LDAP login 
   2. Private and room chats with attachments
   3. Integrations
   4. Push email notifications
   5. Directory synchronization

5. Verify if the FQDN information is still valid

   cat /etc/hosts
   cat /hipchat/config/site.json

   Check HipChat clients unable to connect to HipChat Server: Couldn't load HipChat if that is not the case.

    

Troubleshooting

Sometimes instability in the internet or network connection causes the upgrade check or upgrade process to fails. To retry an upgrade, use the following command:

hipchat upgrade --force-upgrade

 You may also want to review the external directory setup (if you have configured this on the instance) after the upgrade to ensure that everything is working as expected.

For more troubleshooting information, see Connectivity Issues When Upgrading and the Hipchat Server Knowledge Base.