I'd like to set up Jira to work behind the proxy of Fortigate VPN Portal.
The problem is that Fortigate builds its URLs as such (subdomain of your choice here):
where http://jira.local is an intranet address of my Jira Instance.
Because of this, there are issues with Jira resolving url when connected via Fortigate VPN Portal, for example 'Issue Details Screen' has no scrollbar or there are some css missing (icons in the left pane).
Is there any solution to this? For instance with server.xml configuration or with nginx reverse proxy configuration? I've read that in nginx I can use RegEx to match dynamic url, but question is if Jira (or Conluence for that matter) will understand it?
Ideally I'd like to also keep my local setup so I can link Jira and Confluence directly in intranet.
Unfortunately, Jira only supports 1 BaseURL, so I believe there isn't a way for you to set up this.
Accessing Jira from a different BaseURL, you will face issues like mentioned on this https://confluence.atlassian.com/jirakb/fix-gadget-titles-showing-as-__msg_gadget-in-jira-server-813697086.html KB.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
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