System Requirements for HipChat Server
This page describes what you need to install HipChat Server and links to system requirements for the clients. It is intended for IT administrators.
IPv4 address
You need one IPv4 address.
DNS record
While you can initially test HipChat Server with only an IP address we strongly recommend you create either an A or CNAME type DNS record. The DNS record should match the qualified domain name that you configure on your HipChat Server.
SSL certificate
While HipChat Server comes with a self-signed SSL certificate by default for initial testing purposes, we strongly recommend you use an SSL certificate purchased through a trusted Root CA vendor. For more information, see Creating or Obtaining an SSL Key and Certificate.
Virtualization
You need one of the following:
- VMware (64bit)
- VirtualBox (64bit)
- Amazon Web Services (AWS)
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.
If you're using VMware or VirtualBox, see Deploying HipChat Server from an OVA Image.
If you're using AWS, see Deploying HipChat Server from an Amazon Machine Image.
CPU, RAM, and disk space requirements
The amount of CPUs and RAM required depends on the number of users you have:
- Under 100 users: 2 CPU cores (2GHz or higher) and 4GB RAM
- Under 500 users: 4 CPU cores (2.8GHz or higher) and 8GB RAM
- Under 1000 users: 8 CPU cores (2.8GHz or higher) and 16GB RAM
- Under 3000 users: 16 CPU cores (2.8GHz or higher) and 32GB RAM
- Under 5000 users: 16 CPU cores (2.8GHz or higher) and 64GB RAM
The minimum disk space is 70 GB. We recommend you have 200 GB of disk space.
Inbound TCP ports
You need the following inbound TCP ports:
- 443 TCP web from Internet (remote clients and third party integrations)
- 5222 (TLS) TCP XMPP from Internet (remote clients and bots)
- 5223 (SSL / TLS) TCP XMPP from Internet (remote clients and bots)
- 22 TCP SSH from your local LAN for administration (or disable SSH and use local console)
- 80 TCP web from Internet (optional, allows redirection when Users type http://fqdn instead of https)
Outbound TCP ports
You need the following outbound TCP ports:
- 25 TCP (or access to your local email server)
- 53 TCP/UDP to DNS servers
- 123 TCP/UDP to NTP servers
- 443 TCP to barb.hipch.at for native mobile notifications
- 443 TCP to marketplace.atlassian.com for Add-Ons discovery
- 80, 443 TCP to upgrade servers at:
- Chat client systems must meet AddLive's connectivity requirements for video and screen sharing
Additional security best practice recommendation
It is best practice to have routing and firewall concerns addressed before the Application Layer/Virtual Appliance. Therefore it is recommended that port forwarding be used (i.e. by a routing device). Any additional firewall restrictions should be enforced by a separate layer before reaching HipChat Server.
Client system requirements
You and the people in your organization who will be using HipChat, can view the system requirements for the HipChat clients on the clients' download pages. For more information, see Downloading and Connecting HipChat Apps.
One-to-one video chat works best when clients have 200ms or less network latency between them.