Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Imported xml backup from different server on a fresh install, starts up ok, but fails authentication

Sam Issa January 28, 2022

I am building test bed to test an upgrade before rolling into prod, 

I completed the install successfully, imported XML backup from prod instance successfully,

but when I try to login, I get the login screen ok, it recognise the userid i put in (if I put the wrong one it complains, so it is accessing mysql and checking the userid) then i put the password, at that point it redirect to "Page Not Found"  displays the standard confluence frame and top menu bad, but nothing works.

does anyone knows a reference to help overcome this blocker ? maybe manually clean up mysql db from the references to the prod instance ?

regards

Sam.

3 answers

1 accepted

2 votes
Answer accepted
Pramodh M
Community Champion
January 28, 2022

Hi @Sam Issa 

Don't follow XML backup restore method.

Install the same version of confluence in the test environment.

Copy home directory and db and connect them both.

You'll have test environment in no time

Here's the approach

https://confluence.atlassian.com/doc/create-a-staging-environment-for-upgrading-confluence-866094180.html

Thanks

Sam Issa January 30, 2022

Thanks Pramodh
I am now planning to use the recommended link, appreciate your help.

cheers.

Like Pramodh M likes this
0 votes
Daniel January 30, 2022

You could try to add

-Datlassian.recovery.password=[your-password]

to the CATALINA_OPTS in your setenv.sh and login as recovery_admin to fix the authentication.

Sam Issa January 30, 2022

Thanks Daniel, but that did not help, I ended up in the same loop, it seems it's also validating the password, I also have MFA implemented, I disabled it, but still didn't help, I think I will abort this attempt and try to rebuild using different method 

0 votes
Dave Theodore [Coyote Creek Consulting]
Community Champion
January 28, 2022

I would recommend logging in with a user that is in the Jira Internal Directory. If you are logging in with a user in an external directory, you can see this issue.  It may be that your directory service needs to have your Dev box's IP address whitelisted.

Dave Theodore [Coyote Creek Consulting]
Community Champion
January 28, 2022

Here's a trick that I have used when I run in to this problem. You can identify the local admin user and reset the password to something known.

Sam Issa January 30, 2022

Thanks Dave, I use internal directory. I will abort this try and try different method.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
7.15.1
TAGS
AUG Leaders

Atlassian Community Events