HipChat Server not found

Alexander Belozerov July 19, 2018

An error "HipChat Server not found" occurs when trying to connect to the server using a domain name. This error does not occur when connecting via the IP address.

Client: HipHat4 4.30.5.1676, 4.30.5.1678a

Platform: Arch Linux

HipChat Server version: HipChat Data Center 3.1.4 (2018.03.05.095355)

P.S. On Fedora 27, connecting using a domain name does not cause errors.

UPD: started the client under another user - the error disappeared.

UPD2: deleting the folder  .cache/Atlassian/HipHat in my home directory solved the problem with my user

1 answer

0 votes
AhmadDanial
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 22, 2018

Hi, Alexander.

Thank you for the updates on the issue that you were facing here. As of UPD2, can you please confirm that the HipChat Server not found issue was resolved after the deletion of .cache/Atlassian/HipChat file in the home directory? When I checked on my end, the directory contains the following content (as an example):

ahmaddanialmohammad@ubuntu:~/.cache/Atlassian/HipChat/QtWebEngine/Default/Cache$ ls -lAh
total 2.3M
-rw------- 1 ahmaddanialmohammad ahmaddanialmohammad 44K Jul 20 21:15 data_0
-rw------- 1 ahmaddanialmohammad ahmaddanialmohammad 264K Jul 20 21:15 data_1
-rw------- 1 ahmaddanialmohammad ahmaddanialmohammad 1.1M Jul 20 20:19 data_2
-rw------- 1 ahmaddanialmohammad ahmaddanialmohammad 4.1M Jul 20 19:56 data_3
-rw------- 1 ahmaddanialmohammad ahmaddanialmohammad 19K Jan 3 2018 f_000001
-rw------- 1 ahmaddanialmohammad ahmaddanialmohammad 52K Jan 8 2018 f_000002
-rw------- 1 ahmaddanialmohammad ahmaddanialmohammad 19K Jan 8 2018 f_000003
-rw------- 1 ahmaddanialmohammad ahmaddanialmohammad 28K Jan 8 2018 f_000006
-rw------- 1 ahmaddanialmohammad ahmaddanialmohammad 36K Jan 8 2018 f_000007
-rw------- 1 ahmaddanialmohammad ahmaddanialmohammad 39K Jan 8 2018 f_000008
-rw------- 1 ahmaddanialmohammad ahmaddanialmohammad 30K Apr 4 09:16 f_00000c
-rw------- 1 ahmaddanialmohammad ahmaddanialmohammad 189K Jul 20 19:56 f_00000d
-rw------- 1 ahmaddanialmohammad ahmaddanialmohammad 19K Jul 20 19:56 f_00000e
-rw------- 1 ahmaddanialmohammad ahmaddanialmohammad 257K Jul 20 21:15 index

 So, I want to make sense on how the content of the directory ties back to the error that you were seeing originally.

Alexander Belozerov July 22, 2018

Hi, Ahmad

This issue really was solved. I suspect that it is somehow connected with the hipchat package from Arch Linux User Repository (AUR): link

Recalled that I also deleted ~/.config/Atlassian/HipChat and ~/.HipChat, but they were empty.

AhmadDanial
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 23, 2018

Hi again, Alexander.

That's interesting. From the explanation that you have provided, let us summarize the solution you performed:

  1. Delete ~/.cache/Atlassian/HipChat directory
  2. Delete ~/.config/Atlassian directory
  3. Delete ~/.HipChat directory

This will provide a good alternative workaround should other users bump into the same issue. Thank you for sharing again!

Alexander Belozerov July 23, 2018

Ahmad, one last correction: just looked through the bash command history and realized that i deleted ~/.config/Atlassian folder, not ~/.config/Atlassian/HipChat. Looks like there is no HipChat folder in ~/.config/Atlassian, only config file HipChat.ini.

AhmadDanial
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 23, 2018

Hey there, Alexander.

Gotcha. Thank you for correcting me on that part. I went ahead and edited the steps above to ensure that there are no confusion. 

The HipChat.ini file holds the configuration of the client as mentioned in the Windows / Linux Configuration File documentation. Nevertheless, there is not much information shared publicly on what user can / cannot configure in that file. If you are interested, please add yourself as a watcher to the Suggestion below to keep yourself posted for updates on the improvement of the documentation:

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events