We are no longer able to login in JIRA

Question

When we try to login, the login page always come back over and over. Also we have this message in our Dashboard :

*************************************************************
Dashboard Diagnostics: Mismatched URL Scheme

JIRA is reporting that it is using the URL scheme 'https', which does not match the scheme used to run these diagnostics, 'http'. This is known to cause JIRA to construct URLs using an incorrect hostname, which will result in errors in the dashboard, among other issues.

*************************************************************

The last change we made is to deactivate the default administrator account, since my account is member of the administrator group. We done that because we recently bought a 3 users licence and the administrator account was the 4th one. We were also charging data directly into the database via a script. (We can provide more détails about this).

We tried to reboot the Ubuntu virtual machine many times with no success. We also tried to restore to a 13 days old snapshot before the issue and we have the same problem.

Charles Dallaire · Answer

Thanks for the quick response !  I think we broke our database because of direct data charging.  We are new to JIRA and we learn from our errors.  We are currently creating a new Ubuntu server with a fresh install.  Our goal is to import data from our current CMDB (C2) to JIRA Insight.  I think the good way to import data is by using the import/export tool in JIRA.  Is it possible to import data from an excel file ?  If yes, what is the correct formating ?  Thanks !

Nic Brough -Adaptavist- · Answer

Two things:

1. You say "We were also charging data directly into the database via a script"

NO.  Stop doing that now, and ideally go back to a backup you took before you started doing.  It does not work, you will break your system.  Never never never run database changes to a Jira database while it is running, and generally, don't do it even when it's stopped.

2.  The error message you're getting is likely to be because of a misconfiguration in the proxy connector.  What do you have for your base url and for the scheme in <jira install>/conf/server.xml ?