Forums

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

Unable to log in with error 504

Alexander Bondarev
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 Leaders.
July 8, 2020

Hi!

Confluence Server 6.15.10

Some users (about 15%) have problem with log in into the system.
When entering the correct data (login / password) - they receive an error 504 (after 3-4 minutes).
However, we do not observe any information in the Confluence logs.
But if you enter an incorrect password, the user immediately receives an error about it. This information is displayed in the logs.

Our users are being pulled both from LDAP and from the internal directory. In the same directory there may be users who log in successfully and those who cannot log in. The problem is similar. 

Connection to the confluence goes through Nginx. In the logs of which there are entries that for some users the confluence returns a 504 error.

We haven't done any works or updates, but got this problem.

Do you have suggestions? 

1 answer

1 accepted

0 votes
Answer accepted
krhodes12 July 8, 2020

I am having the same issue with Confluence 7.0.4.  Only a small population is getting the error. Same issue  no entries showing in Tomcat or Confluence logs

Alexander Bondarev
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 Leaders.
July 8, 2020

Have you found any workarounds?

We temporarily create accounts in the internal directory.

Do you have any ideas on a possible cause of the problem?

krhodes12 July 9, 2020

I opened a ticket with Atlassian, also found this article.

https://confluence.atlassian.com/jirakb/active-directory-users-fail-to-logon-intermittently-945118456.html

 

I will post if i get confirmation on a workaround or if the above works

krhodes12 July 9, 2020

This is being caused by a firewall update for a High vulnerability issue found and released on 7/2/2020.

If you do a packet capture you should see illegal characters in Header 

Name: Multiple Cameras Information Disclosure Vulnerability 

Like # people like this
Alexander Bondarev
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 Leaders.
July 10, 2020

@krhodes12 , thank you!

Problem was with Multiple Cameras Information Disclosure Vulnerability.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events