Unable to get HipChat to work after manually migrating HipChat to AWS Beijing (China)

Hi, I followed the guideline from here to migrate the root volume (/dev/xvda) of HipChat from AWS Japan to AWS Beijing. After the migration every process seems to be working fine but I cannot access HipChat via the web application link, it always returns with a "ERR_CONNECTION_TIMED_OUT" on my Chrome. I checked both AWS security groups as well as instance's iptables, nothing seems to be the culprit. 

tetra.err.log:

admin@ip-172-31-9-147:/var/log/hipchat$ tail tetra.err.log
2016-09-19T02:44:04.767511+00:00 ip-172-31-9-147 tetra-app-1: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:44:04.978129+00:00 ip-172-31-9-147 tetra-app-0: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:44:53.911459+00:00 ip-172-31-9-147 tetra-proxy-0: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:44:57.564023+00:00 ip-172-31-9-147 tetra-proxy-1: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:45:04.767467+00:00 ip-172-31-9-147 tetra-app-1: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:45:04.978049+00:00 ip-172-31-9-147 tetra-app-0: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:45:53.911350+00:00 ip-172-31-9-147 tetra-proxy-0: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:45:57.564041+00:00 ip-172-31-9-147 tetra-proxy-1: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:46:04.767463+00:00 ip-172-31-9-147 tetra-app-1: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:46:04.978077+00:00 ip-172-31-9-147 tetra-app-0: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.

 

 

 

 

admin@ip-172-31-9-147:/var/log/hipchat$ tail nginx.err.log
2016-09-19T02:43:03.584899+00:00 ip-172-31-9-147 coral-0: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:43:03.685113+00:00 ip-172-31-9-147 coral-1: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:44:03.584585+00:00 ip-172-31-9-147 coral-0: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:44:03.685236+00:00 ip-172-31-9-147 coral-1: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:45:03.584711+00:00 ip-172-31-9-147 coral-0: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:45:03.685129+00:00 ip-172-31-9-147 coral-1: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:46:03.584225+00:00 ip-172-31-9-147 coral-0: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:46:03.685186+00:00 ip-172-31-9-147 coral-1: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:47:03.584890+00:00 ip-172-31-9-147 coral-0: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.
2016-09-19T02:47:03.685201+00:00 ip-172-31-9-147 coral-1: [] ERROR: Unable to get feature flags: url=https://hipcaht.somedomain.com/api/features, err=User timeout caused connection failure.

2 answers

1 accepted

Accepted Answer
0 votes

This issue has been resolved and the resolution is documented in this knowledgebase: https://confluence.atlassian.com/hipchatkb/hipchat-server-hosted-in-aws-is-not-reachable-via-ip-address-or-fqdn-after-root-volume-migration-to-china-region-852722367.html

The main issue was that ports 80 and 443 are blocked in China AWS region. Admin will need to file for ICP Recordal or ICP License to host public content on AWS (China) in accordance with Chinese law and regulations. For more info, see these articles:

0 votes
Chuck Talk Atlassian Team Sep 18, 2016

Hello Chunchi Su,

Looking at the URL as shown in your ERRORs, it appears that there are two issues in the Source URL:

  1. The word HipChat is misspelled as 'hipcaht'
  2. The source URL is shown as 'somedomain.com'

I think that the correct URL would be hipchat.$yourdomain.com where the value for $yourdomain.com needs to be replaced with the actual domain that you are using.  The value hipchat.somedomain.com was intended to be replaced with your domain.

For Example: if your domain is: supercode.com then the HipChat URL would be

hipchat.supercode.com

The URL simply needs to match your domain in order to be migrated to the correct URL. 

I hope this information is useful for you. If you do need further assistance, please Contact Support for further assistance.

Sincerely,

Chuck Talk | Atlassian

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Aug 10, 2018 in Hipchat

What should I think about when migrating HipChat to Slack?

...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...

481 views 1 10
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you