Connecting the Windows and Linux desktop apps

1. Start the Hipchat app.
2. Choose Configure Connection below the Log In button.
3. Under Connect to, select Hipchat Server, then enter the fully qualified domain name of your Hipchat Server. (For example, hipchat.example.com)
4. Click OK.
5. Log into Hipchat.

Connecting the Mac OSX app

1. Start the Hipchat app.
2. Select Hipchat > Preferences > Connect using, then Hipchat Server.
3. In the Server address field, enter the fully qualified domain name of the Hipchat Server. (For example, hipchat.example.com)
4. If Hipchat Server is using a signed SSL certificate, select the Require certificate validation check box. (To find out whether this is required, check with your Hipchat Server admin.)
5. Log into Hipchat.

Connecting the Android app

1. Start the Hipchat app.
2. On the Login Screen, tap .
3. Tap Hipchat Server.
4. Enter the fully qualified domain name of the Hipchat Server. (For example, hipchat.example.com)
5. If Hipchat Server is using a signed SSL certificate, select the Require certificate validation check box. (To find out whether this is required, check with your Hipchat Server admin.)
6. Tap OK, then sign in.

Connecting the iPhone / iPad app

1. Go to your iPhone's or iPad's Settings, then scroll down until you see Hipchat.
2. Tap Connect using > Hipchat Server, then tap the back arrow.
3. Tap Server address, then enter the fully qualified domain name of the Hipchat Server. (For example, enter hipchat.example.com)
4. If Hipchat Server is using a signed SSL certificate, ensure the Require certificate validation toggle is enabled (green). (To find out whether this is required, check with your Hipchat Server admin.)
5. Tap Settings to ensure the new settings are saved.
6. Open the Hipchat app and sign in.

Troubleshooting

See the Hipchat Knowledge Base for help troubleshooting the Hipchat apps.

Note on CentOS/RHEL/Fedora: We have had reports that the Linux Hipchat client on CentOS 7 will not allow you to choose Hipchat Server upon login if NetworkManager is running. We have not been able to reproduce this issue but are calling it out here just in case you hit the same issue. The workaround to execute is to stop NetworkManager.