Why Your Australian Website Is Returning 505 HTTP Version Not Supported Errors
Summary
This guide helps you troubleshoot and resolve: Why Your Australian Website Is Returning 505 HTTP Version Not Supported Errors. Follow the steps below to fix the issue.
Common Causes
When a visitor attempts to load your website, their web browser sends a request using a specific version of the Hypertext Transfer Protocol (HTTP). If your web server does not recognise or support that protocol version, it responds with a 505 HTTP Version Not Supported error. Unlike a standard 500 Internal Server Error, which indicates a general server malfunction, a 505 error specifically means the server refuses to support the protocol version requested by the client. For Australian small businesses, this often means customers cannot access your site at all, leading to lost enquiries and sales.
What Causes a 505 Error
A 505 error occurs when the client—usually a modern web browser—requests a connection using a protocol version that the web server does not support. For example, if a browser attempts to negotiate an HTTP/3 connection but the server is only configured for an outdated version or lacks the necessary modules to handle the request, the server will reject the connection with a 505 status code. This is determined entirely by the server's configuration, not by any setting on the visitor's computer or mobile device.
Steps to Resolve a 505 Error
Because this issue originates on the server, website owners and visitors cannot resolve it through client-side actions. Follow these steps to engage your hosting provider and gather the technical information they need to fix the problem.
1. Document the Error
- Visit your website and note the exact time and date the
505 HTTP Version Not Supportederror appears. - Record the full URL of the page that triggered the error.
- Open your browser's developer tools by pressing
F12orCmd + Option + Ion Mac. - Select the Network tab, refresh the page, and click on the failed request.
- Look at the Response Headers to confirm the status code is
505and note any details regarding the protocol version being used.
2. Run a Curl Test
- Open your terminal (Command Prompt or PowerShell on Windows, Terminal on macOS).
- Run the following command, replacing
yourdomain.com.auwith your actual domain: curl -I https://www.yourdomain.com.au- Review the output. If the server returns a
505status, copy the full output including the headers to share with your host.
3. Contact Your Hosting Provider
- Log in to your hosting support portal.
- Open a new support ticket via Open a Ticket.
- Provide the following details in your request:
- The exact error message:
505 HTTP Version Not Supported - The date and time the error occurred.
- The affected URL.
- The output from your
curl -Itest. - Screenshots of the Network tab from your browser developer tools.
- Ask your provider to confirm which HTTP versions (such as HTTP/1.1, HTTP/2, or HTTP/3) are supported on your server and to update the server configuration if necessary.
4. Check Server Logs
- If you have access to your hosting control panel, navigate to the Logs or Metrics section.
- Look for the Error Logs or Apache/NGINX logs.
- Filter the logs by the timestamp you recorded when the 505 error occurred.
- Provide any relevant log entries to your hosting provider to help them identify why the server is rejecting the protocol version.
What Your Hosting Provider Will Do
Your hosting provider is the only party with access to the web server software (such as Apache or NGINX) and the underlying server configuration. They will need to verify that the server supports modern protocol versions and may need to update the server software, enable specific modules, or adjust the protocol negotiation settings. On shared hosting plans, these settings are managed by the provider and cannot be changed by the website owner.
What Not to Do
- Do not attempt to refresh the page, clear your browser cache, or switch devices as a solution. These actions do not affect server protocol support.
- Do not attempt to edit
.htaccess,httpd.conf, ornginx.confto force a specific HTTP protocol version. These files cannot override the server's core protocol capabilities and incorrect edits can take your entire website offline. - Do not pause or disable your CDN to fix a 505 error. While CDNs can cause other issues, a 505 error indicates a protocol mismatch at the origin server level.
Still Having Issues?
💻 Open a Ticket