Buzz
What actions to take when encountering a 522 error on your website
Facing a 522 error on a website? If you're just visiting, there’s little you can do except wait for the issue to be fixed. However, as a website owner, you'll want to resolve this error as quickly as possible. In this article, we’ll cover all the key information about this error code, along with several potential solutions to help get your site up and running again.
Quick Overview of Cloudflare Error Code 522
The 522 error is a Cloudflare-specific HTTP status code, indicating that the connection between Cloudflare and the website’s origin server has timed out. If you’re seeing this error on a website you're visiting, your best bet is to wait for the issue to be resolved. However, if this is happening on your site, there are several quick solutions you can try to fix it.
Actions to Take
Resolving Error Code 522
Check Cloudflare's system status. While it's unlikely that Cloudflare is the cause of the error (since error 522 pertains to the origin server failing to respond), it's still a good idea to verify Cloudflare's system status first. If Cloudflare is experiencing issues, it might be best to wait until they're resolved before attempting troubleshooting, as your site could start functioning again once Cloudflare is back online, and attempting fixes may not be effective if Cloudflare is down.
- You can check Cloudflare's system status here.
Check if your hosting provider is conducting maintenance. If your hosting provider is undergoing maintenance (or facing technical difficulties), your site may be showing error code 522 because the server is unreachable. Unfortunately, the only thing you can do in this situation is wait until the provider resolves the issue.
- Different hosting providers have various methods of communicating maintenance or outages. Visit your host’s website for updates or contact them directly for assistance.
Verify the status of your web server. If there’s no reported outage or maintenance from your hosting provider, you can check your web server manually using a traceroute. If the traceroute reveals an issue or unusual behavior, you can proceed with additional steps to resolve the problem.
- Windows & Linux: In the command-line interface (CLI), run the command $ tracert [URL] (for IPv4) or $ tracert -6 [URL] for IPv6, where [URL] is replaced with your website’s URL.
- Mac: Open the Network Utility application and go to the Traceroute tab. Enter your site’s domain name or IP address in the input field and click the Trace button.
- Be sure to save the results of the traceroute in case your hosting provider or Cloudflare requests this information.
Ensure your hosting provider allows Cloudflare IP addresses. A common cause of a 522 error is the blocking or rate limiting of Cloudflare’s IP addresses. If you can’t manually add the Cloudflare IP, you may need to request that your hosting provider whitelist it.
- It’s possible to make this change directly from your hosting provider’s dashboard or admin panel. If not, try the following:
- Open your site's .htaccess file.
- Add a line saying #DO NOT REMOVE THIS LINE.
- Below that, add a line that says allow from [IP address], replacing [IP address] with your Cloudflare IP.
- Add another line below that saying #DO NOT REMOVE THIS LINE. The lines with “do not remove” should sandwich the “allow from” code with your Cloudflare IP.
Verify your Cloudflare DNS settings. Incorrect Cloudflare DNS settings can lead to the 522 error on your site. To modify these settings, head over to DNS > Records in the Cloudflare dashboard.
- Ensure the A Record IP addresses are consistent between your server and Cloudflare. If you don’t know your server’s A Record IP address, you can find it in your host’s dashboard or admin panel.
- If there’s a mismatch, click Edit next to the affected entry and make the necessary corrections, then click Save.
Activate keepalive on your origin web server. Keepalive (or KeepAlive) is a TCP feature that allows the reuse of the same connection for multiple HTTP requests, preventing the need to open new ones each time. You can enable keepalive in a couple of ways:
- In your web server’s configuration file (if you have access), adjust these lines:
- KeepAlive On
- MaxKeepAliveRequests 50 to 75
- KeepAliveTimeout 1 to 5
- Alternatively, add the following line to your .htaccess file: <ifModule mod_headers.c> Header set Connection keep-alive </ifModule>
Monitor your site’s resource usage. If your site reaches its CPU, RAM, or process limits, it may slow down and cause the 522 error. Every hosting provider displays resource usage differently, but it’s typically found in your dashboard or admin panel. If your resource usage is high, try the following:
- Reduce plugin usage. Excessive plugins can increase the load on your server, leading to a 522 error.
- Optimize your code. Inefficient code, like numerous animations (especially in JavaScript or jQuery), can drain CPU resources and slow down your site.
- Upgrade your hosting plan. If your memory usage consistently hits the limits, consider upgrading your hosting plan. Contact your hosting provider for advice tailored to your site’s needs.
Reach out to your web host if the issue persists. If you continue experiencing a 522 error after trying all the solutions, contact your web host for further assistance. When doing so, explain the steps you've already attempted to avoid repeating troubleshooting steps.
- Cloudflare advises including the following when contacting your web host about a 522 error:
- The specific error code and message
- The time of occurrence (including timezone)
- The URL where the error occurred
- Avoid contacting Cloudflare for 522 errors unless your web host directs you to do so. If you must reach out to Cloudflare support, be prepared with your traceroute results and any relevant logs from your web host’s investigation.
Temporarily disable Cloudflare. If you’re unable to fix the issue and users can’t access your site, consider disabling Cloudflare while you troubleshoot (either independently or with your host’s support). Consult your hosting provider’s documentation for guidance on disabling Cloudflare, as the steps may vary.
- Once you’re ready to use Cloudflare again, consider restarting your Cloudflare account to prevent any potential future issues.
What does error code 522 mean?
Error 522 occurs when a connection to the site times out. This HTTP status code is unique to Cloudflare and can arise in two main scenarios:
- Before a connection is made, the origin server fails to complete the TCP 3-way handshake within 15 seconds.
- Cloudflare will send a SYN packet to the origin server, which should respond with a SYN-ACK. Cloudflare then sends an ACK packet to complete the handshake.
- If the server doesn’t return the SYN/ACK in 15 seconds, the connection will timeout, triggering error 522.
- After the connection is established, the origin server fails to send an ACK to Cloudflare within 90 seconds of a request.
- Once connected, Cloudflare sends periodic GET requests for resources.
- The server must send an ACK to confirm it received the GET request within 90 seconds. If not, the connection times out and Cloudflare displays error 522.
Several factors can lead to error 522. Some common causes include:
- Server overload: If the origin server is overwhelmed with requests, it might fail to respond to Cloudflare in time, resulting in a 522 error.
- Blocked or incorrect IP addresses: A Cloudflare IP address might be blocked by the host, or the origin IP may be incorrectly entered in Cloudflare’s DNS settings.
- Keepalives are disabled: Keepalive is a TCP feature designed to detect dead connections. If it’s disabled, more 522 errors may occur than necessary.
Can a website visitor bypass error 522?
You might be able to bypass error 522 as a visitor. If you’re unable to wait for the site to resolve the issue, there are a few methods you can try to bypass error 522: using a VPN or an alternate domain. Sometimes, regional server issues cause the error, so accessing the site from a different server could help. However, these workarounds are not guaranteed, and you might still face the 522 error.
- Use a VPN with a server located far from your own to connect to the site via another server.
- Try accessing the site through an alternate domain. Note that not all sites have multiple domains, and some might simply redirect to the main domain, which is not the same as having alternate domains.
Waiting for a few minutes could help resolve the 522 error. Although this isn’t exactly a workaround, if the 522 error is caused by server overload, waiting a few minutes might resolve it. After some time, try refreshing the site to check if you can connect. If the issue persists, it may indicate a more complex problem that requires the site owner’s intervention to fix the issue.
