Knowledgebase

Error 524 occurs when Cloudflare successfully connects to your server, but the server takes too long to respond. This can happen due to server overload, long-running processes, or even potential security threats like DDoS attacks. Here’s how you can troubleshoot and resolve Error 524.

Step 1: Check Server Resources

1. CPU and Memory Usage: Ensure that your server has sufficient resources to handle incoming requests. High CPU or memory usage may cause delays, resulting in timeouts.
2. Disk Space: Make sure you have enough disk space, especially if your website relies on databases or temporary files.
3. Connection Limits: Some web servers have connection limits. Check if these are causing bottlenecks by limiting concurrent connections.

Step 2: Enable Cloudflare's "I'm Under Attack" Mode (If Necessary)

If you suspect your site may be under a Distributed Denial of Service (DDoS) attack:

1. Activate "I'm Under Attack" Mode in Cloudflare: This mode applies additional security checks for incoming requests, helping to mitigate DDoS attacks and other malicious activity. Learn more on Cloudflare's support page.
2. Website Security Check: Follow our guide on what to do if your website was hacked for more security steps, including malware scans and password updates.

Step 3: Optimize Long-Running Processes

1. Break Down Tasks: For processes that require significant time, consider breaking them into smaller, more manageable tasks.
2. Background Processing: If your server performs heavy tasks like bulk email, file processing, or database updates, use background jobs or task queues instead of handling them in real-time.

Step 4: Adjust Server Timeout Settings

1. Increase Timeout Limits: Some servers and applications have configurable timeout settings. Increase these limits in your server configuration or application settings.
   • PHP Script Timeout: Increase the max_execution_time in your php.ini file:
      

     max_execution_time = 300
   • Web Server Timeout:
     • Apache: Adjust the Timeout directive in your httpd.conf.
     • NGINX: Modify proxy_read_timeout and proxy_connect_timeout settings in nginx.conf.

Step 5: Monitor Server Performance

1. Logs: Check your server logs for any errors or warnings related to performance.
2. Traffic Patterns: Use Cloudflare Analytics to identify if certain pages, times of day, or traffic spikes correlate with Error 524 events.

Step 6: Review Firewall and Security Settings

1. Whitelist Cloudflare’s IPs: Ensure that Cloudflare IP ranges are whitelisted in your firewall configuration.
2. Optimize Security Settings: If your firewall has strict security settings, it might be slowing down requests. Consider lowering these settings temporarily to test if this reduces timeouts.

Step 7: Contact Your Hosting Provider

If you've tried the steps above and are still encountering Error 524:

1. Request Assistance: Your hosting provider may be able to identify bottlenecks or other issues with your server.
2. Upgrade Hosting Plan: If your site has grown in traffic or complexity, consider upgrading to a plan with higher resources.

Conclusion

Error 524 generally points to a server-side issue. By optimizing your server resources, enabling appropriate security measures, and configuring timeouts, you can minimize occurrences of this error and keep your site running smoothly.

If you need further assistance, please reach out to our support team.