we're running JIRA 4.3.4 and migrated the VM to a new environment. Old environment had have an httpd 2.2 as reverse proxy in the frontend using mod_proxy_ajp and mod_ssl. The new one has an apache 2.4.9 with mod_proxy_ajp and mod_ssl.
But now, the timesheet-Plugin failes due to the following error (in the browser):
An internal server error occurred when requesting resource https://jira.<domain>.net/rest/timesheet-gadget/1.0/timesheet.json.
The JIRA log says:
2015-04-07 09:46:12,580 TP-Processor3 ERROR rohozneanus 586x10636x2 17c390m 220.127.116.11 /plugins/servlet/gadgets/makeRequest [renderer.internal.http.HttpClientFetcher] Unable to retrieve response javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated ... ...
The ssl certificate is still the same and was not changed during the migration. But there was a change in mod_ssl with version 2.4.8 of the httpd and SSLCertificateChainFile has become obsolete. See: http://httpd.apache.org/docs/current/mod/mod_ssl.html#sslcertificatechainfile
We're running this setup for a lot of domains and the SSL encryption works fine. No employees or customers reported any errors due to a warning of their clients. But it looks like JIRA does not like bundled certificates. To be honest, I'm not sure if it's a Java 6 or JIRA related issue but any help is welcome. Anyone else running a similiar working setup?
Please let me know when I forgot something important.
Basically it seems like something is messed with your certificate. Have you tried to re-import the certificate in your instance?
These pages should be able to help you out:
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot