How Do I Fix Error 502 On Google? Quick Answer

Credit: Hero Images/Hero Images/GettyImages

Error 502 usually indicates a remote problem that has nothing to do with your computer or your internet connection. This is good news as you have nothing to fix, but bad news as the error persists until the people controlling the faulty server figure out they have a problem and fix it. However, depending on the source of the 502 proxy error, you may be able to take steps to fix or bypass it.

advertisement

Internet Status Codes

The “HTTP” at the beginning of each URL stands for “Hypertext Transfer Protocol”. HTTP provides your web browser with an orderly way to communicate with web servers – the machine chatter that goes on behind the scenes of your internet experience. As part of HTTP, the server responds whenever your browser interacts with a server, e.g. B. when you try to load a web page with an Internet status code that tells the browser how the interaction went. The most common is Code 200, a generic message that means everything went well. These codes are always there, but your browser doesn’t usually show them to you unless something goes wrong. Code 404 is the most well-known HTTP error code and indicates that the server could not find what your browser was looking for, but proxy error 502 also pops up from time to time.

advertisement

video of the day

Code 502: Faulty gateway

The HTTP error code 502 indicates a “bad gateway” or “bad proxy”. When you visit a website, your browser does not necessarily communicate directly with the server hosting the website. There are often intermediary web servers, known as “gateways,” that route web traffic between networks. If something goes wrong between the gateway server and another upstream server – which can be either the target server or another gateway server – the status code that comes back to you is the proxy error 502. It’s not a very informative one Message just telling you that the gateway server received an invalid response. The real problem could be with the upstream server or with the gateway server itself.

advertisement

Main sources of 502 errors

If you’re only getting a 502 error for a specific website, it usually indicates a problem with the website’s server. On the other hand, if you are getting 502 errors for all websites, it probably means that your local ISP is having a technical problem. Call them to report the outage; and if you’re using a proxy server for privacy reasons or to circumvent access restrictions, a 502 proxy error could indicate that the proxy server has poor or difficult programming — which isn’t uncommon. In this case, you can try not using the proxy or use a different proxy.

advertisement

Steps you can take

If you encounter a 502 error, hold down the “Ctrl” key on your keyboard and press “F5”. This will clear the cache for that page and download a brand new copy. You can also try loading the website in a different browser to make sure it’s not a problem with your browser itself. If these steps don’t work, try restarting your router, modem, and finally your computer. Restarting these devices can fix a variety of errors that lead to code 502. If you’re tech-savvy, you can temporarily change your DNS server to a free public one. If the problem was with your DNS server, this will bypass the error. Finally, you can try to contact the website with error 502 to report the problem.

The 502 Bad Gateway error is an HTTP status code that means a server on the internet received an invalid response from another server.

502 Bad Gateway errors are completely independent of your particular setup, which means you can see one in any browser, on any operating system, and on any device.

The 502 Bad Gateway error appears in the internet browser window just like web pages.

Microsoft no longer supports Internet Explorer and recommends upgrading to the newer Edge browser. Go to their website to download the latest version.

What does a 502 Bad Gateway error look like?

The 502 Bad Gateway can be customized from any website. Although it’s quite uncommon, different web servers describe this error differently.

Theresa Chiechi / Lifewire

Below are some common ways you can see it:

502 Bad Gateway

502 Service temporarily overloaded

Error 502

Temporary error (502)

502 proxy error

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

HTTP 502

502. This is a mistake

Bad Gateway: The proxy server received an invalid response from an upstream server

HTTP Error 502 – Bad Gateway

Twitter’s famous “fail wheel” error, stating that Twitter is overloaded, is actually a 502 bad gateway error (although a 503 error would make more sense).

A bad gateway error received in Windows Update generates a 0x80244021 error code or the message WU_E_PT_HTTP_STATUS_BAD_GATEWAY.

When Google services like Google Search or Gmail experience a 502 Bad Gateway, the screen often displays a server error or sometimes just 502.

What Causes a 502 Bad Gateway Error?

Bad gateway errors are often caused by problems between online servers over which you have no control. However, sometimes there is no real problem, but your browser thinks there is, thanks to a problem with your browser, a problem with your home networking equipment, or some other reason that you can control.

Microsoft IIS web servers often provide more information about the cause of a specific 502 Bad Gateway error by adding an extra digit after 502, as in HTTP Error 502.3 – The web server received an invalid response while acting as a gateway or proxy , which means Bad Gateway: Forwarder Connection Error (ARR).

An HTTP Error 502.1 – Bad Gateway Error is related to a CGI application timeout issue and should be fixed as a 504 Gateway Timeout issue.

How to Fix a 502 Bad Gateway Error

The 502 Bad Gateway error is often a network error between servers on the Internet, which means the problem isn’t with your computer or your Internet connection.

However, since it’s possible that something is wrong with you, here are some fixes to try:

You try to load a website and this message flashes on your screen: 502 Bad Gateway.

What does that mean?

A 502 Bad Gateway message indicates that one server received an invalid response from another. Essentially, you’ve connected to some sort of intermediate device (like an edge server) that should fetch all the bits you need to load the page. Something went wrong during this process and the message indicates the problem.

Let’s dig deeper into what 502 Bad Gateway means, and we offer five solutions that you can try to fix the problem.

What does “502 bad gateway” mean?

The Hypertext Transfer Protocol (HTTP), a set of rules governing the Internet published by the Internet Engineering Task Force (IETF), governs every Internet transaction. In the HTTP system, problems have numbers.

The 502 status code according to the IETF indicates a few things:

