Gadget throws javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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.
*Except Fisheye and Crucible
Summary
Symptoms
The following appears in the atlassian-jira.log:
012-11-06 13:10:16,422 http-172.17.18.8-443-7 ERROR administrator 790x405x1 122nnop 192.168.110.2 /plugins/servlet/gadgets/makeRequest [renderer.internal.http.HttpClientFetcher] Unable to retrieve response
javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at com.sun.net.ssl.internal.ssl.SSLSessionImpl.getPeerCertificates(SSLSessionImpl.java:352)
at org.apache.http.conn.ssl.AbstractVerifier.verify(AbstractVerifier.java:128)
at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:339)
at com.atlassian.gadgets.renderer.internal.http.HttpClientFetcher$CustomSSLSocketFactory.connectSocket(HttpClientFetcher.java:193)
at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:123)
at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:147)
at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:101)
at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:381)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:576)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:554)
at com.atlassian.gadgets.renderer.internal.http.HttpClientFetcher.fetch(HttpClientFetcher.java:111)
at org.apache.shindig.gadgets.oauth.OAuthFetcher.fetchFromServer(OAuthFetcher.java:802)
at org.apache.shindig.gadgets.oauth.OAuthFetcher.sendOAuthMessage(OAuthFetcher.java:581)
at org.apache.shindig.gadgets.oauth.OAuthFetcher.fetchRequestToken(OAuthFetcher.java:334)
at org.apache.shindig.gadgets.oauth.OAuthFetcher.attemptFetch(OAuthFetcher.java:274)
at org.apache.shindig.gadgets.oauth.OAuthFetcher.fetchWithRetry(OAuthFetcher.java:230)
at org.apache.shindig.gadgets.oauth.OAuthFetcher.fetchNoThrow(OAuthFetcher.java:188)
at org.apache.shindig.gadgets.oauth.OAuthFetcher.fetch(OAuthFetcher.java:169)
at org.apache.shindig.gadgets.http.ContentFetcherFactory.fetch(ContentFetcherFactory.java:54)
at com.atlassian.gadgets.renderer.internal.http.TrustedAppContentFetcherFactory.fetch(TrustedAppContentFetcherFactory.java:44)
at org.apache.shindig.gadgets.servlet.MakeRequestHandler.fetch(MakeRequestHandler.java:84)
at org.apache.shindig.gadgets.servlet.MakeRequestServlet.doGet(MakeRequestServlet.java:55)
at org.apache.shindig.gadgets.servlet.MakeRequestServlet.doPost(MakeRequestServlet.java:65)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at com.atlassian.plugin.servlet.DelegatingPluginServlet.service(DelegatingPluginServlet.java:42)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at com.atlassian.plugin.servlet.ServletModuleContainerServlet.service(ServletModuleContainerServlet.java:52)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) <+14> (ApplicationFilterChain.java:290) (ApplicationFilterChain.java:206)
However, the above stack trace does not tell us the exact gadget that is throwing the error.
Diagnosis
From the stack trace above, we can tell that the error was triggered by 'administrator'. 'administrator' can check his dashboard for any error on the configured gadget to find out which gadget is causing the problem.
Cause
For this case, the gadget that is throwing the error is JIRA Issue Links Matrix.
Solution
Resolution
Disable the JIRA Issue Links Matrix Plugin. If you are using JIRA 5.x or above, this plugin is not compatible with your JIRA version and its best to disable this plugin.
If you do not have JIRA Issue Links Matrix gadget configured, please open a new ticket to https://support.atlassian.com
Was this helpful?