Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Crowd 3.7.0 console won't load - returns 504

After upgrading Crowd from 3.4.4 to 3.7.0 the console won't load. shows the "Set up Crowd" button, clicking on that button redirects to but this page won't load and returns 504 after 1 minute (browser timeout)

This happened with Crowd 3.5.0 as well. When going back to 3.4.4 everything works fine again.

Any help would be greatly appreciated

1 answer

0 votes
Gaurav Atlassian Team Nov 19, 2019

Hi @mw_sysop ,

I am sorry that you are facing issues while setting up the latest Crowd.

Can you please check Crowd logs and paste any errors that you see in the logs?

Also, how did you upgrade Crowd from 3.4.4 ? Can you please share the process



Gaurav Agarwal

Hi @Gaurav ,

The only errors I see in the log are about application links:

Caesium-2-1 WARN [atlassian.applinks.core.DefaultApplinkStatusService] Unrecognized error while attempting to retrieve status of Application Link 'c82cfacc-1197-3d0c-9b9f-ad6445787b73'

When the server is started and the main page with the "Set up Crowd" button is shown the log stays empty.

To perform the upgrade I used the tar.gz archive:

1) stop Crowd
2) download archive
3) extract
4) change ownership of the files
5) add MySQL connector to {INSTALL_DIR}/
6) change reverse proxy settings in {INSTALL_DIR}/apache-tomcat/conf/server.xml
7) set correct path to Crowd home directory in {INSTALL_DIR}/
8) remove symlink to old version
9) create symlink to new version
10) start crowd 

I have used the above process for all upgrades over the last few years

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

272 views 8 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you