Proxies: If you’re getting a bad gateway tip, you’re working with a gateway or proxy server.

Connection: The proxy tried to work with the origin server.

Error: The proxy received an invalid response from the server.

The language of numbers may seem confusing, but it’s actually quite efficient. A simple number says a lot about why the page isn’t loading.

502 bad gateway prevention and solutions

No one wants to deal with error codes while surfing the web. And as a developer, such errors can shift your traffic and hurt your reach. Fixing the problem quickly should be your top priority.

502 gateway errors often stem from:

domain names . Computers perform a quick lookup to resolve a numeric IP into a standard format. If this system goes wrong (as would happen if you switched to a new hosting service), you’ll see a failed gateway warning.

Traffic. Too many visitors can overload a server and make it impossible to process requests.

connectivity. Firewall setup issues can block proxy communications.

As a developer, you can solve these problems in the following ways:

Judgement. Are you dealing with a DNS problem? Or are you overwhelmed by traffic? You know which provider to call next.

Testing. Use a ping or traceroute to determine if your server is reachable at all.

Compensation. You could reduce firewalls and otherwise ensure all traffic reaches you. However, this comes with major security risks. Know what you’re getting yourself into.

As a visitor you can:

Reload. Simple traffic problems can go away if you wait a moment and try the site again.

Clear. Your browser cache can affect smooth surfing. Clear the data and try again.

Error 502 is just one type of HTTP error that your website might generate. Check out our blog to learn about another common problem, Error 431.

references

Hypertext Transfer Protocol (HTTP/1.1): semantics and content. (June 2014). Internet Technology Working Group.

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 you’ve ever visited a website that gave you an error page, you know how frustrating it is.

One of the worst things you can do as a brand is not to meet the needs and expectations of your audience. If your website visitors see an error page when looking for help or information, they could become frustrated and lose trust in your brand, permanently damaging your reputation.

The 504 Gateway Timeout Error is a type of error that can affect user experience in this way. To help you not lose brand sentiment and consumer confidence, we have explained exactly what this error means and what are its most common causes and solutions.

What is a 504 gateway timeout error? A 504 gateway timeout error means your web server didn’t get a timely response from another upstream server when it tried to load one of your web pages. Simply put, your web servers aren’t communicating with each other fast enough. Since a 504 gateway timeout error is rather generic, it doesn’t indicate the exact cause of the problem. In this case, your website will show your website visitors an error webpage.

This is how a 504 gateway timeout error can appear in your user’s browser:

image source

504 error wording

The screenshot above shows how a 504 gateway timeout error is displayed on a server. Below are some other common ways a 504 error can appear, depending on the server, operating system, or browser you’re using.

A 504 error is displayed as HTTP ERROR 504 in Google Chrome. This code appears below a message that reads something like “This website cannot be reached. _____ took too long to reply.”

image source

In Windows-based programs, a 504 error is displayed as ERROR 504, HTTP_STATUS_GATEWAY_TIMEOUT, or “Request timed out waiting for a gateway message.” This is what it can look like when using Excel:

image source

During a Windows update, a gateway timeout error generates error code 0x80244023. The message is: WU_E_PT_HTTP_STATUS_GATEWAY_TIMEOUT.

image source

In other operating systems, web servers, or browsers, a 504 error may also result in the following message – although this is less common: “The proxy server did not receive a timely response from the upstream server.” Here’s a slight variation:

image source

So now we know how the 504 error is worded, but what exactly does it mean? Let’s decode it below.

What does 504 gateway timeout mean?

When you visit a website, your server sends a request to another server hosting that website. This server – known as the “upstream server” – receives the request and responds with all the resources needed to load the website in your browser.

However, a 504 gateway timeout error means your server didn’t get a response from the upstream server fast enough. Because its request has timed out, your server cannot load the webpage and ultimately fulfill its role as a gateway – hence the name “Gateway Timeout” error.

You may be wondering what exactly is causing the delay in the upstream server’s response – and that’s a good question. Let’s get into that below.

504 gateway timeout causes

504 gateway timeout errors are among the most frustrating HTTP status codes you can get. They indicate what happened to your website, but they don’t tell you why it happened, making it difficult for you to pinpoint the cause and ultimately fix the problem.

Below are a few options.

Server connectivity issues

Most websites are on multiple servers or third-party hosting providers. If your server is down for maintenance or other reasons, your website might show visitors a 504 gateway timeout error page.

DNS changes

If you recently changed servers or moved your website to a different IP address, changes will be made to your website’s DNS server. This could result in your website serving a 504 Gateway Timeout Error page to its visitors. Your website will not be operational until these DNS changes take full effect, which may take a few hours.

Incorrect firewall configurations

Your firewall is your website’s gatekeeper, protecting your website from malicious visitors or distributed denial-of-service (DDoS) attacks. Sometimes, a bad firewall configuration causes your firewall to consider requests from a content delivery network as an attack on your server and reject them, resulting in a 504 Gateway Timeout Error.

Error in your website code

If your website’s code contains an error, your server may not be able to correctly answer requests from a content delivery network.

Network connection error

Since a 504 error is the result of a timeout while processing a request between servers, the problem is likely with them – not the internet connection or the user’s device. However, if just one user reports seeing a 504 error on your site, it could be with their modem, router, or other device. or your internet connection.

Because there can be multiple reasons for a 504 error to appear, it’s ultimately up to you to rule out each one until you find the real cause. Luckily, there are five common and effective solutions to fix most of the causes of 504 gateway timeout errors.

How to fix 504 gateway timeout errors Check for server connection issues. Look for DNS changes. Search your logs. Fix faulty firewall configurations. Comb your site’s code to find errors. Contact your hosting provider.

