Thank you! My SE is: SEN-17394073
I have new problem.
My default site is http://sd.corp.ascania.ua:8080
I edit my Server.xml:
<Connector acceptCount="100" connectionTimeout="20000"
relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>"
disableUploadTimeout="true" enableLookups="false"
maxHttpHeaderSize="8192" maxThreads="150"
minSpareThreads="25" port="8080"
protocol="HTTP/1.1" redirectPort="8443" useBodyEncodingForURI="true"/>
<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>"
maxHttpHeaderSize="8192" SSLEnabled="true"
maxThreads="150" minSpareThreads="25"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2,TLSv1.3"
clientAuth="false" useBodyEncodingForURI="true"
keyAlias="jira" keystoreFile="/var/atlassian/application-data/jira/jira.jks"
keystorePass="Pass" keystoreType="JKS"/>
and web.xml:
<security-constraint>
<web-resource-collection>
<web-resource-name>all-except-attachments</web-resource-name>
<url-pattern>*.jsp</url-pattern>
<url-pattern>*.jspa</url-pattern>
<url-pattern>/browse/*</url-pattern>
<url-pattern>/issues/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
I added https://sd.corp.ascania.ua:8443/* in white list (expression with mask)
And now I have
Hi,
Sorry to hear about this problem. I can see that you have a dashboard gadget that is not working correctly, and appears to be generating a gadget.common.error.500 message.
We have a KB that is closely related to this over in Jira activity stream gadget throws gadget.common.error.500. That article indicates this problem is typically caused by Jira lacking an SSL certificate of a resource it is trying to connect to. I would be interested to see if you can recreate this problem and then try to look at the $JIRAHOME/log/atlassian-jira.log file to see if you perhaps can find a PKIX Path Building Failed error here. If so that's a clear indicator of the source of this problem.
On that topic we have another document on how to resolve this in Unable to connect to SSL services due to "PKIX Path Building Failed" error.
I hope this helps.
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.