There was a problem uploading the avatar. Please try again later.

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Server, Data Center, and Cloud By Request - This article was written for the Atlassian server and data center platforms but may also be useful for Atlassian Cloud customers. If completing instructions in this article would help you, please contact Atlassian Support and mention it.

This is for an outdated version of Hipchat Server

 This article applies to a version of Hipchat Server which will be deprecated soon. After that period the version will no longer be supported.

When will my version be deprecated?

The following versions have been deprecated:

  • Hipchat Server 1.3 (EOL Date: Aug 17, 2017)
  • Hipchat Server 2.0 (EOL Date: Jun 17, 2018)
  • Hipchat Server 2.1 (EOL Date: Dec 8, 2018)

The following version will be deprecated soon:

  • Hipchat Server 2.2 (EOL Date: May 30, 2019)

You can read more about Atlassian's End of Life policy here.

You should upgrade to a more recent version of Hipchat Server as soon as you can to take advantage of new features, and security and bug fixes.


When trying to upload an avatar in Hipchat Server administrative interface, the following error message is displayed:



  • Hipchat Server 1.2.7 and above

Steps to Reproduce

  1. Log into Hipchat Server as an Administrator
  2. Navigate to Group Admin >> Group Info
  3. Click Browse under Group avatar to select an image, then click Upload new avatar


Run the SQL command and verify that "storage_location": "local" is included:

DBPASS=$(awk '/"pass"/ {gsub(/[",]/,"");print $2}' /hipchat/config/site.json) && mysql -uroot -p$DBPASS hipchat -e "SELECT metadata FROM groups;

For example:

admin@hipchat:~$ DBPASS=$(awk '/"pass"/ {gsub(/[",]/,"");print $2}' /hipchat/config/site.json) && mysql -uroot -p$DBPASS hipchat -e "SELECT metadata FROM groups;"+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+| metadata                                                                                                                                                                                                                                                                                                                                                                                    |+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+| {"storage_location": "local", "perms": {"create_rooms": "admins", "emoticon_admin": "all", "file_sharing": "all", "history_edit_perm": "admins", "guest_access": "none"}, "history_retention": "3", "email_domains": [""], "trial_expiration": "2017-10-19 02:08:52", "has_signed_in": 1, "email_domain": "", "forgot_password_link_for_directory_users": null} |+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+


This is caused by a string in the database which points to an invalid storage location.


  1. Perform a back up of the Hipchat Server by referring to the Back up and restore Hipchat Server documentation
  2. Access the hipchat database using the command:

    DBPASS=$(awk '/"pass"/ {gsub(/[",]/,"");print $2}' /hipchat/config/site.json) && mysql -uroot -p$DBPASS hipchat
  3. Update the metadata column of the hipchat.groups to exclude the "storage_location": "local" parameter. For example:

    UPDATE groups SET metadata ='{"perms": {"create_rooms": "admins", "emoticon_admin": "all", "file_sharing": "all", "history_edit_perm": "admins", "guest_access": "none"}, "history_retention": "3", "email_domains": [""], "trial_expiration": "2015-01-19 02:08:52", "has_signed_in": 1, "email_domain": "", "forgot_password_link_for_directory_users": null}' WHERE id=1;
  4. Once done, exit the SQL console:

  5. Next, we need to verify that site.json has the correct storage path. Run this query:

    cat /hipchat/config/site.json | grep -A1 '"storage":'

    You are expected to see an output similar to this:

    admin@hipchat:~$ cat /hipchat/config/site.json | grep -A1 '"storage":'
      "storage": {
        "path": "/file_store/local"
  6. If your output looks different, please modify the file so it looks like above. Gain the root access first:

    sudo dont-blame-hipchat
  7. Modify the file using nano or any text editor of your choice:

    nano /hipchat/config/site.json
  8. Once the file is edited, exit using CTRL+X then Y to save same file name.

  9. Run chef-solo using the command cs.

Last modified on Nov 2, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.