Connection Status Of Hipchat Integration With Atlassian products are Shown As 'Not Connected' (Features are Working)

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Fisheye および Crucible は除く

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.

問題

Connection status of Hipchat integration with Atlassian products (Jira, Confluence, Bitbucket, etc) are shown as Not Connected as an example below. For example, Jira:

Not Connected would means the Atlassian product could not connect to the Hipchat Server. Integration features will be unavailable until the connection is restored. However in this case, the integration and its features are working as expected. You received notifications in Hipchat rooms where the integrations have been configured. In this example, Jira issue preview is working as well which is contradicted to the connection status.

You'll see the following error in atlassian-jira.log for example:

Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
	...
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
	at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:563)
	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
	at sun.net.www.protocol.http.HttpURLConnection.followRedirect0(HttpURLConnection.java:2661)
	at sun.net.www.protocol.http.HttpURLConnection.followRedirect(HttpURLConnection.java:2583)
	...
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338)
	at com.sun.jersey.client.urlconnection.URLConnectionClientHandler._invoke(URLConnectionClientHandler.java:240)
	at com.sun.jersey.client.urlconnection.URLConnectionClientHandler.handle(URLConnectionClientHandler.java:147)

診断

  • Ensure that you have installed Hipchat Server SSL certificate into Atlassian product / Java keystore and ensure the path/location is correct. 

    (info) A server restart is required to make sure the SSL certificate installation in server keystore is properly picked up.

  • If your Atlassian product has SSL certificate installed, you'll need to install this certificate into Hipchat Server keystore as well. 
  • Check /var/log/hipchat/coral.log from Hipchat Server and look for something like following to verify that the integration is making successful requests to the /addon/link API:

    2015-10-05T10:01:12.655870+00:00 test-hipchat coral-2: [/addon/link/c3EO5bM123daxrNibAMY#REQguUp5q] =====> New API request: #64, uri=/addon/link/c3EO5bM123daxrNibAMY, method=GET,  from=127.0.0.1, job_handle=none
    2015-10-05T10:01:12.657242+00:00 test-hipchat coral-2: [HiRedisClient,client] start call to None: 1
    2015-10-05T10:01:12.657709+00:00 test-hipchat coral-2: [HiRedisClient,client] Starting factory <twisted.web.client._HTTP11ClientFactory instance at 0x210fb48>
    2015-10-05T10:01:12.698507+00:00 test-hipchat coral-2: [HTTP11ClientProtocol (TLSMemoryBIOProtocol),client] after completion of call to None: 0
    2015-10-05T10:01:12.699273+00:00 test-hipchat coral-2: [/addon/link/c3EO5bM123daxrNibAMY#REQguUp5q] =====> API request complete: #64, uri=/addon/link/c3EO5bM123daxrNibAMY, in-progress=0, time=44ms

原因

The Atlassian product server does not have a valid SSL certificate for calling itself. 

ソリューション

  • Import the Atlassian product's SSL certificate into the JVM keystore of the machine hosting the Atlassian app and the ensure that the status shows as Connected after refreshing the page 
  • By doing this, the issue is resolved because it allows the Atlassian product to connect to itself.

最終更新日: 2018 年 1 月 19 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.