Issue with log in to JIRA after creating new JIRA TEST environment. Recovery mode not working

[Alexandra Mihaela Apostol]

Hello,

We are trying to create a new jira-dev environment from jira-test environment. Until now: 
- we have created a new db and have used the import/export option to get the data
- we have cloned the server with all files
- I have updated the connector and JNDI configurations in the server.xml file to point to the new DB and updated the ssl.conf with new data.

After successfully restarting both the Apache and Jira servers, I am able to access the login page using the URL http://<server_ip>:8080/jira. However, once I enter my credentials, the application fails to log me in, even with a system admin account stored in the Jira internal directory. I have tried also recovery mode and it doesn't work.  Restore Passwords to Recover Admin User Rights in Jira Server and Data Center

Could this issue be related to the method used for copying the database?

I have also tried: 

• Disabling LDAP: In an effort to isolate the issue, I disabled the LDAP integration directly in the database, leaving only the Jira internal directory available. Unfortunately, this did not resolve the problem either.

• Safe Mode: I also tried starting Jira with all plugins disabled, but the login issue persisted.
  
  

Do you have any other ideas? We need to resolve this issue as soon as possible, as it's blocking critical operations on our end. Any assistance or insights you can provide would be greatly appreciated.

Thank you in advance for your support!

BR,
A.

[Ignacio Vera]

I'm pretty sure it’s not the DB copy — it’s almost always a base URL or cookie issue after cloning.

1. Base URL mismatch
   Check if the jira.baseurl still points to the old environment. Update it in the DB to match the new one.
2. Connector misconfigured
   If you’re accessing via http://server_ip:8080 but the connector has secure="true" or scheme="https", the session cookie isn’t sent. Try removing those flags or using the HTTPS proxy URL.
3. Shared or wrong home path
   Confirm jira-application.properties points to the correct $JIRA_HOME, not the one from the test instance.
4. Clear caches
   Delete $JIRA_HOME/caches and restart Jira after making the changes.

[Charlie Misonne]

I'm pretty sure it’s not the DB copy 

Indeed, otherwise the recovery user should work. You can always check if the cwd_users table contains anything to be 100% sure of course.

+ check your log files. There might be something related in there.