1. Check for server connection issues.

If your server is down for maintenance or other reasons, your website will likely present visitors with a 504 Gateway Timeout Error page. The only way to fix this problem is to wait for your server to finish maintenance or fix the problem that is causing the error.

2. Look for DNS changes.

If you’ve recently switched hosting providers or moved your website to a different IP address, your website’s DNS server needs to be updated. These DNS changes take a few hours to process, so your website may be showing visitors a 504 gateway timeout error page in the meantime. The only solution is to sit still while these DNS changes take effect.

3. Search your logs.

If the problem isn’t with your server’s connection or DNS information, look at your server logs. These logs contain details about the health and status of your server. Searching them might uncover other issues that could be causing a 504 error.

4. Correct incorrect firewall configurations.

A faulty firewall configuration can be the reason for your 504 gateway timeout error. To rule this out as a cause, you can temporarily disable your firewall.

If your device is running Windows, go to your Control Panel and click Update & Security > Windows Security > Virus & Threat Protection > Manage Settings. On this settings page you can disable your firewall.

If your device runs on Mac OS, simply navigate to System Preferences > Security & Privacy > Firewall to disable it.

After disabling your firewall, check if the 504 error is resolved. If this is the case, you can either reconfigure the settings of your existing antivirus or switch to a new one.

If the error is not resolved, don’t forget to re-enable your firewall before proceeding to the next step.

5. Comb your site’s code to find errors.

Comb your code to find bugs or copy your code to a development machine. It runs a thorough debugging process that simulates the situation where your 504 gateway timeout error occurred and allows you to see the exact moment when something went wrong.

6. Contact your hosting provider.

Contacting your hosting provider should be the last resort. But if you’ve tried the steps above and still see the 504 gateway timeout error, they might be able to solve the problem or provide valuable insights.

How 504 gateway timeout errors affect SEO

Fixing a 504 gateway timeout error can take time—but it’s worth it when you consider how it can affect your site’s technical SEO.

Like an internal HTTP server error 500, 503 error, or any other 5xx error, a 504 gateway timeout error will prevent your website from loading. This not only harms the user experience but also your SEO performance.

If a web crawler tries to crawl one of your pages and gets a 504 error, it can’t crawl the page. If this page has already been indexed, it may move down in search engine results. Or it could be deindexed if the error persists.

Fixing the 504 gateway timeout error

There is no foolproof way to prevent 504 gateway timeout errors on your website, but there are steps you can take to fix them. By fixing this error as soon as possible, you ensure that visitors continue to have a seamless experience on your website and mitigate any negative impact on your SEO.

Editor’s Note: This post was originally published in January 2019 and has been updated for completeness.

Have you ever been frustrated with proxy error codes you received while using proxies but have no idea why? Proxy error codes are similar to HTTP status codes. By learning what these errors mean, you can run your scraping activities smoothly and also automate your IP settings.

It is very likely that you will get such errors if you don’t properly manage your proxies during crawling or scraping activities. Problems can either come from your side (client side) or from the server side. In this article, you’ll learn about the most common types of proxy errors, why you get them, and how to fix them.

What is a proxy error?

A proxy error is an HTTP error status that you receive in response when a request sent to the web server through a proxy fails. In any case, to continue using the proxy, you need to find a solution. The response returned during a request failure can seem a bit confusing. If you are familiar with HTTP status codes, understanding proxy errors is not a problem.

status code classes

HTTP status codes are displayed as three digits. They are divided into five classes, so the first digit of each error code represents the class.

They are;

1. 1xx – Informational

2. 2xx – success

3. 3xx – Redirect

4. 4xx – Client Error

5. 5xx – Server Error

Common proxy error codes and their

solutions

1xx Informational error code

These are tentative answers, rarely used. These requests are considered used when the server processes the requests;

100 – Next

The code indicates that part of the request has been received and the client can continue sending the remaining request. Typically, the client first sends a request header with the directive “Expect: 100-continue” and gets the 100 status code from the server to send the request body. The “expectation” in the initial request is to avoid sending further requests if the server rejects the initial request header.

101 – Mediation Protocols

A web server sends a 101 status code when the browser requests to change the communication protocol during a transaction. If the client browser’s request asks the server to switch communication protocols and accepts, it sends the HTTP status code “100 – Switching Protocols” as confirmation.

102 – Processing (WebDAV)

The web server may need some time to process complex requests. When a client’s browser sends a WebDAV request with multiple sub-requests with complex requirements, the server takes some time to process and eventually sends this “102 – Processing” code. This code aims to avoid client-side timeout errors by informing the client that the server received and processed the request.

103 – Early Notes

The 103 – Early Hints code is received by the web server when sending the HTTP status to the browser before the HTTP requests are processed. The name indicates that this is an early indication to the client’s browser that the server has not yet started processing the requests.

2xx successful status code

Receiving codes between 200 and 299 means your proxy received your HTTP request, sent it to your intended website, and received a response. 200 is the most frequently received code, which informs that the server has successfully fulfilled the request. Look for any 2xx code other than 200 OK as it may indicate an error.

Here are the most common 2xx status codes;

201 – Created

This status code indicates that the server has completed the received request from the client and created a new resource based on the received request. The initial request acts as a trigger to generate a new response in the server. For example, when a server generates a new response based on a user’s credentials.

202 – Accepted

202 – Accepted is returned when the server receives the request from the client but has yet to process it. This is the only indication for accepting the request, but the result of processing the request will be known later when the “actual processing” takes place.

203 – Non-binding information

The code “203 – Non-Authoritative Information” was received when the server successfully processed the request, but returned the information from another resource to the requested client.

204 – No content

The server cannot find any content for the received request; It sends a 204 – No Content response code, which indicates to the client that no content will be returned.

205 – Reset content

Similar to the 204 code above. A request was successfully processed by the server, but no content is returned. The only difference is that the 205 code informs the client to reset the document view.

206 – partial content

A server returns this error code when it sends any part of the requested resource that is affected by the scope mentioned in the request header.

For example, the client requests a set of files to download and uses multiple streams to download the full content.

3xx – redirect error

3xx codes indicate that additional action is required from the client side to fulfill the request.

These status codes are not a problem if you use a browser (e.g. Google Chrome or Safari), but if you use your own script. Scripts you write and if there is no need to redirect the requests to other URLs will come in handy.

Because these actions can create infinite loops, web browsers typically follow no more than five consecutive redirects of the same request.

Some of the most common 3xx error codes are as follows:

300 – multiple choice

It occurs when a requested URL points to more than one resource.

The user-agent (crawler or web browser) cannot decide which page to fetch and receives an HTTP code “300 – Multiple Choices”.

Fix error code 300 by checking the HTTP headers and making sure the URL points to a single resource – so the user agent can successfully access the page.

301 – Resource moved permanently

This error is received when a permanent redirect to an original URL is set to redirect the user agent to a different URL.

If a web server sends the status code “301 – Moved Permanently” because a user cannot see the original URL, search engines would only index the redirected URL. Most search engine crawlers and user agents can track up to 5 redirects for a single URL. More than five redirects can lead to an infinite loop, and browsers like Chrome display a message like “Too Many Redirects”.

A 301 code is the most popular of all 3xx server response codes.

302 – Resource moved temporarily

A 302 – Moved Temporarily code is received when a temporary redirect is set to the original URL. This means that the user agent will be redirected to another URL after the request.

303 – See another resource

A “303 – See Another Resource” is received when the requested resource is at a different URL, and it should be requested using a “GET” method instead of code. Note that the originally requested page will only be indexed by the search engines if the code “200 – Success” is received.

304 – Resource not changed

A server would respond with the code “304 – Resource not changed” if the requested resource has not changed since the last request.

In this case, the server would assume that the data doesn’t need to be resent since the client already has a copy of the requested resource that hasn’t been modified.

Note that the “last time modified” is mentioned in the request header “If-Modified-Since” or “If-Match”.

Also, if your webpage has not changed since the last time search engine crawlers accessed your site, it is recommended to return the 304 code to speed up indexing and reduce crawler load.

305 – Use proxy

The 305 – Use Proxy code is displayed when the requested resource can only be accessed through a proxy server. The address of the proxy server is also received in the response and displayed in the browser window.

Some browsers such as Internet Explorer do not properly display this response due to security concerns when viewing the proxy server.

306 – Switch Proxy

The code “306 – switch proxy” indicates that the server should use the specified proxy for the following request(s).

307 – Temporary Redirect

A 307 – Temporary Redirect code is received when a requested resource is temporarily moved to a different address specified in the location header of the request. This is only a temporary redirect, but the next request should access the original URL. By the way, only the HTTP/1.1 protocol uses this status code.

308 – Permanent redirect

A “308 – Permanent Redirection” code is an experimental code to indicate a permanent redirect (similar to 307 set as a temporary redirect). Codes 307 and 308 are similar to codes 302 and 301, with the slight difference that the HTTP method is not changed.

4xx client error codes

The main types of HTTP proxy errors are 4xx and 5xx error codes. Receiving an error from the 4xx series indicates that the problem is on the client side. This can be your request, your browser or the automation bot.

400 – Invalid request

It’s a generic response indicating that there is a problem with your sent request. Sometimes your proxy server or the target website may not be able to parse your request. Problems can be malformed syntax, invalid formatting, or misleading request routing.

401 not authorized

The 401 – Unauthorized error code indicates that you are trying to access an unauthorized website that requires you to authenticate yourself.

The error is returned from the proxy server when the web server requires authentication and authorization. You can access the resource by providing credentials.

402 – Payment required

This response code is primarily set for future use. Even though this status code is relatively rare and no uniform convention exists, the goal in creating this code was for digital payment systems.

403 Forbidden

403 indicates that your request is valid and understood by the proxy or web server, but refuses to respond. This happens when you don’t have permission to view the resource.

404 Not found

This code is returned by the proxy server when the requested online resource is not available, even if the request is valid. Although 404 is primarily known as a “client error”, it results from dead links. This could mean that the URL has been removed, is incorrect, or has been modified without redirecting.

405 – Method not allowed

405 is received when a request method is known to the server but has been disabled and cannot be used. For example, an API request can forbid

“DELETE” a resource. Both mandatory methods, GET and HEAD, must never be disabled and should not return this error code.

406 – Not acceptable

A response is sent if, after performing server-driven content negotiation, the web server does not find any content matching the criteria specified by the user-agent.

407 – Proxy authentication required

A proxy displays a 407 code when authentication is required or when a tunnel fails to connect. This can happen if your scraper is not correctly authenticated with the proxy provider or if the credentials are inaccurate. Another reason may be that you are not whitelisting your IPs in the proxy settings.

To fix this error, you need to update your proxy settings by adding whitelisted IPs and entering the correct credentials. Also, make sure that all required information is also included in the request.

408 Request timed out

This error code is received when a client has not generated a request while the server is configured to wait or hold. The client can repeat the request at any time without changing it.

If the 408 error persists, check the load generated on your web server when you spot the errors. Another possibility could be connection problems.

409 – Conflict

The 409 conflict usually has nothing to do with the authority or security of the default web server, but with a specific application, conflicts that are not defined in the HTTP protocol itself.

The web server responds with this error when it considers the client’s requests to be legitimate, but a request could not be completed due to a conflict with the current state of the resources. The response body usually contains enough information for users to identify the cause of the conflict and troubleshoot the problem.

410 – way

The web server responds with this error code when the requested resource is no longer available through the server, will not be available again, and has no known forwarding address. This error is similar to the 404 error, but 410 is a permanent error.

411 – Length required

This error code means that the server refuses to accept the request without a defined content length. The client should repeat the request by adding a valid Content-Length header field containing the length of the message body in the request’s message.

412 – Precondition failed

The web server responded with this error code when preconditions are specified in one or more of the request header fields that evaluated as false when tested on the server.

This status code allows the client to place preconditions on current resource meta information (header field data) and prevents the requested method from being applied to a resource other than the originally intended one.

413 – Request unit too large

The server refuses to process a request because the request entity is larger than what the server can handle. The server could close the connection to prevent the client from sending more of the same request.

“What is ‘too large’ depends in part on the surgery being attempted. For example, a request to upload large files (via the HTTP PUT method) may encounter upload file size limits set by the web server.”

414 – Request URL too long

The web server responds with this error when it refuses to serve the request because the request URL is longer than the server can handle. This rare condition is more likely to occur when a client has incorrectly converted “POST” requests to “GET” requests, with long query information, once the client has entered a URL redirection “black hole” (meaning that a redirected URL prefix showing a custom suffix) or

This error code can also be received when the server is being attacked by a client trying to exploit vulnerabilities that exist on some servers, also using fixed-length buffers for reading and manipulating request URLs. Typically, web servers set fairly generous length limits on real URLs. If a long URL is valid and you still get a 414 error code, it means the web server may need to be reconfigured to allow such URLs through.

415 – Unsupported media type

The web server refuses to complete the request because the request’s entity is in formats not supported by the requested resource for the requested method.

416 – Requested range not satisfiable

The 416 status code is received when a server’s response usually returns 416 when a request contains a “Range” request header field. No range-specific values ​​in this field overlap the current extents of selected resources, and the request had no If-Range request header field.

For example, if the resource is a 1000 bytes file and the requested range is 500-1500, this may not be sufficient as an acceptable range.

417 – Expectation failed

The web server typically responds with this status code when the expectation received in an “Expect” request header field cannot be met by the server, or when the server is a proxy and has strong evidence that the next-hop server has the could not fulfill request.

429 – Too many requests

This error is likely to occur when too many requests are sent within a limited time frame while using the same IP address. Websites typically implement such restrictions to protect themselves from attackers and avoid overloading.

Using rotating proxies can fix this error code by setting delays between requests per IP and per a specific time frame.

5xx – Server Error

Series of 5xx is returned when the server successfully receives the request but cannot process the request or encounters a problem processing it.

To fix all those 5xx errors, rotate IPs and change proxy network and IP type. Using a private proxy network is better in such cases to rotate IPs and ensure reliability.

You may get error codes like –

500 – Internal server

The 500 – Internal Server error code is received when the server encounters an unexpected condition that prevents it from responding to the request.

501 – Not implemented

The 501 – Not Implemented error is received when the server cannot provide the requested resource due to an unsupported or unrecognized method(s) in the request.

502 Bad Gateway

This error often occurs during data collection when the server is acting as a gateway or proxy and receives an invalid response from another server.

When super proxies refuse the Internet connection or sent requests, the unavailability of IPs for selected settings is detected, as bots display 502 code.

503 – Services not available

The 503 – Service Unavailable code is received when a server receives the request at the same time as other requests are overloading it, or is in scheduled downtime/maintenance. In this case, check the status of the requested server if possible.

504 – Gateway Timeout

“504 – Gateway Timeout” is received when a server (a) is acting as an external gateway or proxy and does not get the response in time from the next server (b) that is further up the request chain trying to fulfill the request.

505 – HTTP version is not supported

A “505 – HTTP Version Not Supported” code is received when a server does not support the HTTP protocol version and is used in the request message.

507 – Insufficient disk space

“507 – Insufficient Storage” means that the server has run out of disk space and is no longer fulfilling the request.

510 – Extensions are missing

The server cannot process the request because an unsupported extension is requested, then the code “510 – Not Extended” is received.

Solving common proxy error codes

The easiest way to solve these proxy error codes is to use a proxy manager. A proxy manager is often free, open-source software that automates proxy management to avoid such errors. To prevent the 407 error code, you need to choose a proxy port. Then all related credentials and zone information will be updated automatically.

You can apply specific actions in your proxy manager when a rule you apply is triggered. To avoid errors like 403 it is important to rotate your IPs; Hence, home proxies are the best option. NetNut can do its part by integrating with your proxy tools to avoid these errors. Learn how to integrate NetNut to configure your proxy settings.

Also check out our GitHub repositories for a better understanding of advanced usage with our proxies, code documentation, and walkthroughs.

In summary, the basic steps you can follow to fix these proxy errors are:

1. Switch to residential proxies

Although home proxies are a bit more expensive, unlike data center proxies, they offer a large pool of proxies. Therefore, you can rotate your IPs and avoid getting blocked.

NetNut is a better example of a private proxy service provider that uses a dynamic P2P + ISP proxy network and offers both rotating and static private IPs.

2. Reduce the number of requests

