Changing the base URL of a server

[Martin Nørgaard]

Hi,

I recently migrated our production environment from one VM to another.

In this migration the host-name changed from:

jira.mycompany.com to jiraprod.mycompany.com

This created the issue that users were unable to use old links (as they pointed to jira.mycompany.com)

By making the old DNS-record point to the new IP the issue was solved, somewhat.

Some issues still persist, in that we have some login issues (when you press the 'Home'-button you are sent to jiraprod.mycompany.com and have to login in again, if you used an old link to access the instance.

I suspect, that if I can change the baseurl to jira.mycompany.com then the issue would be solved, but this triggers an failure in the Gadget Feed URL health-check.

How can this be circumvented?

The instance is not using a reverse proxy.

Thanks and regards,

Martin

[Nic Brough -Adaptavist-]

You should be using Jira on the base url.  The DNS routing of the old url is effectively wrong because it's not the base url.

A better "fix" for this is to throw up a web page on the old url that does nothing other than issue a permanent redirect to the new base url.

[Martin Nørgaard]

Hi Nic,

So you are proposing a 301 redirect instead of the current "fix"?
Would this also work for all of the "old" links that are directing to specific issues/projects/boards?

Thanks and regards,
Martin

[Nic Brough -Adaptavist-]

Yes, if implemented correctly - only the base url needs to be redirected, so you can pull the rest of the url the user has landed on and just replace the base url part of it before redirecting