I have also experienced this issue when using the server on the corporate network behind a proxy.
However, if I place the server on an internet-facing section, this error does not appear.
So it seems to be a problem when on a network that uses a proxy server—for me at least.
We've been having the same issue. Not sure if this will help anyone, but I've been able to trace our issue down to communication to the marketplace being blocked by the firewall and proxy. Looking at the logs indicates that even with a home grown descriptor, hosted internally, HipChat first attempts to check the marketplace for the capabilities. Opening communication to the marketplace seems to have resolved the issue for us.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs