How Do I Fix Error 502 On Google? Trust The Answer

Sometimes extensions or add-ons that you have installed on your browser, or applications that you have installed on your computer can prevent Gmail from working.

Try temporarily disabling these extensions and applications one at a time, and then use Gmail again to see if that fixes the problem.

To use Gmail without extensions, open Gmail in your browser’s incognito or private browsing mode.

A 502 Bad Gateway Error occurs when you try to visit a web page but one web server receives an invalid response from another. Usually the problem is with the website itself and there is nothing you can do about it. In other cases, this error occurs due to a problem with your computer or network equipment.

What is a 502 Bad Gateway Error?

A 502 Bad Gateway Error means that the web server you connected to was acting as a proxy to relay information from another server, but received a bad response from that other server. It’s called a 502 error because that’s the HTTP status code that the web server uses to describe this type of error.

These bad reactions can be due to a number of different causes. The server may be overloaded or there may be network problems between the two servers and the problem is only temporary. It is also possible that there is a misconfigured firewall or even a coding error and the issue will not be resolved until these issues are resolved.

Just like 404 errors, website designers can customize the look of a 502 error. So you may see different looking 502 pages on different websites. Sites may also use slightly different names for this error. For example, you may see things like:

HTTP Error 502 Bad Gateway

HTTP 502

502 Service temporarily overloaded

Temporary error (502)

502 Server Error: The server encountered a temporary error and could not complete your request

502 Bad Gateway nginx

In the vast majority of cases, this is just a bug on the server side of things that you can’t do anything about. Sometimes it’s a temporary bug; sometimes it isn’t. Still, there are some things you can try on your end of things.

Reload the page

Refreshing the page is always worth trying. Often the 502 error is temporary, and a simple update might do the trick. Most browsers allow you to refresh the page by pressing Ctrl+R on Windows or Cmd+R on Mac, and also provide a refresh button somewhere in the address bar.

It doesn’t fix the issue very often, but it only takes a second to try.

Check if the site is unavailable to other people

If you can’t reach a website (for whatever reason), you can also check if it’s just you having a connection problem or if other people are having the same problems. There are many tools for this, but our favorites are isitdownrightnow.com and downforeveryoneorjustme.com. Both work pretty much the same. Enter the URL you want to check and you will get a result like this.

If you get a report saying the website is down for everyone, there’s not much you can do except try again later. If the report shows the site is up, the problem may be yours. It’s very rare for this to happen with a 502 error, but it’s possible and you can try some of the things we describe in the next few sections.

Try a different browser

It’s possible that a problem with your browser is causing the 502 Bad Gateway error. An easy way to check this is to use a different browser and see if it works. You can use Google Chrome, Mozilla Firefox, Apple Safari or Microsoft Edge. If you can still see the error in the new browser, then you know it’s not a browser issue and you should try a different solution.

Clear your browser’s cache and cookies

If trying a different browser works, your main browser may have cached outdated or corrupted files that could be causing the 502 error. Removing these cached files and trying to open the website might solve the problem.

It’s definitely worth trying, and we have a handy guide for you on how to clear your history on any browser.

RELATED: How to Clear Your History in Any Browser

Check your plugins and extensions

If you are using extensions in your browser, it is possible that one or more of the extensions are causing the problem. Try disabling all your extensions and then accessing the website. If the error goes away after that, it’s likely that a plugin is causing the problem. Activate your plugins one by one to find the culprit.

RELATED: How to Uninstall Extensions in Chrome, Firefox, and Other Browsers

Reboot your devices

So you’ve used a website verification tool and discovered that the website isn’t available to you. And you have tested another browser and have the same problem. So you know the problem is probably yours, but it’s not your browser.

It’s possible that there are some strange, temporary problems with your computer or network equipment (wireless LAN, router, modem, etc.). A simple restart of your computer and network devices may help resolve the issue.

Change your DNS servers

Sometimes DNS problems can cause 502 errors. Changing your DNS servers is not a likely solution, but it is a possible one. And it’s not too difficult to do. Unless you’ve changed them yourself, your DNS servers are likely set by your ISP. You can change them to a third party DNS server like OpenDNS or Google DNS and that might solve the problem.

And there are other reasons why you might want to change DNS servers too – such as: B. higher speed and reliability.

RELATED: The Ultimate Guide to Changing Your DNS Server

The 504 gateway timeout error is one of the most common HTTP 5xx errors that website owners and website visitors face. For many WordPress blogs and ecommerce platforms, knowing how to fix server errors like this one is crucial to keep their hard-earned visitors from going to competitor websites.

Because the 504 Gateway Timeout error doesn’t tell you why it occurred, it’s difficult to pinpoint exactly what’s causing the server timeout. This article will help you understand it in detail, learn how to diagnose its cause and then fix it.

After trying all the different solutions mentioned in the post, your website should be up and running in no time.

Sounds interesting? Let’s dive in!

Prefer to watch the video version?

The 504 gateway timeout error is one of the most common HTTP 5xx errors that website owners and website visitors face. 🤔 Learn how to fix the problem quickly with this guide. ⬇️

Click to tweet

What is the 504 gateway timeout error?

Every time you visit a website in your browser, the browser sends a request to the web server hosting the website. The server processes the request and responds with the requested resources.

See how Kinsta compares to the competition. Choose Your Provider WP Engine SiteGround GoDaddy Bluehost Flywheel HostGator Cloudways AWS Digital Ocean DreamHost Compare Others

The server response includes one of many HTTP status codes to indicate the status of the response to the browser. But not all of these HTTP status codes are errors. For example, a status code of 200 OK means that the server successfully processed the request and “everything is fine”.

The 5xx class of HTTP status codes indicates that something is wrong with the server, the server is aware of it and cannot complete the client request. Therefore, they are also known as Server Error 5xx status codes.

Officially, five status codes are given under the 5xx class (500, 501, 502, 503, 504). You may also encounter many unofficial codes (506, 507, 509, 520, etc.).

The Internet Engineering Task Force (IETF) defines the 504 Gateway Timeout error as follows:

The 504 (Gateway Timeout) status code indicates that the server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access to complete the request.

To simplify further, this error occurs when two servers are involved in processing a request. The first server (usually the main server) expires and waits for a response from the second server (upstream server).

The 504 gateway timeout error manifests itself in various forms. Here are a few ways it usually appears:

The 504 Gateway Timeout error is similar to the 502 Bad Gateway error, which indicates that the first server received an invalid response from the second (upstream) server.

Variations of the 504 gateway timeout error

The browser shows every 504 gateway timeout error in it, just like any other error. Since there are different operating systems, web servers, browsers and user agents, it can appear in different ways.

Below are some common variants of 504 error messages you may encounter:

504 Gateway timeout

504 gateway timeout NGINX

NGINX 504 gateway timeout

Gateway timeout error

Error 504

HTTP error 504

HTTP Error 504 – Gateway Timeout

HTTP 504

504 error

Gateway timeout (504)

This page isn’t working – The domain took too long to respond

504 Gateway Timeout – The server did not respond in time

The page request was canceled because it took too long to execute

Website visitor: There was a problem processing your request. Please try again in a few minutes.

Site owner: Gateway timed out. Check your error log for more information.

A blank white screen

All of the above error responses, although worded differently, point to the same 504 gateway timeout server error.

Web servers and websites can customize how they present the 504 gateway timeout error to users. Some of them can be cool! It’s an excellent tactic to quell the disappointment of your visitors.

SEO impact of 504 gateway timeout error

All 5xx errors prevent a web page from loading, thereby adversely affecting the user experience. Therefore, search engines like Google take these errors seriously. If the error persists for a long period of time, it can even result in the website being removed from search engine results.

For example, when Google spiders come across a 503 Service Unavailable error, they will understand that it is a temporary issue as it is mainly used to enable website maintenance mode. Therefore, they try to crawl the page again later.

A 504 gateway timeout error is not necessarily temporary as it can have multiple reasons. If your site is down for just a few minutes and the spiders try to crawl it several times a minute, they try to serve the page from their cache. You wouldn’t even notice.

However, if your site is down for more than 6 hours or more, Google considers the 504 error to be a serious site-wide issue that you need to fix as soon as possible. This can negatively impact your SEO.

Google Search Console is one of the best SEO tools for monitoring your website’s HTTP 5xx errors.

Causes of 504 gateway timeout error

Since the 504 error is due to a timeout between servers, the problem is probably not with the client’s device or internet connection. This includes your device and connection.

A 504 gateway timeout error indicates that the web server is waiting too long for a response from another server and is “timed out”. This timeout can have many reasons: The other server is not working properly, is overloaded or is down.

The other server does not always have to be external (e.g. CDN, API gateway). It can also be a server-like entity within the main web server (e.g. reverse proxy server, database server).

How to fix 504 gateway timeout error

Without knowing exact details about the WordPress site such as: B. the server configuration, hosting plan, third-party plugins and the traffic it attracts, you may find it frustrating and overwhelming to troubleshoot a 504 gateway timeout error.

Because there are many variables involved, I recommend that you start by troubleshooting client-side issues, which are fairly rare, and then move on to troubleshooting server-side issues. They are usually the culprits with 504 errors.

Try reloading the webpage

One of the first things to try when encountering a 504 gateway timeout error is to wait a few minutes and try refreshing the page.

You can press the F5 key combination to refresh/reload the webpage in most browsers. To clear the page’s browser cache before reloading, you can press CTRL+F5 instead.

While you’re at it, you can also try loading the website in a different browser to rule this out as a problem. Since most 504 errors are due to temporarily overloaded servers, using this solution should get your website working again right away.

If waiting and reloading the website doesn’t fix the 504 error problem, you can check if a website is down for everyone or just you. Two useful online tools for testing a website for downtime are Down for Everyone or Just Me and Is It Down Right Now?

Restart your network devices

Sometimes problems with your network devices like modem or router can cause 504 gateway timeout error. Restarting these devices might help you fix the problem.

While you can turn off all of these network devices in any order, the order in which you turn them back on is important. Typically turn these devices on from the “outside in” by following the ISP’s connection order to your main client device.

Check your proxy settings

A proxy server sits between your device and the internet. It is mainly used to improve online privacy by hiding private information (e.g. device location) from websites and web servers (e.g. using a VPN).

Although it is rare for proxy servers to cause a 504 error, sometimes incorrect proxy server settings can be the culprit. You can disable the proxy server and try reloading the webpage to see if that fixes the error.

Most clients do not use a proxy service, so you can skip this step if you are sure you are not using a proxy server. However, you may have set it without even knowing it. I would suggest that you check your device and browser proxy settings to rule out this cause.

DNS problems

A 504 gateway timeout error can also be caused by DNS issues on the server side or the client side (or both).

The most likely reason for a server-side DNS problem is that the FQDN (fully qualified domain name) does not resolve to the correct IP address, or the DNS server is not responding. Usually this occurs when you have just migrated your WordPress site to a new server or host. Therefore, it is important to wait until the domain’s DNS records are fully propagated, which can take up to 24 hours.

You can use free tools like whatsmydns.net DNS Checker or DNSMap to see if your DNS has spread worldwide.

To troubleshoot client-side DNS issues, you can try flushing your local DNS cache. It’s like clearing your browser cache, except here you’re flushing the DNS cache from the operating system.

If you are using Windows, you can flush DNS cache by opening Command Prompt and typing the following statement:

ipconfig /flushdns

You should see the message “DNS resolver cache flushed successfully”. message if it worked.

For the latest macOS versions, you can open the terminal and run the following command:

sudo killall -HUP mDNSResponder

You won’t see a notification in macOS when the process is complete, but you can change this by appending the command with your custom message.

sudo killall -HUP mDNSResponder; DNS cache was cleared successfully

If you’re using older versions of macOS, the command you need to enter will vary depending on which version of macOS you’re running. For more details, see the macOS section in Kinsta’s in-depth flush DNS tutorial.

If you are using the Linux operating system, the process is quite similar to macOS as even Linux uses the terminal as a command line interface. Because there are many Linux distributions, the exact command you need to run may vary from one distribution to another. For more information, see Kinsta’s guide.

Finally, you can temporarily change your client-side DNS servers. By default, your ISP assigns you the DNS servers automatically. However, you can temporarily change these to public DNS IPs.

Some reliable DNS servers you can try are Google Public DNS, Cloudflare 1.1.1.1, Quad9 DNS, and Cisco OpenDNS.

Temporarily disable your website’s CDN

Sometimes the problem could also be with your Content Delivery Network (CDN). When a website’s origin server is unreachable, most CDNs attempt to serve the full webpage from their cache.

But most CDNs don’t enable this feature by default because of the complexity of caching dynamic assets on most websites (e.g. WordPress admin dashboard).

An easy way to fix this is to temporarily disable your CDN. For example, if you use the free CDN Enabler WordPress plugin to associate your website assets with the CDN URLs, you can disable the plugin and test your website reloading.

The same goes for using any other plugins you use to connect to your CDN (e.g. WP Rocket, Breeze, W3 Total Cache).

If you cannot access your website admin dashboard, you can disable the plugin via SFTP by renaming the plugin folder name.

CDNs like Cloudflare or Sucuri that provide full proxy services have additional firewalls between their edge servers and your origin server. As a result, HTTP 5xx errors are common when using it. Most of them cache 5xx errors returned from your origin server, making them easy to fix.

Cloudflare’s free plan tends to throw a 5xx error. Unfortunately, since it’s a full proxy service, there’s no quick way to disable it. But before you blame Cloudflare for this, you should know that Cloudflare shows two variants of the 504 Gateway Timeout error.

504 Gateway Timeout on Cloudflare (Variation 1)

Cloudflare will show you a custom 504 gateway timeout error screen if your site’s origin server responds with a standard HTTP 504 response.

Here the problem is with your web server and not with Cloudflare. You can try to fix the problem with the other solutions mentioned below or contact your hosting provider’s support for technical help.

504 Gateway Timeout at Cloudflare (Variant 2)

When Cloudflare causes the 504 Gateway Timeout error, the error screen will mention “cloudflare”, which is currently the default server name for all Cloudflare assets. Usually the error screen is shown as follows:

Because Cloudflare itself isn’t responding, you won’t see a Cloudflare-branded error screen here.

Most likely, Cloudflare is already aware of the issue and is already working on a fix. You can confirm this by checking the Cloudflare System Status webpage. Alternatively, you can contact Cloudflare Support for a faster resolution.

504 Gateway timed out on Cloudflare due to large uploads

The size of your uploads to your website can also be a reason for server timeouts. Cloudflare limits upload file size (per HTTP POST request) to just 100MB on both Free and Pro plans.

The problem may be on your host’s side or with Cloudflare. You can find out the exact cause by bypassing Cloudflare with your DNS hosts file and trying the upload again.

If you’re using Cloudflare with WordPress, I recommend using the free plugin and excluding critical URLs from caching (e.g. the WordPress admin dashboard). You can refer to Kinsta’s detailed post on configuring Cloudflare settings for WordPress.

Suggested reading: How to Set Up Cloudflare APO for WordPress.

Server issues (check with your host)

Server issues are one of the most common reasons for a 504 gateway timeout error. Since most WordPress sites are hosted on Nginx or Apache web servers, Nginx or Apache is waiting for a response from something and times out.

Many clients come to Kinsta because of this very issue they face with other WordPress hosts. The conversation goes something like this:

Sign up for the newsletter Want to know how we’ve increased our traffic by over 1000%? Join over 20,000 others receiving our weekly WordPress insider tips newsletter! subscribe now

We have around 100,000 visitors per month with more than 200,000 views. Currently we’re hosting with ____ and we’re constantly experiencing 504 errors due to server overload. I don’t like how ____ has handled the issue and we have also been told that we will have to move to their dedicated plans soon which I don’t think is necessary.

High-traffic and e-commerce sites are more prone to 504 errors due to server congestion as they generate many uncacheable requests. However, this problem can occur with any website, including simple blogs. Many hosts will ask you to upgrade to a high-tier plan to fix the problem, which in most cases is unnecessary.

Kinsta uses LXD managed hosts and orchestrated LXC software containers for each site. Thus, each WordPress site resides in its own isolated container with access to all the software needed to run it (Linux, Nginx, PHP, MySQL). The resources are 100% private and are not shared with other websites, not even your websites.

Most WordPress hosts that offer shared hosting plans do not have this feature. Therefore, a high-traffic website hosted on the same server as yours can cause your website to throw a 504 error as well.

Aside from isolating each site in its container, Kinsta also designed its infrastructure to easily handle thousands of simultaneous connections. Kinsta even hosts the MySQL databases on localhost, not a remote server. This means no latency between machines, resulting in faster queries and fewer chances of timeouts.

Many clients migrating to Kinsta see a huge decrease in overall load times.

An overloaded server is not the only cause of a server timeout. There can be many other reasons for the 504 error:

Slow server infrastructure

The server you are using to host your WordPress site may not have enough resources to handle the load. It’s like playing a modern, graphics-intensive video game on a decades-old PC.

The server simply hangs up trying to serve the website. The only solution to this problem is to upgrade to a server with better infrastructure. Because of this, even Kinsta’s most basic WordPress hosting plan will handle a medium-traffic static site.

Requires more PHP workers

PHP workers are used to run your WordPress site’s code. An e-commerce website with 50,000 visitors per month requires a lot more resources than a simple blog with the same amount of traffic. When all of the server’s PHP workers are busy, they build up a queue.

If the queue gets too big, the server ignores old requests, which can cause the server to throw a 504 gateway error. You can ask your host if you can increase the number of your PHP workers. This allows your website to run multiple requests at the same time.

firewall issues

Your server’s firewall might have some bugs or misconfiguration. Perhaps some of its rules are preventing the server from connecting properly. To determine if your firewall is the culprit, you can check your server’s error logs.

Network connection problems

Connection problems between the proxy server and the web server can cause delays in responding to HTTP requests. If you are using a load balancer, you may also experience network connectivity issues.

HTTP timeouts

HTTP timeouts can occur when a connection between the web server and the client is kept open for too long. For WordPress sites, this usually happens when running WordPress imports. One way to solve this problem is to switch to a faster internet connection.

You can also use a tool with WP-CLI support to run the scripts directly on the server and bypass the HTTP connection entirely. For example, you can use the WP-CLI wp import command to run the WordPress importer plugin directly from the command line interface.

Important: 504 Gateway Timeout errors look similar to 503 Service Unavailable errors or 502 Bad Gateway errors. But they are all different. If Kinsta encounters a 504 error, open a support ticket to get your issue fixed immediately.

To monitor your website downtime yourself, you can use a tool like updown.io. It regularly checks the status of your website (or any URL) by sending an HTTP request to it. You can set the check frequency from 15 seconds to 1 hour. If your website does not respond properly, you will be notified by email or SMS.

You get a generous amount of free credits with every updown.io account, but if you’re looking for cheaper alternatives, you can check out WebGazer or UptimeRobot. These two tools allow you to monitor your website’s uptime every 5 minutes for free. That’s decent enough for most website owners.

Monitoring your website will give you an idea of ​​how often it has gone down. This is especially helpful if you use a shared hosting provider. Most managed WordPress hosts will do this for you automatically. So it is always recommended to go with them.

For a detailed explanation, see Kinsta’s post on the importance of managed WordPress hosting.

Spam, bots or DDoS attacks

Malicious attackers can cripple your web server by sending too many and/or resource-intensive requests. If your website is spammed by bots or subjected to a DDoS attack, it can overload your server and cause 504 gateway timeout errors for many real users.

You can look at your server traffic and analytics to see if you can spot erratic patterns in site traffic. If you use Kinsta to host your site, you can easily view this data by going to your MyKinsta Analytics dashboard.

Start your investigation by looking at the top client IPs. It gives you an idea of ​​who is generating the maximum number of requests and from where. If your server suddenly consumes a huge amount of bandwidth or attracts a lot of traffic, this report will come in very handy.

Next you can look at the cache analysis report. Here you can see how many requests bypass or miss the cache or are served from the cache. For performance and stability reasons, you’ll want to cache as many requests as possible, but that’s not always possible.

For example, WooCommerce sites generate a lot of non-cacheable requests for features like the shopping cart and checkout.

Struggling with downtime and WordPress issues? Kinsta is the hosting solution built for performance and security! Check out our plans

Finally, you can use a WordPress security plugin to improve your site’s security by detecting and blocking worrisome traffic/IPs. You can also ask your host to block specific IPs.

Depending on the length and scale of the attack, this could be an endless process of IP blacklisting, as many attackers change their IPs and proxy addresses after being blocked.

Note: Kinsta does not allow its clients to install WordPress security plugins as they can have a major impact on the site’s performance, especially its scanning abilities. Since Kinsta uses load balancers with Google Cloud Platform, blocking IPs would not always work as intended.

You can use dedicated security solutions like Cloudflare or Sucuri to protect your websites from DDoS attacks and spambots. For more information, see Kinsta’s articles on installing Cloudflare on your WordPress site and how Sucuri helped stop a DDoS attack.

Corrupt WordPress database

Sometimes a 504 gateway timeout error can be due to a corrupted database, especially on WordPress sites. Typically this is due to corrupted database tables or files. Sometimes this can also be caused by a serious security issue, e.g. B. if your website or database is hacked.

Repairing a corrupt WordPress database depends on the problem. Plugins like WP-DBManager make it easy to diagnose and repair database problems. I recommend reading Kinsta’s detailed guide to repairing WordPress database issues to get started.

Check your website’s plugins and themes

In most cases, third-party plugins and themes do not cause 504 errors. But there is a small chance that they cause server timeouts, usually by queuing a lot of uncached requests generated by the plugin/theme. Since this ties up many of your server’s PHP workers, you may get 504 errors.

A good example of this problem is WooCommerce, a plugin that is installed to add ecommerce functionality to WordPress sites.

The easiest way to fix this problem is to disable all your plugins. Remember that you won’t lose any data by deactivating just one plugin.

If you can access your admin dashboard, you can go to the Plugins screen, select Disable from the Bulk Actions menu, highlight all plugins, and then click the Apply button. This will disable all your plugins.

If you are unable to access your admin panel, you can disable plugins via SFTP using the method previously outlined. Simply rename the main plugins folder name to disable all plugins in bulk.

After disabling all plugins, check if your website loads properly. If it works you need to activate each plugin and test the site after activating each plugin.

Finally, make sure your plugins, themes, and WordPress core are up to date. Also, make sure your server is running the recommended version of PHP.

If you feel this is too overwhelming, you can always contact your host for help. Kinsta uses Kinsta APM and other troubleshooting techniques to help customers narrow down which plugin, query, or script might be causing the error.

In the worst case, like an inefficient query or broken code in a plugin/theme, you can bring in a WordPress developer to fix the problem.

Check the error logs

Viewing error logs can be very helpful in fixing and debugging 504 errors on your WordPress site. This can help you quickly isolate an issue on your site, especially if it is due to a demanding plugin on your site.

If you’re a Kinsta client, you can easily see errors in the log viewer in your MyKinsta dashboard.

If your host doesn’t have a logging tool, you can enable WordPress debug mode by adding the following code to your wp-config.php file:

define( ‘WP_DEBUG’, true ); define( ‘WP_DEBUG_LOG’, true ); define( ‘WP_DEBUG_DISPLAY’, false );

The WP_DEBUG constant enables or disables the WordPress debug mode. It has two optional companion constants that can extend its capabilities. The constant WP_DEBUG_LOG instructs all errors to be saved in a debug.log file in the /wp-content/ directory. If you don’t see this file, you can always create one.

The constant WP_DEBUG_DISPLAY controls whether debug logs are displayed on the HTML page. Setting this to false will hide all errors, but you can check the errors later since you also defined WP_DEBUG_LOG as true.

Important: If you have WP_DEBUG enabled in the Kinsta environment, it will forward all errors to the debug.log file and not error.log in the MyKinsta dashboard.

You can also download the raw WordPress error log files via SFTP. You can usually find error logs in the root of your server in a folder called “logs”.

Kinsta users can also enable WordPress debug mode from their MyKinsta dashboard. To do this, navigate to Sites > Tools > WordPress Debugging and click the Enable button. This allows you to see PHP errors and notices without enabling debug mode via SSH or SFTP.

Finally, you can check the server log files. Depending on which server you use to host your WordPress site, they can often be found in these locations:

Apache: /var/log/apache2/error.log/

Nginx: /var/log/nginx/error.log/

For more information, see Apache or Nginx logging-related documentation.

Configure Apache or Nginx settings properly

You can edit your server configuration files to increase the resource limits for specific directives. This can help you to fix 504 gateway timeout error.

For Apache web server

First add the following code to your httpd.conf:

time out 600

This setting defines how long the server waits for certain requests before marking them as a network timeout problem. Der Standardwert beträgt 60 Sekunden (Apache 2.4-Version).

Sie können diese Anweisung nur in Ihre httpd.conf-Datei einfügen, nicht in Ihre .htaccess-Datei. Da die meisten Shared-Hosting-Anbieter es Ihnen nicht erlauben, die httpd.conf-Datei zu ändern, können Sie stattdessen versuchen, den Wert der LimitRequestBody-Direktive in Ihrer .htaccess-Datei zu erhöhen.

Fügen Sie dann die folgende Zeile zu Ihrer php.ini-Datei hinzu:

max_execution_time 300

Der Standardwert der PHP-Direktive max_execution_time beträgt 30 Sekunden. Wenn Sie ihn erhöhen, können die PHP-Skripte Ihrer Website länger ausgeführt werden.

Für Nginx-Webserver

Wenn Sie Ihre WordPress-Sites auf Nginx + FastCGI Process Manager (PHP-FPM) ausführen oder Nginx als Reverse-Proxy für Apache verwenden, können Sie die Servereinstellungen optimieren, um 504 Gateway Timeout-Fehler zu vermeiden.

504 Gateway-Timeout-Fehler auf Nginx + FastCGI (PHP-FPM)

Zuerst müssen Sie Ihre PHP-FPM-Pool-Konfigurationsdatei bearbeiten. Sie finden es am Speicherort /etc/php7.4/fpm/pool.d/www.conf auf Ihrem Nginx-Server (der genaue Pfad kann je nach PHP-Version variieren). Alternativ können Sie den folgenden Befehl in Ihrem Terminal ausführen, um die Konfigurationsdatei des PHP-FPM-Pools zu bearbeiten:

sudo nano /etc/php/7.2/fpm/pool.d/www.conf

Legen Sie als Nächstes die folgende Direktive fest:

request_terminate_timeout = 300

Danach müssen Sie Ihre php.ini-Datei bearbeiten. Sie finden es unter /etc/php.ini . Öffnen Sie die Datei und fügen Sie den Wert für die Direktive max_execution_time hinzu bzw. ändern Sie ihn auf 300 Sekunden.

max_execution_time = 300

Fügen Sie abschließend den folgenden Code zum Speicherort Ihrer nginx.conf-Datei hinzu:

Standort ~ .php$ { … fastcgi_read_timeout 300; }

Laden Sie Nginx und PHP-FPM neu, damit die Änderungen wirksam werden.

sudo-Dienst nginx neu laden sudo-Dienst php7.4-fpm neu laden

Der genaue Code zum Neuladen von PHP-FPM hängt von der auf Ihrem Server installierten PHP-Version ab. Testen Sie Ihre Website, um festzustellen, ob das Problem behoben wurde.

504 Gateway-Timeout-Fehler auf Nginx-Proxy

Wenn Sie Nginx als Reverse-Proxy-Server für Apache verwenden, können Sie es nachsichtiger gegenüber Server-Timeouts machen, indem Sie Ihrer nginx.conf-Datei die folgenden Anweisungen hinzufügen:

Proxy_connect_timeout 600; proxy_send_timeout 600; Proxy_read_timeout 600; send_timeout 600;

Vergessen Sie nicht, Nginx neu zu laden, nachdem Sie Ihre Änderungen vorgenommen haben.

sudo-Dienst nginx neu laden

Andere HTTP-Fehler wie 504 Gateway Timeout

Wie bereits in diesem Artikel erwähnt, ähneln viele andere HTTP 5xx-Fehler dem 504 Gateway Timeout-Fehler. Das liegt daran, dass sie alle auf der Serverseite passieren. Zu diesen Fehlern gehören:

Andere HTTP-Fehler, die durch clientseitige Probleme verursacht werden, wie der 404 Not Found-Fehler, sind ebenfalls wie der 504-Fehler. Weitere Informationen findest du in der detaillierten Anleitung von Kinsta und der Liste der HTTP-Statuscodes.

Wenn Sie nicht wissen, was einen 504-Gateway-Timeout-Fehler verursacht hat, wie können Sie ihn rechtzeitig beheben, um hart verdiente Besucher davon abzuhalten, zu den Websites von Mitbewerbern zu wechseln? 🤷‍♂️ Alle Details sind in diesem Beitrag. ⬆️

Zum Twittern klicken

summary

Ihre WordPress-Site kann aus mehreren Gründen vom Fehler 504 Gateway Timeout betroffen sein. In diesem Artikel haben Sie gelernt, wie Sie sie alle beheben können. In der Regel werden diese Fehler durch serverseitige Probleme verursacht. In diesem Fall können Sie sich an Ihren Host wenden und das Problem schnell beheben lassen.

Sie müssen jedoch auch verstehen, dass dieser Fehler auf Plugins, Designs, Dienste von Drittanbietern, ineffiziente Datenbankabfragen oder eine Kombination aus zwei oder mehr davon zurückzuführen sein kann. Wenn Sie die Ressourcen Ihres Servers (z. B. PHP-Worker) ausschöpfen, wird empfohlen, Ihre Website auf Leistung zu optimieren.

Wenn Sie immer noch feststellen, dass Ihre Website eine Zeitüberschreitung aufweist, müssen Sie möglicherweise Ihren Hosting-Plan oder die Anzahl der PHP-Worker aktualisieren. Ich empfehle Ihnen, diese Option erst in Betracht zu ziehen, nachdem Sie alle anderen in diesem Artikel beschriebenen Lösungen ausgeschöpft haben.

Von einfachen statischen Websites bis hin zu komplexen E-Commerce- und Mitgliederseiten sind die skalierbaren Hosting-Pläne von Kinsta so konzipiert, dass sie alle Arten von Websites aufnehmen können. Um mehr über unser skalierbares Cloud-Hosting zu erfahren, lesen Sie diesen Artikel!

