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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Migrating JIRA/Confluence apps.

Having moved JIRA and Confluence together from previous location to a new server, JIRA logs in ok but Confluence does not. Error seen in conf logs: "authenticateUser Directory 'JIRA Server' is not functional during authentication of 'dbarter'. Skipped."

some more error trace and then:

" Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to <old server ip address>:8080 [/] failed: connect timed out"

Have I missed updating something in JIRA with the old server details? JIRA governs logins for Confluence. I have updated Application Links, base url and userserver in JIRA to refer to new server location.

Any help much appreciated.

1 answer

0 votes

The user directory settings are totally separate from the application links in each application.

In your Jira, you've done the right thing and updated the user server, but you do not mention telling Confluence that the user server (user directory) it is using has moved.

As an admin, go to admin -> user directories, find the Jira user server entry and edit it - you should find it points to the old server, which you can overwrite with the new one.

Thanks Nic, when I go to User Directories under User Management there are 2 entries: Delegated LDAP Authority which is not editable and JIRA internal directory which is editable but comes up with a screen for Directory Settings with the only option to "save and test" or "cancel". Have I missed something? The JIRA user server under User Management has the correct IP address in it and also "::1" and "".


Hi Nic, We tried again with this migration and bumped up against the same issue. I have since seen a recommendation to edit a Confluence database entry for crowd directory and although I didn't check during the migration attempt it would appear that this could be the key. What do you think?

You should go to the internal directory and make sure there is an account you can log into that has full system admin rights.

If you log in with that user instead of your account from LDAP, you will find it can now edit the LDAP connection - this happens because Confluence does not let you edit the settings for the directory you are logged in by.

Thanks again Nic. Yes we had an admin account that isn't used and after resetting the password I can edit the JIRA directory settings from within Confluence. If I just update the server address will it keep the account and password that are also on the screen? Not sure I know what the password is/should be so it would be better to leave that as it is.

I may have answered my own question as it appears in plain text in the cwd_directory_attribute in attribute application.password. If so then that's brilliant and mission accomplished. Gold stars from me.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

Announcing Team Calendars in Confluence Data Center

Hi Community! We're thrilled to share that Team Calendars for Confluence is now a built-in feature for Confluence Data Center releases 7.11 and beyond.  A long time favorite,  Team Cale...

78 views 0 3
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