Sending too many requests at once makes any website suspicious. Set a slight delay between requests to avoid errors.

3. Improve IP rotation

As explained above, using a proxy management tool helps accomplish this task. Control your IP sessions to minimize requests from the same IP address.

4. Have a good working scraper

Following the above factors but using a poorly performing scraper can still lead to errors. Therefore, make sure you have an advanced scraper to bypass obstacles implemented by websites.

Remember!

The first steps to overcoming these proxy errors is to understand the error code and why you are getting such a code. By understanding such causes while implementing these techniques, you can run your data collection smoothly and minimize errors.

Can’t find a solution to your error code? Ping us via email and our support experts can help!

You look at the Apigee Edge documentation.

Check out the Apigee X documentation.

Was this troubleshooting playbook helpful? Please let us know by clicking Send Feedback.

videos

Watch the videos below to learn more about fixing 500 internal server errors.

Video Description Introduction Provides an introduction to 500 internal server errors and possible causes. Also shows a 500 Internal Server real-time error along with steps to troubleshoot and fix the error. Handling Service Callout and Extract Variables Errors Illustrates two 500 internal server errors caused by Service Callout and Extract Variables policies and shows how to troubleshoot these errors. Handling JavaScript Policy Errors Displays an internal server error of type 500 caused by a JavaScript policy and the steps to troubleshoot and resolve this error. Handling Back-End Server Errors The example shows 500 internal server errors caused by an error on the back-end server and steps to resolve the errors.

symptom

The client application receives an HTTP status code of 500 with the message “Internal Server Error” in response to API calls. The 500 Internal Server error can be caused by an error during the execution of any policy in Edge or by an error on the target/backend server.

The HTTP status code 500 is a generic error response. This means that the server encountered an unexpected condition that prevented it from fulfilling the request. This error is typically returned by the server when no other error code is appropriate.

error messages

You may get the following error message:

HTTP/1.1 500 Internal server error

In some cases, you may see a different error message that provides more detail. Here is an example error message:

{ “fault”:{ “detail”:{ “errorcode”:”steps.servicecallout.ExecutionFailed” }, “faultstring”:”Execution of ServiceCallout callWCSAuthServiceCallout failed. Reason: ResponseCode 400 is treated as an error” } }

Possible causes

The 500 Internal Server Error can be triggered due to various causes. In Edge, the causes can be divided into two main categories depending on where the error occurred:

Cause Details Detailed troubleshooting steps are provided for execution errors in an edge policy A policy inside the API proxy can fail for some reason. Edge Private and Public Cloud Users Backend Server Error The backend server can fail for some reason. Edge Private and Public Cloud users

Execution error in an edge policy

A policy inside the API proxy can fail for any reason. This section explains how to troubleshoot when the internal server error 500 occurs during policy execution.

diagnosis

Note: The 500 Internal Server error can appear for many different reasons. For example, a 500 error can occur when a policy is executed, or it can originate on the backend target server. That’s why we’ve provided some general diagnostic steps below to help you identify and fix this type of problem. We also provide several examples that provide specific steps to resolve these errors, depending on the cause of the issue.

Diagnostic steps for private and public cloud users

If you have the trace UI session for the error then:

Verify that the error was caused by a policy execution. For more information, see Determining the cause of the problem. If the error occurred during policy execution, continue. If the error was caused by the backend server, go to Backend server error. Select the API request that fails with 500 Internal Server Error in the trace. Examine the request and select the specific failed policy or flow named “Error” that immediately follows the failed policy in the trace. You can get more details about the error by checking either the Error field in the Properties section or the error content. Using the details you have gathered about the error, try to determine the cause.

Diagnostic steps for Private Cloud users only

If you don’t have the trace UI session then:

Verify that the error occurred while executing a policy. For more information, see Determining the cause of the problem. If the error was caused by policy execution, continue. If the error occurred during policy execution, continue. If the error was caused by the backend server, go to Backend server error. Use the Nginx access logs as described in Determining the source of the problem to determine the faulty policy in the API proxy and also the unique request message ID. Check the message processor logs ( /opt/apigee/var/log/edge-message-processor /logs/system.log ) and look for the unique request message ID in them. Once you find the unique request message ID, see if you can get more information about the cause of the error.

resolution

Once you determine the cause of the policy issue, try to fix the issue by repairing the policy and redeploying the proxy.

The following examples show how to find the cause and solution for different types of problems.

If you need further assistance troubleshooting 500 Internal Server Error or suspect it is an issue in Edge, contact Apigee Support.

Example 1: The service callout policy failed due to an error in the backend server

If the call to the backend server within the service callout policy fails with an error like 4XX or 5XX, it is treated as a 500 Internal Server Error.

Here is an example where the backend service fails with a 404 error within the service callout policy. The following error message is sent to the end user: { “fault”: { “detail”: { “errorcode”:”steps.servicecallout.ExecutionFailed” },”faultstring”:”Execution of ServiceCallout service_callout_v3_store_by_lat_lon failed. Reason: ResponseCode 404 is reported as Error handled” } } } The following Trace UI session shows the 500 status code caused by an error in the service callout policy: In this example, the “error” property lists the reason why the service callout failed policy as “ResponseCode 404 is treated as an error”. This error can occur when the resource accessed through the backend server URL in the service callout policy is not available. Check the availability of the resource on the backend server. It may be temporarily/permanently unavailable or moved to another location.

Example 1 resolution

Check the availability of the resource on the backend server. It may be temporarily/permanently unavailable or moved to another location. Correct the backend server URL in the service callout policy to point to a valid and existing resource. If the resource is temporarily unavailable, try making the API request as soon as the resource becomes available.

