We were recently trying to migrate our app behind an AWS elastic load balancer (ELB). Due to some configuration issues, the ELB started generating a "504 Gateway Timeout error" on the browser.

As a result, we decided to remove ELB and go back to our original configuration. Essentially we changed our DNS A records. However, the browser (Chrome in this case) continued to give us 504 errors. We could visit our app in incognito mode or using another browser which had not seen 504 error.

The only solution was to clear the browser cache/cookies (clearing cache alone did not work). After performing this step, everything was fine.

I am still perplexed by this issue. How is the browser not able to redirect after DNS record changes? What has cookie got to do with this?

closed as off-topic by Rubén, jonsca Aug 14 at 2:21

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "It is a question about creating/developing a web application." – Rubén, jonsca
If this question can be reworded to fit the rules in the help center, please edit the question.

  • Browser questions are off-topic here. This might be on-topic at Super User, but I suspect it would be closed there due to it being a "server" issue with your DNS. – jonsca Aug 14 at 2:22

Browse other questions tagged or ask your own question.