HipChat WebApp not working 2.0.7 (2016.11.08.200718) or later

[Rene Seiler]

Hello,

I created a new AMI with HipChat 2.1 build 2.1.0, but I wasn't able to connect at all to this instance. So, I decided to upgrade from HipChat Server 2.0 build 1.4.0 to HipChat Server 2.0 build 2.0.7. 

admin@hipchat:~$ hipchat upgrade -u -f
Expected sha512sum and filename: cf5bb5afd58a074591c8abb3f61d06ed71f3bb50ee230d0d44a052b459fa448ea4e25f1ae1ac2d0f36a5dc23c260ba9ea89fa8ff2cdc4878b21229bcc13f41fe  hcs-2.0.7-2016.11.08.200718.tar.gz
Downloading the update, this may take a few minutes depending on your network speeds
Calculated sha512sum: cf5bb5afd58a074591c8abb3f61d06ed71f3bb50ee230d0d44a052b459fa448ea4e25f1ae1ac2d0f36a5dc23c260ba9ea89fa8ff2cdc4878b21229bcc13f41fe  hcs-2.0.7-2016.11.08.200718.tar.gz
coercing to Unicode: need string or buffer, NoneType found
Updating system configuration, this may take a few minutes...
Upgrade Completed Successfully (awyeah)
Current Version is: Atlassian HipChat 2.0.7 (2016.11.08.200718)

I'm able to connect with the client app (Mac OS and Windows 8), but the WebClient will not load at all.

It looks like the WebApp uses the wrong host name. Instead of hipchat.charry.com it uses ec2-54-93-115-135.eu-central-1.compute.amazonaws.com

Rene

[Rene Seiler]

Looks like. The strange thing is I didn't change DNS settings while upgrading HipChat. I will have a look next time. 

Interesting was, that the OSApp was able to connect and the WebAPP not.

Rene

[wdehaan]

Hi Rene,

Was is just DNS then?

[Rene Seiler]

looks like it works again after setting the DNS records again.