Cloudflare is a United States-based company that specializes in providing Internet security and other online services. Some of these services include DDoS protection, CDN and domain name services. It is a very popular alternative and is used by many people. Recently, there have been many reports where users are experiencing »Error 524» on their servers.
Error 524 en Cloudflare
What causes the “Error 524” on Cloudflare servers?
After receiving numerous reports from various users, we decided to investigate the problem and came up with a set of solutions to completely fix it. At the same time, We investigate the reasons why it is activated and list them as follows.
-
Long-running procedure: the error 524 indicates that Cloudflare was able to determine a TCP connection to the origin, but the origin was unable to respond with an HTTP before the time limit was reached. This means that there is no problem with Cloudflare and that you can make a connection to the origin, but the origin is exceeding the connection response time limit. Cloudflare just wait 100 seconds before this error is triggered, so, if the procedure you are running is longer than the one triggered with this error.
-
Overload: in some cases, the server may be overloaded and limited by hardware. Higher-than-normal CPU usage on the server can cause increased load times. This, at the same time, it will limit the server's ability to complete a task and this error can be triggered.
Now that you have a basic understanding of the nature of the problem, we will look for solutions. Make sure to apply them in the specific order in which they are presented to avoid conflicts.
Solution 1: check your resources
If this error is triggered on your server, it is recommended that you check the server resources for high usage. Resource usage may be higher than normal due to this error occurring. It is recommended that you increase the hardware capabilities of the server or limit the processes that run on it..
Solution 2: Move to subdomain
If you regularly run processes that take longer than 100 seconds to complete, you can try moving these processes to a non-proxy subdomain of the Cloudflare DNS app. In this way, the limitation of 100 seconds will no longer apply to the procedure and will load regularly.
Note: It is also recommended to disable any VPS software and test the Railgun configuration.
