Error 522 is an HTTP status code that shows there’s a connection problem because the server isn’t responding. This often happens with services like Cloudflare, which speeds up and protects websites. The error means that Cloudflare tried to connect to your site but didn’t get a reply in time. It’s also called a "connection timeout" error.
This article explains what the 522 error is, why it happens, and how to fix it.
What is a 522 Error?
Cloudflare is a service that helps make websites faster and more secure. But if the website’s server doesn’t reply in time, users will see a 522 error with a message like "Connection timed out" or "Cloudflare error 522."
This error happens when the communication between Cloudflare and the server (called the TCP handshake) fails. The process looks like this:
- Cloudflare sends a connection request to the website’s server.
- The server should reply to confirm the request.
- Cloudflare then sends a final message to complete the connection.
If the server doesn’t reply fast enough, Cloudflare can’t complete the process and shows a 522 error, meaning the connection failed because it took too long.
What Causes a 522 Error?
A failed connection attempt, known as an unsuccessful handshake, is the main reason for a 522 error. This slow response from the server can happen for several reasons:
Slow or unstable internet: Problems with internet settings, the client's Internet Service Provider (ISP), or security software like firewalls can cause connection issues.
Server overload: If the server is too busy, under maintenance, or being updated, it may not respond quickly.
Offline server: If the server is down or misconfigured, it can’t complete the connection.
SSL certificate problems: If the SSL certificate is expired, invalid, or untrusted, a secure connection won’t be made.
Routing issues: If the traffic is sent through a bad or crowded network, the connection can fail.
How to Fix a 522 Error?
To start fixing a 522 error, first check if the website is down for everyone and look at the Cloudflare system status page. If the website is working but the error continues, here are steps that can help website owners fix the issue:
Step 1: Optimize the Server
The server hosting the website is responsible for delivering content to visitors. If it’s overloaded, it can cause the 522 error. To fix this:
- Check how much CPU and memory the server is using. If it’s overloaded, consider upgrading to a larger server or adding more resources.
- Use server software like Apache or NGINX to improve performance, allowing it to handle more traffic without slowing down.
- Monitor the network and website traffic to spot issues. Use online tools to track things like page load times and find traffic bottlenecks.
- Optimize database queries to make them run faster.
- Reduce the size of website files, images, and scripts to speed up loading.
- Ensure that the connection between the server and Cloudflare is stable.
- Set up a load balancer correctly to handle traffic spikes.
Step 2: Check Firewall Settings
Sometimes firewalls block traffic from Cloudflare, causing the 522 error. To fix this:
Try accessing the website from a different network or use online tools to check if the website is accessible.
If the website is blocked, it means the firewall is stopping traffic from Cloudflare.
Make sure third-party firewalls are properly configured, and whitelist Cloudflare’s IP addresses so the firewall doesn’t block its traffic.
Step 3: Adjust DNS/IP Settings
Incorrect DNS settings can cause the 522 error. To check and fix Cloudflare’s DNS settings:
Step 1: Open the Cloudflare control panel and select your website.
Step 2: Go to the DNS option on the screen's left side.
Step 3: Check the A Record (Address Record) to make sure the IP addresses on your hosting server and Cloudflare are the same. Different IP addresses can cause the 522 error.
Step 4: If the IP addresses are different, find the wrong A record.
Step 5: Click the Edit link to edit it.
Step 6: Enter the correct IP address in the IPv4 address field.
Step 7: Then click on the Save button to save the changes.
Step 4: Check SSL Certificate Issues
Having a valid SSL certificate helps avoid the 522 error. You can see if a website has a valid certificate by looking for the padlock icon in the browser's address bar.
Use an online SSL Checker tool to check more details about the SSL certificate, such as expiration date or other problems. Look for:
- Expired certificates.
- Problems in the certificate chain (like a missing or incorrect intermediate certificate).
- Certificates that don’t match the website’s domain name.
- Renew or install the correct certificate if needed. Other problems, like weak encryption or incorrect SSL settings, may require editing the SSL configuration file.
Step 5: Enable KeepAlive
KeepAlive is a setting that keeps the connection between a client and a server open for longer, helping improve performance by reducing the need to reconnect. Both Cloudflare and the server use KeepAlive.
Cloudflare uses KeepAlive to keep the connection active for longer, improving speed. If KeepAlive is turned off on the server, a 522 error can happen due to connection issues.
To fix this, you need to enable KeepAlive in the server’s settings by adding:
KeepAlive On
For example, to enable KeepAlive on an Apache server in Ubuntu:
Open the Apache configuration file using a text editor like nano:
# nano /etc/apache2/apache2.conf
Look for the "KeepAlive" line in the file. If it's missing, add:
KeepAlive On
Save and exit the file.
Restart the Apache service to apply the changes:
# systemctl restart apache2
Step 6: Review Cloudflare Configuration
Check the Cloudflare settings to ensure everything is set up correctly. Check DNS, SSL, and firewall settings to find any issues causing the 522 error. Also, make sure the server is properly configured and responding to requests.
Step 7: Turn on Cloudflare's Under Attack Mode
If the 522 error continues after trying the previous steps, you can enable Cloudflare’s Under Attack mode. This feature helps protect against DDoS attacks and reduces the chance of a 522 error by blocking harmful traffic before it reaches your server.
To easily enable Under Attack mode, follow these steps:
Step 1: Log in to your Cloudflare account and choose your website.
Step 2: Go to the left side of the screen and click on the Security option.
Step 3: After that, click on the Settings option.
Step 4: In the Settings window, go to the Security Level and select the "I'm Under Attack!" option from the drop-down list.
Step 5: Once you select it, the changes will be saved automatically, and you will see "I'm Under Attack mode" in the Security Level. This means that I am in attack mode, which is enabled on your website.
Step 8: Contact Cloudflare Support
If the problem still isn’t fixed, contact Cloudflare Support. Go to the Support menu at the top and click Contact Cloudflare.
Cloudflare offers two support options:
Live chat (only for Business and Enterprise accounts).
Support tickets (available for everyone).
Conclusion:
Cloudflare error 522 happens when a server takes too long to respond to a request. Common causes include not enough memory or CPU, a firewall blocking an IP address, or the KeepAlive setting being turned off.
You’ll need server administrator access to fix this problem.