Example 2: Extract variables policy failed

Now let’s look at another example where 500 Internal Server Error is caused due to error in Extract Variables Policy and see how to troubleshoot and fix the problem.

The following trace in the UI session shows status code 500 due to an error in the variable extracting policy: Select the failed extracting variable policy, scroll down and look at the Error Contents section to see to get more details:

The error content indicates that the variable “serviceCallout.oamCookieValidationResponse” is not available in the extract variable policy. As the name of the variable suggests, it should contain the response from the previous service callout policy. Select the service callout policy in the trace and you may find that the serviceCallout.oamCookieValidationResponse variable has not been set. This indicates that the call to the backend service failed, resulting in an empty response. Even though the service callout policy failed, the policies after the service callout policy continue to run because the “ContinueOnError” flag in the service callout policy is set to true as shown below:

Callout.OamCookieValidation false serviceCallout.oamCookieValidationResponse http://{Url} Note the unique message ID “X-Apigee.Message-ID” for this specific API request from the trace as follows: Select the “Analytics Data Recorded” stage from the request. Scroll down and note the value of X-Apigee.Message-ID. Note: The following steps can only be performed by the Edge Private Cloud users. View the message processor log ( /opt/apigee/var/log/edge-message-processor/system.log ) and look for the unique message ID you noted in step 6. The following error message was observed for the specific API request: 2017-05-05 07:48:18,653 org:myorg env:prod api:myapi rev:834 messageid:rrt-04984fed9e5ad3551-c-wo-32168-77563 NIOThread@5 ERROR HTTP.CLIENT – HTTPClient$Context.onTimeout() : ClientChannel[C:]@149081 useCount=1 bytesRead=0 bytesWritten=0 age=3002ms lastIO=3002ms .onConnectTimeout connectAddress=mybackend.domain.com/XX.XX.XX .XX:443 resolveAddress=mybackend.domain.com/XX.XX.XX.XX The error above indicates that the service callout policy failed due to a timeout error while connecting to the backend server. To determine the cause of the connection timeout error, telnet to the backend server from the message processors. The telnet command gave the connection timed out error shown below: telnet mybackend.domain.com 443 Trying XX.XX.XX.XX… telnet: connect to address XX.XX.XX.XX: Connection timed out This error Occurs under the following circumstances: When the backend server is not configured to allow traffic from the Edge message processors.

If the backend server is not listening on the specific port. In the example shown above, although the extract variables policy failed, the root cause was that Edge was unable to connect to the backend server in the service callout policy. And the cause of this error was that the backend end server was not configured to allow traffic from the edge message processors. Your own extract variable policy behaves differently and may fail for a different reason. Depending on the cause of the error, you can fix the problem according to your extract variable policy by checking the message in the error property.

Example 2 resolution

Resolve the root cause of any errors or failures in the Extract Variables policy accordingly. In the example shown above, the solution was to correct the network configuration to allow traffic from edge message processors to your backend server. To do this, the IP addresses of the message processors were allowed-listed on the respective back-end server. For example, on Linux, you could use iptables to allow traffic from the IP addresses of the message processor on the backend server.

Example 3: Error in JavaCallout policy

Now let’s look at another example where 500 Internal Server Error is caused due to a bug in the Java callout policy and see how to troubleshoot and fix the problem.

The following UI trace shows the status code 500 due to an error in the Java callout policy: Select the flow named “Error” followed by the failed Java callout policy to get the error details, as shown in the image below : In this example, “error” property in the Properties section shows that the error is due to an expired password used when connecting to the Oracle database within the JavaCallout policy. Your own Java callout behaves differently and fills in a different message in the error property Check the JavaCallout policy code and confirm the correct configuration to use.

Example 3 resolution

Correct the Java callout code or Java configuration accordingly to avoid the runtime exception. In the Java callout error example above, one would need to use the correct password to connect to the Oracle database to resolve the issue.

Backend server error

A 500 Internal Server Error can also come from the backend server. This section explains how to troubleshoot when the error comes from the backend server.

diagnosis

Diagnostic steps for all users

The cause of other backend errors can be very different. You must diagnose each situation independently.

Verify that the error was caused by the backend server. For more information, see Determining the cause of the problem. If the error was caused by the backend server, continue. If the error occurred during policy execution, go to Edge Policy Execution Errors. Perform the following steps depending on whether you have access to a trace session for the failing API or whether the backend is a Node.js server:

If you don’t have a trace session for the failed API call:

If the UI trace for the failed request is not available, check the backend server logs for details about the error. If possible, enable debug mode on the backend server to get more details about the error and the cause.

If you have a trace session for the failed API call:

If you have a trace session, the following steps will help you diagnose the problem.

In the trace tool, select the API request that failed with 500 Internal Server Error. Select the Received response from target server phase from the failed API request as shown in the following image: Check the Response Content section for details about the error. In this example, the response content, which is a SOAP envelope, displays the error string as an “Unauthorized” message. The most likely cause of this problem is that the user is not submitting the correct credentials (username/password, access token, etc.) to the backend server. This issue can be resolved by passing the correct credentials to the backend server.

If the backend is a Node.js server:

If the backend is a Node.js backend server, check the Node.js logs for the specific API proxy in the Edge UI (both public and private cloud users can check the Node.js logs) . If you are an Edge Private Cloud user, you can also check your message processor logs ( /opt/apigee/var/log/edge-message-processor/logs/system.log ) for more details about the error.

NodeJS Protocols option in Edge UI – API Proxy Overview tab

resolution