Haben wir etwas verpasst? Wenn Sie immer noch Schwierigkeiten haben, den Fehler 504 Gateway Timeout auf Ihrer WordPress-Seite zu beheben, hinterlassen Sie unten einen Kommentar.

A 504 gateway timeout error is an error that occurs when a website server times out while attempting to contact another server.

There are many possible causes, and they generally lie on the website side of the connection.

There are several ways you can try to fix 504 gateway errors on your own website or on other websites.

Check out Insider’s tech reference library for more stories.

The Internet, by its very nature, is an interconnected network of computers, and that means that sometimes there can be connectivity issues when parts of the network are misbehaving. For example, it’s not uncommon to encounter a 504 gateway timeout error that prevents you from accessing a website’s content.

What is a 504 gateway timeout error?

A 504 gateway timeout error means the server you’re trying to reach didn’t get a timely response from another server it relies on to display the website. In most cases, this generally means that one of the servers is misbehaving or is misconfigured in such a way that the website server “times out” waiting for a response from the other computer and therefore displays an error instead of the requested website.

There is no standard way to display a 504 error, but it usually contains the 504 code. Dave Johnson

This is a fairly generic error message, and that means it can appear on any platform – you can see a 504 error on any web browser, on any computer, and it appears on mobile devices and in programs that rely on an internet connection. It also means that the exact appearance of the error can vary, but usually includes the 504 code to indicate the nature of the problem.

504 gateway timeout caused

When you see a 504 gateway timeout error, the general problem is pretty easy to understand, but this simple explanation doesn’t explain why the timeout error occurs. There are many possible causes – here are the most common:

There is a network connection error. Many network connections are required to successfully display a website in your browser, including modems, routers, network switches, cabling, and more. When there is a problem between two devices, it can result in a 504 error.

Many network connections are required to successfully display a website in your browser, including modems, routers, network switches, cabling, and more. When there is a problem between two devices, it can result in a 504 error. There is a server connectivity problem. Most websites are hosted on servers managed by third parties and if the server is offline due to a hardware problem or maintenance, a 504 error may be generated.

. Most websites are hosted on servers managed by third parties and if the server is offline due to a hardware problem or maintenance, a 504 error may be generated. There was a recent change in IP address or DNS server. If the website’s server has recently changed IP address, it may take some time for the DNS server address to be updated. Because browsers find websites using a DNS server lookup, this can cause a 504 error until the update is complete.

. If the website’s server has recently changed IP address, it may take some time for the DNS server address to be updated. Because browsers find websites using a DNS server lookup, this can cause a 504 error until the update is complete. The server’s firewall or other settings are configured incorrectly. There can be a number of basic configuration errors, particularly in the server’s firewall, which are designed to prevent malware and hacker intrusions.

There can be a number of basic configuration errors, particularly in the server’s firewall, which are designed to prevent malware and hacker intrusions. There may be a problem with the user’s computer or network. Most of the time, 504 errors are a problem at the end of the website server connection. However, in rare cases, the user’s computer or network connection may not behave properly. If this is the problem then generally every website you try to reach will experience a connection error, not just one.

How to get rid of a 504 gateway timeout error on a website you visit

If you can’t reach a website because of a 504 gateway timeout error, try reaching other websites. If you’re only having trouble on one website, the problem is almost certainly with the server and out of your control. If you can reach the site administrator, you can let them know about the problem, but otherwise you just have to wait for it to be fixed.

If you’re seeing a 504 error on multiple websites, the problem is more likely to be at your end of the connection. There are a few things you can try to resolve the issue:

Close and reopen the web browser or restart your computer. Then try to reach the problematic websites again.

. Then try to reach the problematic websites again. Reboot your network modem and wireless router. Turn off both devices, wait at least two minutes, and then turn them on again. Start with the network modem and then after it is fully connected, turn on the WiFi router and wait for it to establish a solid connection.

. Turn off both devices, wait at least two minutes, and then turn them on again. Start with the network modem and then after it is fully connected, turn on the WiFi router and wait for it to establish a solid connection. Change your DNS server. This is usually configured by your ISP, but it is possible to manually select a different DNS server.

. This is usually configured by your ISP, but it is possible to manually select a different DNS server. Turn off your proxy server (or check its settings). In the vast majority of cases, your computer should not be using a proxy server to connect to the Internet. However, if your computer is misconfigured or malware has configured your computer to connect through a proxy server, you can try turning it off. On Windows, click Start and then click Settings. In the settings window, search for “proxy” and click Change proxy settings. Here you can switch off the proxy server or refine the settings.

A 504 error can sometimes be caused by a misconfigured proxy server. DavidJohnson

How to fix 504 gateway timeout errors on your own website

If you own or manage a website that is suffering from a 504 error of its own, there are a handful of troubleshooting steps you can take to resolve the issue.

Update your DNS server. If you recently changed your website’s IP address, you may need to update your DNS server. DNS changes can take several hours to process, and you may generate 504 errors in the meantime.

If you recently changed your website’s IP address, you may need to update your DNS server. DNS changes can take several hours to process, and you may generate 504 errors in the meantime. Correct your firewall settings. You may have a bad firewall configuration that is preventing your server from communicating properly. To test this, you can temporarily disable the firewall entirely to see if that fixes the issue.

You may have a bad firewall configuration that is preventing your server from communicating properly. To test this, you can temporarily disable the firewall entirely to see if that fixes the issue. Check for other connection issues. This can be caused by problems with your server, router, network switch, or system maintenance.

This can be caused by problems with your server, router, network switch, or system maintenance. Check for other configuration issues. For example, WordPress-based websites are prone to corrupt databases. You may need to run the database repair tool from the WordPress admin dashboard.

Answers:

A:

Hello Jack,

There are numerous strategies available on the internet to diagnose the 502 bad gateway problem. Probably the most effortless techniques are described here:

Refresh your website – This is one of the basic strategies that works for most of the bugs in your browsers. Here and there your browser will not respond as it gains weight at the same time from the huge retrieval of information. Therefore, it may not respond and will display a gateway error. To fix this problem, all you have to do is restart your browser or refresh your website page by essentially tapping the refresh button. Or on the other hand, to restart your browser, just close the current browser and start it again after some time. To activate the site page, you can also press the F5 key or the Ctrl+R key.

