Resolution: Won't Fix
HCS 2.2.0, HCS 2.2.6, HCS 2.2.9
Severity 2 - Major
After updating the FQDN using the WebUI, the /etc/hosts file does not show the new FQDN. This results in the web/desktop apps to show an error:
If you look at the solo.json file and the /etc/hosts after the change, it'll show two different FQDN's:
HipChat Server 1.4.x, 2.0.x, 2.2.x
This error only appears to be related to AWS deployed instances.
- Login to the HipChat Server web user interface
- Change either the hostname/domain
- Verify that this change resides in DNS as well
- After DNS propagation, try and login with the web or desktop app.
The HipChat client should load.
Receive error 'Couldn't load HipChat'.
- This happens after a change to the FQDN is made (including on HC Server install steps)
- Amazon ELB address is also sometimes auto-populated instead of the HCS FQDN on new installs
- Only happen to AWS deployed HipChat Server instances
- This error will affect all users on the Server that aren't logged in. Some users may not be affected right away
Using the developer tools in Chrome, you will see http-bind errors in the Network tab when loading up the app. Notice in the Headers tab that these show a 'Request URL' that is different from 'Request Headers' origin and referer.
For a workaround, log into the HipChat Server command line and run the following command:
Make sure to replace incorrect-address and correct-hipchat-server-fqdn with the appropriate values. You may need to do this on /hipchat/config/site.json as well:
After the change is made, please do a full reboot of the server using sudo reboot.