If you’re using Cloudflare with WordPress, I advocate using their free plugin and excluding crucial URLs from caching (such as the WordPress admin dashboard). You can try fixing it with the other solutions mentioned under or contact your internet hosting provider’s support for technical assist. For fixing client-side DNS issues, you would try flushing your local DNS cache. You can disable the proxy server and examine out reloading the webpage to see whether or not it’ll repair the error.

There may be community configuration points like firewalls, misconfigured routes, etc. blocking communication between the web and software servers. The utility server itself might be down or unresponsive. The utility server might be alexhost.com operating too many processes and is overloaded.

A 504 Gateway Timeout sometimes lasts so lengthy as the server’s default timeout setting, which varies but is commonly around 60 seconds. Checking the website’s error log may help identify this drawback. Switching to a special web browser can single out whether a 504 Gateway Timeout error is restricted to your major browser. Whereas server-side points are usually the basis explanation for most 504 errors, they can additionally be triggered by client-side problems or false configurations. The 504 Gateway Timeout error occurs when the central server, as a gateway or proxy, doesn’t receive a well timed response from an upstream server. # Examine upstream_response_time to substantiate which upstream is timing out

  • A 504 Gateway Timeout means a proxy or gateway server (like Nginx, Cloudflare, or a load balancer) waited for the upstream/origin server to reply, however the upstream server took too long.
  • If packet loss seems, we examine bodily components (switch ports, NIC errors), digital components (overlay networks, mis-sized NAT gateways), and policy components (stateful firewalls timing out idle flows).
  • If your site is seeing a spike in visitors, contemplate upgrading your internet hosting plan.
  • Reducing 504 risk is in the end about matching workload shape to infrastructure shape.
504 Standing Code: What Is It & How To Repair It?

Step 3 — Restart Web Services

Rebooting these units may assist you to with fixing the issue. If ready and reloading the site doesn’t fix the 504 error issue, you’ll have the ability to examine whether or not a website is down for everybody or simply you. To take away the page’s browser cache earlier than reloading, you probably can press the CTRL+F5 shortcut combo as an alternative. You can press the F5 keyboard shortcut to refresh/reload the webpage in most browsers. One of the first things you possibly can try when encountering a 504 Gateway Timeout error is to attend a few minutes and try reloading the page.