We need to change base URL

[Bose Kamineni]

JIRA 7.1.4

Jira is installed on a linux server 

we have an entry http://<linux server>.<institute>.edu/jira for base URL

We want users to use another URL - http://<web server>.<institute>.edu/jira where requests go through F5

I am wondering if I can update base URL from hhttp://<linux server>.<institute>.edu/jira to http://<web server>.<institute>.edu/jira and that would work.

Thanks,

Bose Kamineni

[Nic Brough -Adaptavist-]

It will, as long as your DNS resolves the new url correctly.

[Bose Kamineni]

Nic,

Thank you very much- we changed the base URL and able to access Jira. I will wait from response from users if they face any issues.

I have one question- 

After I log out I see the warning message-

JIRA's base URL is set to http: <webserver>/JIRA but you are accessing JIRA from http: <webserver>/JIRA  

Update JIRA's base URL

I verified and base URL is already updated- I am curious why it gives this warning.

Bose Kamineni

[Nic Brough -Adaptavist-]

Are the two http://<webserver>/JIRA lines absolutely identical, letter for letter?

[Bose Kamineni]

Nic,

I verified both are identical

JIRA's base URL is set to http://dci.duke.edu/jira but you are accessing JIRA from http://dci.duke.edu/jira

This is a warning message- but users had sent me an email about a problem

Dashboard is not displayed correctly

We've detected a potential problem with JIRA's Dashboard configuration that your administrator can correct. Hide

Dashboard Diagnostics: Mismatched URL Hostname

JIRA is reporting that it is running on the hostname '<hostname>.dhe.duke.edu', which does not match the hostname used to run these diagnostics, 'dci.duke.edu'. This is known to cause JIRA to construct URLs using the incorrect hostname, which will result in errors in the dashboard, among other issues.

The most common cause of this is the use of a reverse-proxy HTTP server (often Apache or IIS) in front of the application server running JIRA. While this configuration is supported, some additional setup might be necessary in order to ensure that JIRA detects the correct hostname.

The following articles describe the issue and the steps you should take to ensure that your web server and app server are configured correctly:

[Bose Kamineni]

Nic,

since dci.duke.edu is a proxy server so I might need to make additional configuration so that  users will be able to see the dashboard.

I found two document links - they might be helpful in resolving the issue with mismatched URL hostname

http://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Apache

http://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Apache+using+SSL

[Nic Brough -Adaptavist-]

Ah, I see the problem.

You have a proxy effectively running one url, and your base url set to another.

This does not work.  You need to run everything on the url that your users will be using.