Setting up new JIRA - Lots of issues

[Thomas Caraccia]

I installed JIRA 7.4 on a server running server 2012r2

I am able to reach the base url when it is localhost:8080

I am also able to reach the URL when it's localhost:8443 and I bind a Selfsigned cert to using config.bat I need help with:

1. how can i set the URL to a different hostname? I have a non-publically routable domain that I am using to test purposes. I went into IIS and added the ISAPI filters and use the URL rewrites to get the address to change to jira-dev.domain.com when I do that I make sure I update the base URL inside of JIRA. but, when i run it from a browser and it opens. I am getting a multitude of errors. 

     a. I'm getting an error with a gadget that will only how__msg.gadget

     b. all of my photos that i imported are showing as broken links.

     c.  most of the time I still need to add the port to the end of the url for routing.

     d. im also getting a gadget feed error when logging in.

2. I would perfer to be able once this box is in production not to touch tomcat, and have all of the SSL certs go through IIS (i am more familar with it) but i am unable to get this to work with the domain name. 

does it only have to do with the fact i'ts a self signed cert, if I added a CA cert will that remidiate the issue? Any assistance to get this dev version of jira running would help me greatly.

[Shankar Asam {Appfire}]

You can get rid of context path from server.xml and set Context path=""

And, self signed certs should work perfectly with gadgets/dash boards

[Thomas Caraccia]

Yes I have to imprort my cert into the java cert store. which i did now the gadget loads correctly, but its not loading any of the data its just a blank box.

[Shankar Asam {Appfire}]

So how are you accessing it now? If you want to access on port 80, then you might use a proxy or webserver in front of the JIRA and configure proxypass directives to route on jiraserver on port 8080 or if you don't have any web server then you can simply edit the server.xml and replace connector port 8080 with 80 and start the JIRA. You need root privs to run the JIRA as lower ports (ex: 80) can be run only by root. 

[Thomas Caraccia]

AS of right now I am hosting it simply with updating the base URL and then appending the port number at the end. How could I setup a reverse proxy with IIS on SSL?

[Nic Brough -Adaptavist-]

I recommend doing that in two steps - proxy first, then add SSL to it.

Start with https://confluence.atlassian.com/adminjiraserver071/integrating-jira-applications-with-iis-802593039.html

[Thomas Caraccia]

Now, if am not going to use a context path how do I handle this document?

[Thomas Caraccia]

How come everytime i add SSL and a selfsigned cert, I am getting the Gadget issue? Is that only with a selfsigned cert, or is that related to SSL

[Nic Brough -Adaptavist-]

It's SSL, self-signed certs will work.

Have a look at the log file to see what the errors are.

[Nic Brough -Adaptavist-]

Point c is the one that stands out to me.  Either you always need to enter a port, or you never need to.  If you need to enter it some of the time, that tells me the network is not routing port 80 (or 443?) irregularly which will break your gadgets, pictures and feeds exactly as you describe.

[Thomas Caraccia]

So I decided to completely blow out everything and start over. I setup everything and changed my base URL to my devurl (in HTTP) and that is working, but I have to also append the port to the end, how can have it respond on 80 instead or rather 443?

[Nic Brough -Adaptavist-]

You could reconfigure the Tomcat to run on port 80, but it's better to stick a proxy in front of it.

[Shankar Asam {Appfire}]

Thomas,

If you see any msg.gadget errors on JIRA, the below links will help you understand the problem.

https://confluence.atlassian.com/jirakb/how-to-fix-gadget-titles-showing-as-__msg_gadget-813697086.html

https://confluence.atlassian.com/confkb/internal-gadgets-displaying-titles-as-__msg-935392222.html

[Thomas Caraccia]

While i've read these items, and attempted the fixes. I am still unable to resolve this particular issue.