Restart your internet device – In some cases, this error also occurs due to an issue with your internet modem and should be checked and configured accordingly. You should just restart it, just turn off your webmodem’s power source and hold on for some time unless the LED lights on the modem turn off properly. After about 10 to 15 seconds stuck, turn on the power supply again and check if it works or not.

Delete cache and cookies – It is also possible that your browser has degenerate or outdated data stored. Which is responsible for detecting the gateway error. To clear your browser’s treats and cache, you can go to your browser settings and from that point decide to clear the treats and cache.

Check your system firewalls – Firewalls are additionally responsible for blocking correspondence between two servers, which leads to gateway failure. You can check the likelihood of the problem appearing or not by disabling it for a moment.

Disable CDN shortly – CDN or Content Delivery Network is used to increase the loading speed of a page. In addition, it is responsible for activating error 502 every now and then because CDN works with additional firewalls, which prevents communication between two servers. Then you need to randomly disable your CDN and check if it is reliable or not. If none of the methods work for you. The complete opposite of what you can do is to contact your hosting service provider and ask them to solve this problem. Many supportive administrations offer free specialized help 24 hours a day.

Thanks very much!

introduction

The 502 Bad Gateway error is common among website users. There are different possible reasons for this error and different ways to fix it. In this article, we will cover the top possible causes and how users and web developers can solve them.

Use MetricFire’s platform to analyze and troubleshoot your system’s performance. For more detailed information about MetricFire and how to integrate it into your system, book a demo with our team or sign up with MetricFire for the free trial.

What does NGINX 502 Bad Gateway mean?

502 Bad Gateway means the server you are accessing is getting an error from another server. This happens when a server acts as a proxy to get information from another server. Connecting to another server returns an error. NGINX returns error 502 if it cannot connect to PHP-FPM or PHP-FPM is not responding.

There are different names for the 502 error that you may see on different websites. For example:

HTTP Error 502 – Bad Gateway.

HTTP 502.

502 Service temporarily overloaded.

Temporary error (502).

502 Bad Gateway nginx.

502 Bad Gateway.

Error 502.

502 proxy error.

Also, the appearance of the page showing the 502 error can be customized on different websites in the same way as it is for the 404 not found error. There are various causes of error 502. Below we will look at the main as well as possible ways to fix this error.

What is PHP-FPM used for?

PHP-FPM (PHP-FastCGI Process Manager) is a web request processing tool for PHP applications. PHP-FPM together with NGINX can significantly increase the performance of websites while reducing resource consumption.

PHP works as an isolated service when using PHP-FPM. Web requests are processed over a TCP/IP socket, NGINX only processes HTTP requests, and PHP-FPM interprets PHP code. Using separate services is very important to improve efficiency.

Possible reasons for 502 Bad Gateway

Let’s take a look at some of the possible reasons behind the 502 bad gateway.

NGINX is not running

If you see the 502 error, the first thing you need to do is verify that NGINX is running. To do this, run the following command:

systemctl-status nginx

If you see in the response that the status is inactive (dead), you need to start NGINX.

PHP-FPM is not running

The next reason for the 502 error is that PHP-FPM is not running. If you are using Linux, you can check if PHP-FPM is running with the following command:

ps aux | grep php-fpm

If you don’t see any PHP-FPM processes as a result of this command, you need to run PHP-FPM to fix error 502.

PHP-FPM timeout expires

If the server takes too long to respond, a 502 error can be caused by a PHP-FPM timeout. In this case, PHP-FPM will close the connection even before the response is sent and NGINX will return a 502 error. To fix this problem you can increase the PHP-FPM timeout or alternatively examine your application and find out why it is not responding for too long.

Firewall blocks requests

A firewall can block communication between the edge servers and the origin server. Some DDoS protection systems or security plugins of your CMS can also block requests from servers.

A domain name is not allowed

The domain name does not resolve to the specified IP address or to all IP addresses. In this case, you need to change the DNS server and wait for the changes to propagate and become active globally.

Server is not available

The original server is down or there is no connection to this server.

How to solve the 502 error?

Most of the time, the 502 error occurs due to problems on the side of the website. However, there are times when the root cause lies in the user’s device. You can check if only you are having connection problems or other people are also unable to connect to this website. To do this, use any of the tools that check the status of the site and whether it is working or not. For example, use one of the following or similar tools: isitdownrightnow.com, downforeveryoneorjustme.com. To learn more about the cause of Error 502, you can examine the NGINX log file on your computer (/var/log/nginx/error.log).

As a visitor

If you are the only one having connection problems, there are several things you can do to fix the 502 error as a website visitor.

Reload the page in the browser. Often the 502 error is temporary and a simple reboot can help. Clear browser cache and cookies. The browser can store old or corrupted files and data that can cause the 502 error. Try a different browser. There may be a problem in the browser you are using and the error does not appear in another browser. Restart your computer and network devices. Maybe this is the problem and after a reboot the error goes away. Check plugins and extensions in your browser. If you use plugins or extensions and the website works in another browser, they may be blocking the connection. Disable all installed plugins and extensions and check the connection again. Change your DNS server. Changing the DNS server can fix the 502 error. You can choose between Open DNS or Google DNS servers.

As a developer

In most cases, the 502 error occurs to all users because the problem lies within the website. As a web developer, you can:

Check if your server is available. Check the firewall logs for unusual crashes. When using Cloudflare, your visitors will return a 502 Bad Gateway error when a certain limit is reached. Try disabling Cloudflare.

Monitor your system metrics with MetricFire’s Hosted Graphite

To identify bottlenecks and fix errors like error 502, it is helpful to monitor the metrics of your system and the technologies you are using in your application. MetricFire has an open source platform that gives you the tools to monitor and analyze your system’s metrics. MetricFire offers hosted Graphite and hosted Grafana. Grafana is a web-based analytics and data visualization application. You can use it to create various customizable dashboards that can include charts, graphs, and notifications.

Let’s take a look at some of Grafana’s main features:

