nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

why must I reinstall Jira again?

noe.garza@garlandtechnology.com

I updated Jira two weeks ago.

We had connections isses, so after reasearching I updated file dbconfig.xml, adding a useSssl=false.

When I restarted Jira, it's acting like licence was never installed!

The installation I did before was not exactly smooth, and I don't want to go through it again as I have other work to do, especially if it will kick me out again.

Accepted answers

Nic Brough -Adaptavist-

You've changed the config in a way that makes Jira think you have an empty database and hence it needs to set it up to get you started.

All comments

Nic Brough -Adaptavist-

You've changed the config in a way that makes Jira think you have an empty database and hence it needs to set it up to get you started.

noe.garza@garlandtechnology.com

oh no!

I hope I haven't lost my tickets!

We 'updated' from bugzilla when a new employee (now gone) convinced us Jira was better. Small company here, 4-8 developers. We don't have an administrator or IT guy. One of us has to take time away from developing to administer tools and licenses. Upgrade needs to be a smoother process.

So far, regretting changing from bugzilla...

Nic Brough -Adaptavist-

I doubt you have lost anything. Typically if you change the dbconfig file and put something in it that breaks the connection or points it elsewhere, the original database is completely untouched.

I would take a backup of the database, just in case (I'm the sort who is paranoid and always gets a backup), then undo the changes you made to dbconfig so it can connect again. You should find everything is still there.

Then you'll need to take another look at the "connections issues", as your changes were obviously not a fix for them.

noe.garza@garlandtechnology.com

Fixed.

Nothing lost.

I modified conf/server.xml to use proxy.

Previous admin had setup an nginx proxy.

Jira uprade I did blew it away.

As I recall, upgrade procedure asked me to backup two files, I believe one was server.xml?...I didn't...

The ssl issue was warning connecting to mySql. As far as I can tell, this was never done correctly and warnings were always there...works, tho.

Thank you for your help.

Apologies for troubling you with my self-inflicted troubles...

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software