How to change Jira 7.11 base URL without web interface after cloning VM?

[Josh Wyatt]

I am running Jira Server 7.11 on Linux in Amazon with MySQL. The webserver and database are running on separate EC2 instances.

The production deployment of Jira server runs on the URL https://jira.mydomain.net and I want to clone it into a test deployment that runs on the URL https://jira-beta.mydomain.net .

In preparing to test the upgrade process, I created AMI images of the webserver instance and the DB instance, and spun up new instances based on these images. The database comes up fine; tomcat on the webserver comes up and connects to the database after editing /opt/var/atlassian/application-data/jira/dbconfig.xml to reflect the new database location/IP.

Upon startup, the test instance still appears to be trying to connect to itself at "https://jira.mydomain.net" as reported in /opt/atlassian/jira/logs/catalina.out - but this times out, as expected (thankfully). The web interface is, of course, unavailable.

How do I convince this newly cloned Jira deployment that its base URL is actually https://jira-beta.mydomain.net?

[Matt Doar · Accepted solution]

update propertystring, propertyentry set propertystring.propertyvalue = 'https://jira-bet.mydomain.net' where propertystring.ID = propertyentry.ID and propertyentry.PROPERTY_KEY = 'jira.baseurl';

is how you do it in on-prem Jira. 

[Josh Wyatt]

Success! Thank you. Is this referenced anywhere in the Jira documentation?

[Matt Doar]

https://confluence.atlassian.com/jirakb/change-the-base-url-of-jira-server-in-the-database-733940375.html is pretty close