Dashboard Templates. You can style your dashboard in templates as if you were writing code. Templates allow you to use the same design in different environments. Remarks. You can create logs and comments on your chart manually or automatically. Custom Plugins. Grafana can install external plug-ins that you can use to extend the basic functionality. SQL support. With SQL support, you can easily retrieve data from a variety of data sources. warnings. Grafana can send users notifications about important incidents.

Graphite is a tool for collecting, storing and processing metrics. You can use Graphite as a data source for Grafana. Grafana comes with an advanced Graphite query editor that allows you to write various queries, add functions, change function parameters, accept complex nested queries using query links, and more.

With Hosted Graphite and Grafana, you can track your system performance in real time. MetricFire offers you hosting services for both tools so you can focus on your system’s performance and monitor its metrics from your browser.

To learn more about how to integrate Graphite and Grafana into your system, book a demo with our team or sign up for the MetricFire free trial today.

Conclusion

In this article, we took a look at what error 502 means, what are the possible reasons for its occurrence and how to fix it. We also found that to troubleshoot your system, it’s important to use monitoring tools like hosted Graphite and Grafana offered by MetricFire.

Book a demo with MetricFire experts or sign up for the free trial today and learn more about our features.

If your Gmail account is not receiving emails, it could be due to various issues.

Every email you receive takes up storage space, and if your Google account runs out of storage space, you won’t be able to receive new emails.

You may also have the wrong Gmail inbox settings or unstable internet connection.

Check out Insider’s tech reference library for more stories.

Gmail is by far the most popular email service in the world. Most popular apps and websites allow you to create websites using just your Gmail account, and if your work involves email at all, Gmail is probably the center of your online life.

Because of this, it can be very frustrating when you find that you are no longer receiving emails. There are a variety of issues that can prevent you from receiving emails, but fortunately they can all be fixed.

Here’s what to do if you find you’re no longer receiving email.

How to Fix Gmail If You’re Not Getting Emails

Clear your Google storage

Many of us are guilty of hoarding messages and files that we don’t need. If your inbox is full of old emails, you run the risk of running out of disk space.

Search your inbox to delete large files from your account or Google Drive to free up space. If you need more space to store your emails, you can also upgrade your storage plan.

If your Google storage space is full, you will no longer be able to receive emails. Google; William Antonelli/Insider

Make sure your emails are not moved to another folder

Gmail has an automatic system for filtering emails into your different folders. So if you’re waiting for an email from a new sender, chances are Gmail has marked it as spam.

You can open your spam folder by clicking or tapping Spam in Gmail’s left sidebar. When you find the email you’re looking for there, open it and select Don’t report spam or Move to inbox.

You can move spam messages back to the general inbox. gmail; William Antonelli/Insider

Alternatively, look at the All Mail folder, which contains all the emails you receive, regardless of the folder.

You might also want to check your Trash folder. There is always a chance that you accidentally deleted the email you were looking for.

If you find that a lot of important emails are being filtered to other folders, make sure you don’t accidentally have a filter blocking your emails.

1. On the Gmail desktop website, click the gear icon in the upper-right corner, and then click View All Settings.

2. Select the Filters and Blocked Addresses tab to view all your Gmail filters.

3. Review the filters and select Delete for any you want to remove.

Connect to the Internet

It may seem obvious, but you need an internet connection to receive emails. If your internet connection is intermittent or weak, Gmail will have trouble receiving and loading email.

Run a speed test on your computer or phone to see if your connection is slow. And if the problems persist, disconnect from the internet and reconnect. You may also need to manually reset your internet router or even try using a different device to check your email.

Make sure your accounts are set up correctly when using the iPhone Mail app

When using Gmail on your iPhone, you may face some issues. If you’re using the Mail app on an iPhone, you need to make sure your Google account is set up and linked properly.

1. Open Settings and scroll down to Mail.

2. Tap Accounts and then tap Add account.

3. Choose the email provider you are using and log in to the given account.

4. After signing in, your Gmail account should be linked to your iPhone’s Mail app.

Gmail on an iPhone can also have IMAP issues, which is the system that allows information to flow in and out of your smartphone. If it’s off, there are simple steps to enable it.

In a computer’s web browser

1. Open Gmail and click the gear icon in the top right corner, then click View All Settings.

2. Select the Forwarding and POP/IMAP tab.

3. Scroll down to IMAP access and click Enable IMAP.

Enable IMAP, either on your computer or phone. gmail; William Antonelli/Insider

On your iPhone

1. Open Safari, go to Gmail.com and log in to your account.

2. Tap Go to Mobile Gmail Site and tap the link at the bottom of the screen.

3. Tap More in the bottom left.

4. Scroll down and tap View Gmail and tap Desktop.

5. Tap Settings and then tap the Forwarding and POP/IMAP tab.

6. Scroll down to IMAP access and tap Enable IMAP.

JavaScript is required. Please enable javascript in your browser.

Please wait while we check the server…

We tried to ping the Gmail website through our server and the website returned the above results. If mail.google.com is down for us too, there’s nothing you can do but wait. The server is probably overloaded, down or unreachable due to a network problem, an outage or website maintenance…

The chart above shows the service health activity for mail.google.com over the last 10 automatic checks. The blue bar indicates the response time, which is better when it is smaller. If there is no bar for a certain time, it means that the service was down and the website was offline.

Cannot Access Gmail – Troubleshooting Guide Cannot Access Gmail – Troubleshooting Guide

If the website is UP but you can’t access the page, try one of the following solutions:

Browser related issues

Force a full refresh of the site. This can be achieved by pressing the CTRL + F5 keys simultaneously in your favorite browser (Firefox, Chrome, Explorer, etc.).

Try alternative URLs like gmail.com, gmail.google.com

Clear the temporary cache and cookies on your browser to ensure you have the latest version of the website. For instructions select your browser:

Fix DNS problems

A Domain Name System (DNS) allows a website IP address (192.168.x.x) to be identified with words (*.com) to make it easier to remember, like a phone book for websites. This service is usually provided by your ISP.

Clear your local DNS cache to ensure you’re using the latest cache from your ISP. For Windows – (Start > Command Prompt > type ipconfig /flushdns and press Enter). For details select your operating system:

If you can access a website at the office or over a 3G network but it doesn’t work on your computer, it’s a good idea to use a DNS service other than your ISP. OpenDNS or Google Public DNS are excellent and free public DNS services.