Deploying Hipchat Server
This page describes how to deploy Hipchat Server from an open archive (OVA) image and an Amazon Machine Image (AMI) using Amazon Web Services (AWS). It also describes how to configure Hipchat Server to use a static IP address.
Deploying from an OVA image
You can deploy Hipchat Server from an OVA image. Before you start, see the recommendations for deploying Hipchat Server in a secure configuration.
Downloading the OVA image
Download the OVA image at here.
System requirements for deploying the OVA image
We distribute Hipchat Server in an open virtualization archive (OVA) format.
We support deploying the Hipchat Server OVA image on VMware and VirtualBox.
Note: If you want to cluster Hipchat Server for high availability and fault tolerance, we recommend you deploy Hipchat Server using VMware as VMware provides these features. For details, see the VMware site and documentation. Also, see this FAQ.
The virtual machine uses a 64-bit OS base on Ubuntu defaulting to 4GB RAM and 4 vCPU and 74GB of storage capacity.
Deploying from the OVA image
- Start your virtualization management interface using any of the following: VI Client, VirtualBox, VMware Fusion, Workstation, or Virtual Server.
- Deploy the appliance (OVF template), then specify the local
- Accept the license agreement.
- Specify the deploy-time configurations, if available.
- Start the virtual machine, if it doesn't start automatically.
- Wait at least five minutes for the server to start for the first time.
Your Hipchat Server's IP address ( will be accessible and will show you the Configure Hipchat Server UI when the system is ready.
- Log into the local console or SSH with the following credentials:
- Accept the EULA and type
passwdand update the local admin account password.
The password is your key into the Hipchat Server command line interface. If you lose it, we can't recover it for you.
- Optionally, configure a static IP address.
- Log in to and configure Hipchat Server in the UI. The first time you log in, a setup wizard runs.
Configuring a static IP address
If you deployed Hipchat Server from an OVA image, Hipchat Server is running in dynamic host configuration protocol (DHCP) mode (if DHCP is available), and will have its IP address, netmask, gateway, and DNS provided by your DHCP Server.
You can alternatively, manually, assign a static IP address.
When you configure Hipchat Server to use a static IP address you must configure all parts of the network, such as the netmask, gateway, and DNS.
To assign an IP address, type the following command:
hipchat network -m static -i <IP> -s <netmask> -g <gateway> -r <DNS>
hipchat network -m static -i 192.168.1.2 -s 255.255.255.0 -g 192.168.1.1 -r 22.214.171.124
If you have multiple network interfaces (NIC), you can use the
-c option to configure each one separately.
eth1, for instance:
hipchat network -m static -i 192.168.1.2 -s 255.255.255.0 -g 192.168.1.1 -r 126.96.36.199 -c 1
Netmask, default gateway and DNS are mandatory options when configuring a static IP address. If you're configuring more than one NIC, you will end up with more than one default gateway in your routing table. This will cause routing problems and might render your instance unreachable.
To get around that, you should run
hipchat network for all NICs then remove the gateway from
/etc/network/interfaces and delete the routes from the routing table.
Note: For more help on the syntax, type:
Deploying from an AMI
You can deploy Hipchat Server from an AMI.
Note: For information on Amazon Web Services' security infrastructure, see Amazon Web Services Security Center.
- Log into the Amazon Web Services (AWS) administrator's console.
- Download the current set of public machine images' names by region: hipchat-server-amis.html (hipchat-server-amis.csv)
- In the Amazon Machine Images (AMIs), search for a Hipchat Server identifier in your region, for example: ami-11aa22bb33
- Launch the selected image.
- Define a new security group (firewall rules) with open outbound and the following inbound rules for TCP ports:
- 22 for remote management by yourself
- 80, 443, 5222, 5223 for production chat and web services
- Provision an instance of Hipchat Server image
- Select an Instance Type with at least two vCPUs and 4GB or more of RAM:
- c4.large for under 100 users (4GB RAM)
- c4.xlarge under 500 users (8GB RAM)
- c4.2xlarge under 1000 users (16GB RAM)
- c4.4xlarge under 3000 users (30GB RAM)
- c4.8xlarge under 5000 users (60GB RAM)
- Assign at least 60GB to the root EBS SSD volume.
Note: 4GB is used for system files; the rest is used for file uploads, logs, and chat history.
- Assign the newly created Hipchat security group.
Select a keypair for SSH access as the admin user. For example, type:
ssh -i yourkey.pem firstname.lastname@example.org
Note: If you are prompted for a password when trying to SSH using your EC2 private key then verify that you have the correct key, the correct user ownership of the yourkey.pem file, and and that the permissions on the key are read only (i.e. chmod 400).
- Note the public fully qualified domain name (FQDN) once deployed, for example:
ImportantHipchat Server is designed to use the Public DNS address, not the Public IP.
- Create a
CNAMErecord for your production domain that resolves to the AWS public hostname.
- Wait at least ten minutes for the server to start for the first time (depending on instance type).
Your Hipchat Server's FQDN () will be accessible and will show you the Configure Hipchat Server UI when the system is ready.
Getting root access to the OVA and AMI files
To get root access to the OVA or AMI files:
SSH in as "admin" and run
Changes you make as root may be overwritten on upgrade and may cause data loss.