Is it always a requirement to edit the server.xml?

[MP32]

I was under the impression that I would have to edit my server.xml file just to access the Jira configuration dashboard- however, I was able to do so without touching the file. 

Now my only problem is that when I try to create a new project, I get this error 

Error creating project, XSRF check failed

From what I read online it's because my server.xml file isn't configured properly. I'm a JIra newbie, so this might be obvious, but is editing the server.xml file a requirement to run jira 100% of the time?

I have Jira deployed to an instance on AWS- if I want to migrate Jira to another instance, can I simply just copy the server.xml file over to the appropriate directory on the new instance and Jira will work smoothly on the new instance?

[Tim Perrault · Accepted solution]

Hi @MP32 

No not technically required, but I'm assuming you want to access the site over HTTPS. That will require you to update the server.xml file.

Thanks,

Tim

[MP32]

I have my load balancer taking in HTTPS traffic but then it forwards it to the Jira instance as 8080. I changed the configuration of the HTTP connector as per this document

However, I'm still getting that same error. Here's what my http connector looks like in my server.xml file

---

<Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"
maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" scheme="https"
proxyName="cf-tf-test-domain.link" proxyPort="443"/>

[MP32]

I made sure to comment out the default connector and my loadbalancer target group is using HTTP1

[Tim Perrault]

I mean that looks correct. The only question I have is the proxyName just an example for this post? Just want to make sure you are using correct thing there. For example if my jira was located at https://example.com I would put proxyName="example.com".

The only thing that I have in my instance's server.xml file that is different from yours is the secure flag. in between bindOnit="false" and scheme="https", I have secure="true".

<Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"
maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" secure="true" scheme="https"
proxyName="jira.example.com" proxyPort="443"/>

[MP32]

I noticed that secure="true" is in the HTTPS connector by default, but not the HTTP one. That's also my actual proxyname I'm using, which points to my loadbalancer. I tried it with and without secure="true" and neither configuration is working. Do I have to completely re-deploy Jira or can I just change the server.xml file while it's up and running?

[Tim Perrault]

You won't need to re-deploy, but a simple stop and start of Jira will make it so that the changes made are used. After any changes are made it will usually require a restart.