I am working to get a new HipChat Server set up. I have a wildcard SSL certificate that the Powers-That-Be insist should work fine. On the surface it does appear to work.
Unfortunately, I'm running into a litany of errors, the most serious of which is that all integrations are failing. Some are failing to setup at all (Confluence, Stash/BitBucket), and some install, but notifications fail to arrive (JIRA, Jenkins). I've also run into issues installing new integrations (Alias and Standup, to be specific) that fail with 500 internal server error.
The system is running entirely internal to our corporate network, but it is able to connect out to the internet.
Should the wildcard certificate work? Or do I need to push for a host specific certificate to be created?
On our system requirements page, it lists that port 443 TCP be open to the internet so that integrations can install and work. Most integrations rely on third-party servers to process the query/information using their API's (think GitHub or Giphy) so this is the reason for the requirement.
Of course, you can run HipChat Server completely shut off from the web, it's just that all integrations will fail to install. The caveat to that are the Atlassian core server products (JIRA, Confluence, etc) which have the HipChat integration already installed server-side and can be configured to communicate without reaching out to the web.
I hope this clarifies!
HipChat Server Support Engineer | Atlassian
...from the beginning. We have built up a lot of content in HipChat, with it being a core tool in our distributed company model. While it is true that we didn’t need to move to Slack immediately, we felt it...
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