Once you identify the cause of the error, troubleshoot the issue on your back-end server. If it’s a Node.js backend server: Check if your custom code is throwing the error and fix it if possible. If your custom code is not throwing the error or you need help, contact Apigee Support.

If you need further assistance troubleshooting 500 Internal Server Error or suspect it is an issue in Edge, contact Apigee Support.

Determining the cause of the problem

Use one of the following methods to determine if the internal server error 500 was thrown while executing a policy in the API proxy or from the backend server.

Using Trace in the UI

Note: The steps in this section can be performed by both public and private cloud users.

If the issue persists, enable UI tracing for the affected API. After capturing the trace, select the API request that shows a 500 response code. Navigate through each stage of the failed API request and see which stage is returning the 500 Internal Server Error: If the error is triggered during the execution of a policy, then continue to Execution Errors in an Edge Policy. If the backend server responded with 500 Internal Server, go to Backend server error.

Use API monitoring

Note: The steps in this section can only be performed by public cloud users.

With API monitoring, you can quickly isolate problem areas to diagnose error, performance, and latency issues and their source, e.g. B. Developer apps, API proxies, backend targets or the API platform.

Walk through an example scenario that shows how to use API Monitoring to troubleshoot 5xx issues with your APIs. For example, you might want to set up an alert to be notified when the number of 500 status codes or steps.servicecallout.ExecutionFailed errors exceeds a certain threshold.

Using Nginx access logs

Note: The steps in this section apply only to Edge Private Cloud users.

You can also refer to Nginx access logs to determine if the 500 status code was thrown during policy execution in the API proxy or by the backend server. This is especially useful if the problem has happened in the past or if the problem is intermittent and you can’t capture the trace in the UI. Use the following steps to get this information from Nginx access logs:

Google’s John Mueller answered a question about when 500 error response codes will cause Googlebot to crawl content less frequently. Mueller explained scenarios where 500 response codes don’t affect crawling and can cause pages to drop from Google’s index.

Accidentally blocked Googlebot and caused 500 errors

The person who asked the question explained that their content delivery system is set up to block malicious bots while allowing actual human users and legitimate bots to browse the site.

Everything was working fine until they updated their “Server Monitoring Suite” and apparently the previous filters and bot blocking settings didn’t carry over to the new system.

After that, they noticed that Google Search Console started listing 500 error response codes in response to Googlebot crawling.

The person finished explaining what happened and then asked the question:

“Our technology team questioned whether this was a real impact on users and why we should look specifically at Googlebot rather than actual user metrics to prove there is an issue here. Given this context, I have a few questions. The first is to get the technology concerns out of the way. How do you think Googlebot sees 500-series bugs, and could you give us some clarity on established…thresholds beyond which Googlebot will…crawl…less…source content…based on those bugs?”

What is a 500 error code?

Servers communicate a variety of status response codes to browsers and bots. These response codes tell, for example, whether a page’s request was successful, redirected to another page, blocked, or unsuccessful.

A 200 response code indicates that the request for a web page was successful.

A 500 response code means that the request for a web page was unsuccessful.

The formal name of the 500 response code is:

“500 Internal Server Error”

There are other versions of the 500 response code that indicate a specific reason why a webpage request was unsuccessful.

The 500 response code is somewhat generic as it simply means that the page request was unsuccessful. But it often means the server is down, but not always.

Google Search Console and 500 error responses

It’s a good idea to monitor Search Console for 500 error responses as they are a strong indicator that something is wrong.

Sometimes it can mean that the server is under heavy load, for example from too many bots, and is therefore unable to serve websites.

In this case, the problem appears to be due to a misconfiguration in the Content Delivery Network (CDN) that inadvertently blocked Google from accessing webpages.

How Googlebot indexing is affected by 500 errors

Mueller provided a helpful explanation of the steps Google takes in response to 500 error codes and how eventually continued errors can result in those webpages being removed from Google’s search index.

Google’s John Mueller replied:

“We don’t have strict limits. But essentially, 500 errors is what we try to try again. And if we keep seeing… the 500 errors, we’ll… slow down the crawl. And if we continue to see that there are 500 errors, we will remove those URLs from the index. So that’s something, if every now and then individual pages have a 500 error, it’s not a big deal. We’ll try them again, they’ll stay indexed and next time we try them again, that’s fine.”

Next, Mueller explains that the reason Googlebot is slowing down crawling is because Googlebot itself is causing server overload.

“But if a large chunk of a page has 500 errors all the time and we maybe assume we’re causing the problem and we slow down the crawling of the whole page and at some point we say well it looks like pages are really gone, we’re going to drop them.” to let. So that’s basically the effects you would see there, and if you’re talking about a big site and you’re wondering what percentage of 500 errors is okay… I don’t know. My feeling is if you see anything over one percent then that sounds like something is broken and it’s probably something where we would start to slow down. But I don’t think we have hard limits where we would say that so many requests and so many bugs mean that much slowdown.”

Monitor Search Console for 500 errors

It is up to each publisher to decide what his daily routine looks like. For some people, checking the search console once a week is enough. Some may find it comforting to check Search Console once a day to respond to unforeseen circumstances.

In any case, you should monitor Search Console for 500 error codes. As John Mueller mentioned, big 500 errors could be an indication that something is wrong and needs immediate attention.

quotes

List of server response codes from the World Wide Web Consortium (W3C).

How does Google respond to 500 response codes?

Watch the discussion starting at minute 13:48

We tried to ping the Google website through our server and the website returned the above results. If 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 service health activity for 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 Google – Troubleshooting Guide Cannot Access Google – 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.).

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.