A question most likely for Atlassian:
To use FishEye with JIRA OnDemand, it currently has to be on port 80, or port 443 with related SSL.
Our existing FishEye is on a different port and we can't easily move it without a lot of other changes, since port 80 is also in use. There are complications around using port 443 with an SSL as well.
Are there any plans to remove this restriction on the port number for FishEye with JIRA OnDemand? Currently it would cause us some disruption and possibly cause us other problems to use it, and it's an obstacle in migrating to JIRA OnDemand.
I found the issue below, raised internally by Atlassian, but it's closed as "Not a bug".
Based on that, I'm not sure whether to raise a change request, as it may also be considered "Not a bug".
Does anybody else have an opinion, or know Atlassian's position on this?
Due to security limits in OnDemand, all external Application Links must go through Port 80 and 443, all other ports are not available.
Atlassian is currently not looking into changing this restriction in the near future.
What you could do as an alternative is run Fisheye via Apache for example and use a virtual host to allow Fisheye to be reachable via Port 80 or 443. Some info can be found here - https://confluence.atlassian.com/display/FISHEYE/Integrating+with+other+web+servers
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs