If you have been running a website for a while, you will have most likely encountered the 505 HTTP Version Not Supported error.
It's a message that tells you: "HTTP Version Not Supported."
But why does it appear on your site, and are there any quick ways to fix it?
This article provides an overview of the 505 error along with the tips and solutions to resolve the issue quickly and cost-effectively.
The HTTP status code 505 is a client error code that means, "The server encountered an internal error or misconfiguration." When the server encounters an error, it's usually related to a misconfiguration of server-side programming.
This HTTP response code means that the server cannot communicate with the client for whatever reason – whether it be an incorrect URL, a connection issue, or an out-of-date client.
These errors are some of the most frustrating for website owners to deal with because they are not easy to detect and can be time-consuming to fix.
That’s because HTTP version not supported errors don’t indicate problems on your website or particular posts or pages. Instead, they usually reflect problems that are specific to your visitors’ internet access points, such as the network or ISP.
Before we answer this question, let's first take a look at how the internet works.
There are two main players on the internet: servers and clients.
Let's say that you're using your browser to open a web page. You're accessing the internet through a web client.
The web client sends a message to the server with your request to access the web page. The server returns an HTTP status code every time you make a request to your server to access a resource.
That status code can be a successful request, a client error, or a server error. In fact, there are five groups of HTTP response status codes, including:
1xx status codes: Informational requests
2xx status codes: Successful requests
3xx status codes: Redirects
4xx status codes: Client errors
5xx status codes: Server errors
Although somewhat different, they all inform a user whether a specific HTTP request has been successfully completed.
The 505 HTTP Version Not Supported response status code that we're looking into today belongs to the 5xx status codes group or the redirects. These are the server errors that indicate something on the server-side of things is the problem. The most common errors in the group include the 501 Not Implemented and the 507 Insufficient Storage.
On the other hand, response codes in the 4xx group, like the 404 Not Found error and the HTTP 405 Error, are client errors that indicate the problem is with the client.
If you come across a 505 error on your site, the first thing you want to do is update your web browser. If you're using an older version, update to a newer version or switch to a modern browser. If the error goes away, congrats, you've done it!
If the error still appears on your site, the next troubleshooting tip is to upgrade your origin Web server software to support the major version of the HTTP protocol you require.
The error message will tell you what protocols are supported by your origin server. You need to review those protocols in order to troubleshoot the error. The error may specifically state which program name does not support the protocol. If so, review that information to fix the error.
The next step is to make sure that you have not left any whitespace after the HTTP version in the URL. Also, double-check to see the URL you inserted doesn't contain any special characters that may cause the issue.
A 505 HTTP Version Not Supported status code indicates that the server encountered an internal error or misconfiguration. These errors are some of the most frustrating for website owners to deal with because they are not easy to detect and can be time-consuming to fix.
The 505 HTTP Version Not Supported belongs to the 5xx status codes group or the redirects. These are the server errors that indicate something on the server-side of things is the problem.
The best way to fix the status code is to:
Update your web browser or switch to a modern browser.
Upgrade your origin Web server software to support the major version of the HTTP protocol you require.
Make sure that you have not left any whitespace after the HTTP version in the URL.
Check to see if the URL you inserted doesn't contain any special characters.
As seen in