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

504 error after IP change

Ben Stone I'm New Here Jun 09, 2021



I'm hoping someone here can help as I've about run out of ideas. We currently run a couple of Confluence instances, one for testing, one in production. They both run on Centos, and have been running fine.


We are currently in the process of a network migration, during which I have to change the IP address of the Confluence servers. When I change the IP of these servers I can get to the log in screen fine, however when I try to log in I get a 504 gateway timeout error.


I can still log in as admin, so I know the server is up. The issue only seems to affect LDAP users. Every now and again I find that the login completes just fast enough to not get the 504 error, so I know that in theory there are no network, or routing issues. 


As soon as I change the IP back, the gateway timeout goes away, and users can log in again instantly.


My guess is that something is caching the old IP address somewhere, but I've gone through every log file, and config file I can find, and I've not found anything. Basic ping tests show that DNS is resolving to the correct IP.


Has anyone ever seen anything like this before?





1 answer

0 votes
Brant Schroeder Community Leader Jun 16, 2021

@Ben Stone Welcome to the Atlassian Community.

If you are able to log in utilizing the local Jira directory but are timing out on LDAP it sounds like a routing issue.  Can you traceroute the request from Jira to your LDAP server?  Sounds like the request is routing back to the old instance.  I am assuming that the LDAP server is using the hostname to connect and this is routing to the old IP address.

Also what are you seeing in the Jira logs?

Suggest an answer

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

Miss the Confluence demos at Team 21? Watch them here!

Phew, Atlassian Team 2021 blew by. With dozens of demos and a handful of keynotes, you may have missed some of the awesome Confluence Cloud sessions. Don't' worry, you can watch them all here or on Y...

366 views 2 6
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