How do fix an 803 Error?

[Zippy-Bungle]

I got am 803 error this week on the Moz crawl for one of my pages. The page loads normally in the browser. We use cloudflare.

Is there anything that I should do or do I wait a week and hope it disappears?

803 Incomplete HTTP response received

Your site closed its TCP connection to our crawler before our crawler could read a complete HTTP response. This typically occurs when misconfigured back-end software responds with a status line and headers but immediately closes the connection without sending any response data.

[KristinaKeyser]

Kristina from Moz's Help Team here. Here is the working link to our Crawl Errors resource guide if you're still needing it!

https://moz.com/help/guides/moz-pro-overview/crawl-diagnostics/errors-in-crawl-reports

[wukonig]

It would be great to read more about this issue here. I would love to debug/troubleshoot the 803 Errors, but I have no idea where to start. One problem: It's not possible to adjust the crawl-speed/delay of the moz-bot so I can't tell it the bot is the problem or not. Any suggestion out there how to debug a 803 crawl error?

TIA,

Jörg

[Mad_Pack]

Hi Sha,

The first link with the complete list is not working. I would love to access it. Where can I find the link?

Thanks in advance, Michiel

[phpaddicted]

Same here, I found error on 803 in an image, What to do now? Can you pls help?

Thnaks

[viatrading1]

Hi,

Found a 803 Error in an image. Does that mean I should compress/improve somehow the image, or is it a web server error?

Thank you,

[Zippy-Bungle]

So if it is a standard wordpress page  would the issue likely to be with the wordpress code - or my on-page content?

[ShaMenz]

Hi Zippy-Bungle,

To understand first why the 803 error was reported:

When a page is called, the web server sends header details of what's to be displayed. You can see a complete list of these HTTP header fields here.

One of the headers sent by the web server is Content-length, which indicates how many bytes the rest of the page is going to send. So let's say for example that content length is 100 bytes but the server only sends 74 bytes (it may be valid HTML, but the length does not match the content length indicated)

Since the web server only sent 74 bytes and the crawler expected 100 bytes the crawler sees a TCP close port error because it is trying to read the number of bytes that the webserver said it was going to send. So you get an 803 error.

Now browsers don't care when a mismatch like this happens because Content-length is an outdated component for modern browsers, but Roger Mozbot (the Moz crawler, identified in your logs as RogerBot) is on a mission to show you any errors that might be occurring. So Roger is configured to detect and report such errors.

The degree to which an 803 error will adversely affect crawl efficiency for search engine bots such as Googlebot, Bingbot and others will vary, but the fundamental problem with all 8xx errors is that they result from violations of the underlying HTTP or HTTPS protocol. The crawler expects all responses it receives to conform to the HTTP protocol and will typically throw an exception when encountering a protocol-violating response.

In the same way that 1xx and 2xx  errors generally indicate a badly-misconfigured site, fixing them should be a priority to ensure that the site can be crawled effectively. It is worth noting here that bingbot is well known for being highly sensitive to technical errors.

So what makes the mismatch happen?

The problem could be originating from the website itself (page code), the server, or the web server. There are two broad sources:

1. Crappy code
2. Buggy server

I'm afraid you will need to get a tech who understands this type of problem to work through each of these possibilities to isolate and resolve the root cause.

The Moz Resource Guide on HTTP Errors in Crawl Reports is also worth a read in case Roger encounters any other infrequently seen errors.

Hope that helps,

Sha