-2

Some of the application users get 504 Gateway Timeout errors while accessing some app links. However, it works fine for other users.

The app is hosted on Amazon Linux 2 AMI Apache Version: 2.4.57

Tried below troubleshooting steps,

  • Clear browser cache and cookies
  • Hard refresh browsers
  • Try a different browser or device or incognito mode
  • Check network connectivity
  • Test in a different device/PC
  • Test in different networks: such as a different Wi-Fi network or mobile hotspot, to determine if it's a network-related problem
  • Update the browsers to the latest versions
  • If the issue persists across all browsers, reset the browser settings to their default values.
  • Temporarily disable antivirus/firewall
  • Disable browser extensions
  • Update browsers and plugins: Ensure that the user's browsers and plugins are up to date. Outdated software can sometimes cause compatibility issues and result in a 504 error.

The 504 issue persists after trying all these steps. Let me know if require any further information on this.

How to resolve the 504 Gateway timeout error?

Manoj Agrawal
  • 429
  • 3
  • 10
PoojaA
  • 1
  • 2

1 Answers1

-1

The 504 Gateway Timeout error is an HTTP status that indicates that the server did not receive a timely response from an upstream server it needed to complete the request. You can start by checking if you have:

A problem with the upstream server, such as a hardware failure or software bug.

A problem with the network connection between the server and the upstream server.

A problem with the server's configuration.

A problem with the browser or other client software.

Since you have already tried the basic troubleshooting steps, I'd believe the problem lies with one of the above, if you're not sure specifically how to trouble shoot, there are many common practices for each check on the internet.

I'm not exactly an expert on the matter but I hope this helps a bit

niconico
  • 9
  • 2
  • Thanks @niconico for your response. I'll find and implement those steps you suggested. But I am curious to know why it works for most of the users without any error, and DOES NOT WORK FOR ONLY FEW USERS. So if it works for most of the users, does that mean the issue is not with the upstream server but at the end user? And even after trying above troubleshooting steps for end user, it is still failing. – PoojaA Aug 25 '23 at 04:21