/
Dashboard Hub Pro: "No compatible datasource" error when configuring gadgets

Dashboard Hub Pro: "No compatible datasource" error when configuring gadgets

Problem

The error message, “There is no compatible datasource for Jira” displays, and gadgets cannot be configured. A warning on the gadget list screen indicates that no compatible data sources are available.

Error message stating that there is no compatible datasource for Jira
Error message at the top of the page that states the following gadgets don't have a compatible datasource.

The following error message displays when attempting to add the instance as a datasource within its own instance:

Error adding datasource, check the URL, if the app is installed or you have access to that instance.

This page displays an error message - Error adding datasource. Check the URL if the app is installed or you have access to that instance.

Solution

  1. Make sure the Jira base URL is correct.

  2. Check the atlassian-jira.logs and identify whether the following timed-out error is logged. This error displays when the Jira instance behind the load balancer can’t find the IP address based on the domain name.

    org.apache.http.conn.ConnectTimeoutException: Connect to <hostname>.com:443 [<hostname>.com/69.4.29.9] failed: Connect timed out at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376) at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:108) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) at com.atlassian.gadgets.renderer.internal.http.WhitelistAwareHttpClient.execute(WhitelistAwareHttpClient.java:52) at com.atlassian.gadgets.renderer.internal.http.ShindigApacheClientAdapter.execute(ShindigApacheClientAdapter.java:43) at com.atlassian.gadgets.renderer.internal.http.HttpClientFetcher.performRequest(HttpClientFetcher.java:129) at com.atlassian.gadgets.renderer.internal.http.HttpClientFetcher.fetch(HttpClientFetcher.java:77)

 

  1. Contact your network administrator to verify the network configuration.

  2. An alternative solution is to create a datasource manually by setting the server's internal IP in the URL. (Check with your Network/IT team for the server's internal IP address.)