Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


How to fix double logins / failed logins authenticating against Crowd / JIRA


If you need a second login attempt with any of your Atlassian Applications authenticating against Crowd or JIRA reduce your load balancer / reverse proxy timeouts!

HaProxy and AWS Load Balancer

I’ve seen two systems where logins from Confluence and HipChat would constantly fail on the first attempt and then succeed on the second.

Error messages were along the lines of:

User Directory 'JIRA test Server' is not functional during authentication of 'zf2wyft'. Skipped.

This was for an environment with HaProxy as reverse proxy. Confluence would try to authenticate against Crowd and often, but not always fail on the first attempt. The workaround in that case was to target the local ip instead of the load balancer.

But then the problem appeared again when using the AWS Classic Loadbalancer. In that case HipChat and Confluence were authenticating against JIRA. The symptoms were the same. I coincidentally found that reducing the timeout on the Load Balancer fixed the problem. We went from 3600s, as per Atlassian AWS Cloudformation Template to 60s. Problem solved.

So I went back to the HaProxy system and changed the timeouts there also:

We went from:
timeout connect 50s
timeout client 500s
timeout server 500s
timeout connect 10s
timeout client 60s
timeout server 60s

Once again, problem solved.

I was in contact with support in both cases and we were all stumped so I thought it put this into a googleable place...



Log in or Sign up to comment