The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

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

ramani_chandran
Contributor
June 29, 2018

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

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
Answer accepted
Craig Castle-Mead
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
June 30, 2018

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

ramani_chandran
Contributor
July 6, 2018

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?

TAGS
AUG Leaders

Atlassian Community Events