Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,464,264
Community Members
 
Community Events
176
Community Groups

crowd still pointing towards the old version 2.8.4,but the new version 2.9.1 was already in place

can anyone please help me on this issue, i have crowd 2.9.1 running before the ssl certificate upgrade ,once after the import i restarted the crowd,then it started running with the old version 2.8.4. i have started crowd by going into the crowd-latest folder which is pointing to the latest version,later i came to know that the crowd-latest folder was pointing the crowd old version 2.8.4. now how can i start crowd with the latest version?

1 answer

1 accepted

1 vote
Answer accepted

Sounds like you may just need to change the crowd-latest folder symlink to point to 2.9.1

Failing that, step through your setup (dns > reverse proxy > crowd config etc) and re-validate everything. I’ve found it can be very helpful doing this with another person. Talking through the setup is sometimes enough to realize a small config problem.

 

CCM

Hi Craig,

Thanks for your reply, there was one proxy port and url missing in the server.xml after updating that it started working.

After that yesterday when i stopped and restarted for some other changes to take place,it was showing apache tomcat 404 error while loading the url in browser, but the application is up and running at the back end,Could you please suggest what might be the problem?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events