Ⅰ. What is an HTTP 505 error?
HTTP 505 (HTTP Version Not Supported) is a type of 5xx server error, indicating that the server is unable to process the client’s request because the version of the HTTP protocol used in the request is not supported by the server. Put simply, the client and server are ‘speaking different versions of the HTTP language’, resulting in a communication failure.
When a browser or client sends a request to a server, it declares the HTTP version being used in the request header (e.g. HTTP/1.0, HTTP/1.1, HTTP/2 or HTTP/3). If the server does not support that version, it will return a 505 error.
II. Common Causes of HTTP 505 Errors
1. The client is using an unsupported HTTP version
This is one of the most common causes. Possible scenarios include:
– Outdated browser: Accessing modern websites using older browsers such as Internet Explorer, which may default to HTTP/1.0 or earlier versions
– Incorrect client software configuration: Certain automation tools, API clients explicitly specify an HTTP version that the server does not support
– Version too new: The client attempts to use HTTP/3, but the server only supports up to HTTP/1.1
2. Server configuration issues
– Outdated server software: Web server software such as Apache or Nginx has not been updated in a timely manner and does not support newer HTTP protocol versions
– Configuration file errors: The target HTTP version has not been correctly enabled in the server configuration file (e.g. HTTP/2 support is not enabled)
– Inconsistent virtual host configuration: The main domain is configured correctly, but the virtual host configuration for subdomains omits protocol version support
3. Incompatibility with middleware or gateway devices
In complex network architectures, gateway servers, load balancers, CDNs or firewalls may become bottlenecks:
– The gateway modifies the HTTP version when forwarding requests
– The load balancer is incorrectly configured and does not support protocols such as HTTP/2
– WAF (Web Application Firewall) blocks requests of specific versions
– Issues with network egress quality: when using low-quality shared network egress, nodes may not support modern HTTP protocols, leading to failed version negotiation
4. Application-layer bugs
– WordPress plugins or third-party components trigger version mismatches during external link redirection
– Incompatible HTTP versions are hard-coded in custom application code
– Server logs may display specific details regarding the failed protocol negotiation
III. Solutions for HTTP 505 Errors
▶ Client-side solutions (general users)
1. Update your browser
Ensure you are using a newer version of Chrome, Firefox, Edge or Safari. Modern browsers support HTTP/2 and even HTTP/3 by default, enabling them to communicate normally with most servers.
2. Clear your browser cache
Cached data may contain outdated protocol negotiation information:
– Chrome: Settings → Privacy and security → Clear browsing data → Select ‘Cached images and files’
– Firefox: Settings → Privacy & Security → Clear Data
3. Try using a different browser
If you encounter a 505 error in Chrome, try accessing the same website using Firefox or Edge. If other browsers work normally, the issue lies with the configuration or cache of the specific browser.
4. Check the URL spelling
Ensure the URL is correct, including the protocol (http:// or https://) and the domain name spelling.
5. Temporarily disable network acceleration tools for testing
If you are using a network acceleration tool, try temporarily disabling it and reloading the page. If the error disappears, it suggests that an intermediate gateway may be causing the HTTP version mismatch.
▶ Server-side solutions (web administrators/developers)
1. Upgrade server software
Ensure that web servers such as Apache, Nginx, and IIS are running newer, more stable versions. For example:
– Nginx 1.9.5+ supports HTTP/2
– Apache 2.4.17+ supports HTTP/2 (requires the mod_http2 module to be enabled)
2. Check and modify server configuration
Nginx configuration example (enabling HTTP/2):
Within the server block, add the http2 parameter to the listen directive, for example: listen 443 ssl http2;
Apache configuration example:
Enable the HTTP/2 module and add the following to the configuration: Protocols h2 h2c http/1.1
3. Check middleware configuration
– If using a CDN such as Cloudflare, confirm that it supports the required HTTP version
– Check whether the load balancer has ALPN (Application-Layer Protocol Negotiation) enabled
– Ensure that the firewall is not blocking traffic for specific HTTP versions
4. Review server logs
Analyse Apache’s `error.log` or Nginx’s `error.log`, search for error entries related to HTTP versions, and identify the specific cause.
▶ Advanced Scenarios: Cross-border Network Access and Data Collection
For developers, data analysts, or users requiring cross-border network access, HTTP 505 errors are often closely related to the quality of the network gateway.
Typical scenarios:
– When using a low-quality shared network gateway, the node may be running outdated software that does not support HTTP/2, resulting in requests being downgraded or rejected
– In cross-border data collection, API integration or automated testing, a mismatch in protocol versions between the gateway server and the target server will directly trigger a 505 error
– Certain websites detect and block requests from specific network gateways, returning a 505 error as an anti-crawling measure
Solution: Use high-quality overseas network services
When stable, reliable network services are required, Novproxy provides professional overseas network solutions.
– Stable overseas nodes: Provides overseas server nodes to reduce the risk of being identified as abnormal traffic
– Protocol compatibility: Supports mainstream protocol versions such as HTTP/1.1 and HTTP/2 to avoid 505 protocol mismatch errors
– High anonymity: Effectively protects network privacy, suitable for scenarios such as data collection, cross-border e-commerce and social media operations
– Global coverage: Covers major markets including the US, Europe and Southeast Asia, meeting cross-border business needs
Visit the official website to find out more: [https://novproxy.com]
IV. Quick Troubleshooting Checklist
Troubleshooting step Action Applicable users
| Step | Action | Target Audience |
| 1 | Refresh the page (F5) or restart the browser | General Users |
| 2 | Update the browser to the latest version | General Users |
| 3 | Clear browser cache and cookies | General Users |
| 4 | Test using a different browser | General Users |
| 5 | Temporarily disable network acceleration tools (VPNs/Proxies) | Users using acceleration tools |
| 6 | Check server software versions (Apache/Nginx) | Website Administrators |
| 7 | Check protocol support in server configuration files | Website Administrators |
| 8 | Review server error logs | Website Administrators |
| 9 | Inspect CDN/Load Balancer configurations | Middleware Architects |
| 10 | Switch to high-quality overseas network services (e.g., Novproxy) | Developers / Cross-border Business Users |
V. Summary
The root cause of the HTTP 505 error lies in incompatibility between the HTTP protocol versions used by the client and the server. The solution is straightforward: first determine whether the issue lies on the client or server side, then address it accordingly.
– General users: Prioritise updating your browser, clearing the cache, or switching to a different browser
– Developers/administrators: Check server configurations, upgrade software, and troubleshoot middleware
– Cross-border business/data collection users: Ensure you use a high-quality network service that supports modern HTTP protocols, such as the overseas network service provided by Novproxy, to fundamentally avoid 505 errors caused by protocol incompatibility at gateway nodes
By systematically investigating protocol versions, middleware configurations and the quality of network gateways, HTTP 505 errors can be quickly identified and resolved.