I am running Jira Server 7.11 on Linux in Amazon with MySQL. The webserver and database are running on separate EC2 instances.
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?
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.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events