I have Fisheye 4.8.3 and use jks keystore with CA and SUB-CA and server certificates in the same keystore (very common scenario).
After test upgrade to 4.8.4 Fisheye refuses to start with following Jetty error:
How can i fix it??
Hello! I know you've already contacted us via support.atlassian.com but I thought I'd reply back here as well so that others can see the answer too.
This is a new bug introduced in Fisheye 4.8.4. Here's the link to the bug report:
This is caused by the fact we updated the version of Jetty bundled in Fisheye 4.8.4. If you're interested, this part of the code in the new version of Jetty is what's causing the problem.
The bug is part of our short term backlog, according to our Development Team Lead in this message we're planning to release the bug fix on Fisheye 4.8.6, expected early 2021.
If you're running into this issue consider staying on 4.8.3 while the bug hasn't been fixed yet. If you need to upgrade to 4.8.4 you may want to set up and terminate SSL at a reverse proxy in front of Fisheye and let the communication between Fisheye and the reverse proxy happen over HTTP.
Don't forget to add yourself as a watcher to the bug report to get notified when it's finally fixed.
On October 20, 2021, Atlassian published a security advisory for Jira Service Management. The full advisory is available at this link. We've seen a number of questions already asking for...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events