Degraded performance Customers may experience issues using Community search. Our team is investigating.
I have created a redirect url, so that the users can connect easier to it.
the name of the redirect is : jira.xyz.co
the redirect is working fine, and it takes me to the desired destination url, but without DNS resolution.
I’m trying to figure out for the redirect to have the below view when the users type: jira.xyz.co
to forward them to the below link
I think he needs both, Harry - a DNS entry for his 18.104.22.168 jira.xyz.co host and a proxy - rewrite or ajp - to provide a 'pretty' url to his users.
If he just does the DNS fix his users would have to enter the port and context to get to the server, like http://jira.xyz.com:8080/jira - the proxy would fix it so they could just enter http://jira.xyz.com (and hopefully then config'd to forward to https://jira.xyz.com).
@bardhyl - setting up the rewrite or ajp proxy is very easy in Ubuntu with simple commands to enable/disable modules that you'll need - and I'd go into the jira server's server.xml file (located in your <jira base>/conf directory - <jira base> is the root directory of where you installed JIRA. There will be a line that starts <Context path="/jira" docBase= - change it to read <Context path="" docBase= instead.
For Apache config on Ubuntu check this search out:
This page had some nice 'background' intel for folks new at apache config on ubuntu:
dude...to do that you have to run tomcat as root - with all the security issues that've been reported over the last couple years - no company I've worked with would want/allow that. And setting up SSL with apache is just _easier_.
Plus Apache gives you performance improvements and better handling for multiiple simultaneous requests.
But to each their own...the important thing is security, stability, and happy users - and you can have 2 of those.
Please stop giving false information. You can run Tomcat like that via iptables 8080->80 or using authbind for Tomcat to run on port 80. No need for root. Same can be done for 443.
Not sure where you've worked etc.
Putting Apache increases load. The old Tomcat needs to be fronted by Apache is a very old theory that no longer applies. Current Tomcat (7+) easily holds on its own.
Harry, why do I need an A record instead of keeping the redirect thats allready created, and also you commented to update the jira base url, what do I need to change on the base url, currently my jira base url is configured as: http://xx.xxx.xx.xx:8080/jira, where the symbol x represents the ip number. Thnx.
JIRA only accepts 1 base URL. A lot of things will break if you try to access it from multiple URL redirects/cnames. It's not supported.
So stick with 1.
Your base URL should be the URL you want to use to access JIRA and what others would be using, i.e. what's customer facing. Avoid redirects.
Yup, you *can* use redirects if you want, but they only have limited uses.
Jira won't run on several urls, it runs on a single distinct base url and expects people to use that. Redirects are pretty useful for catching people who may have old bookmarks or notes pointing to where you moved a system from when you changed the location, but that's about it.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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