HipChat4 broken after moving to 18.04

Long story super short ‘YAY I HAVE NEW MONITORS!’ / ‘BOO I HAVE TO REINSTALL!” … HipChat4 what have you done to me? So yeah – handily pretty much the release day for Bionic Beaver (I know right?) 18.04. Work machine – so need to be up on my feet as fast as humanly possible – backups – sweet as – just need tools. HipChat – last time it was the graphics issue – this time it would appear to be shiny new OpenSSL. The fix for me is below – however, my first encounter with this joy showed “Unable access hipchat.com. Please check that your network is connected and try again” ….¬†needless to say, my network¬†was very connected. Much packets. Many wow.

$ nslookup hipchat.com
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: hipchat.com
Address: 34.196.65.144
Name: hipchat.com
Address: 34.206.78.152
Name: hipchat.com
Address: 52.23.0.68

So – clutching at straws I ran it from the command line and ran with what it was ACTUALLY complaining about. Here is an abstract:

Warning: [12:31:04][qt.network.ssl][:0] QSslSocket: cannot call unresolved function SSLv23_client_method
Warning: [12:31:04][qt.network.ssl][:0] QSslSocket: cannot call unresolved function SSL_library_init
[12:31:04][void AbstractOnlineStatus::handleReplyFinished(QNetworkReply*):131] errors from onlineStatusCheck found. ErrorStr = “Error creating SSL context (error:140A90C4:SSL routines:func(169):reason(196))”

Okay – a smoking gun – and something is better than nothing.

Atlassian sites seemed to cross-reference a bunch however my trail ended with:

https://community.atlassian.com/t5/Hipchat-questions/hipchat4-openssl-error/qaq-p/146012

– then –

https://jira.atlassian.com/browse/HCPUB-6249

Okay – everyone likes a little false hope. From there

$ sudo bash

# rm /opt/HipChat4/lib/libcrypto.so*

# ln -s /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 /opt/HipChat4/lib/libcrypto.so.1.0.0

# ln -s /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 /opt/HipChat4/lib/libssl.so.1.0.0

Ensure that the application was dead, start from console – and watch it rattle on through all the way to the login prompt.

Happy days indeed.

Thank you unnamed chap/ess… the hero we deserve.

Leave a Reply

Your email address will not be published. Required fields are marked *

%d bloggers like this:
Skip to toolbar