You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am migrating crowd (2.4.0) to a new server. I followed this procedure:
Copied the folders, updated the config files, backed up the database and restored it to the new SQL Server. (MS SQL 2008r2)
Crowd started up with no problem and I believe it has a connection to the database. The issue I'm seeing is when I try to login, it's not accepting my password. I tried to do a password reset and I can seeing in the java command line area of Crowd that it is trying to send an e-mail to my correct e-mail address (the mail server probably needs reconfigured) but the e-mail doesn't come through.
Any ideas?? Thanks!
In order to get a better idea of your authentication failure, it would be necessary to review the logs. Specifically atlassian-crowd.log which is located in <Crowd_HOME_Dir>/logs/.
One of the common issue with migrated Crowd is users sometimes for get to follow the direction mentioned on our documentation, specifically this point:
Ensure that the address list includes at least the following items: 'localhost', '127.0.0.1' and the IP address or hostname of the machine that is going to receive the new Crowd instance. This list determines the hosts that can access the Crowd Administration Console.
If the new IP address of the server is not declared, it would be impossble to access Crowd trough the new server. Would it be possible for you to access Crowd trough a machine with a registered IP address on pre-migrated server.
I hope you can post your logs for review, please note that this is a public forum, so do cencored the logs if necessary.