How to Fix 504 Gateway Timeout on WordPress with Cloudflare SSL: 5 Expert Solutions & Quick Diagnostics

Deploying Cloudflare as a reverse proxy for a WordPress site is common practice for performance and security, yet the 504 Gateway Timeout error can disrupt user experience and search rankings. This guide walks you through a data‑driven, step‑by‑step blueprint for diagnosing and resolving the timeout, covering five tested solutions—complete with benchmark tables, actionable code snippets, and preventative strategies.

⚡ 30‑Second Quick Resolution

Turn the Cloudflare SSL proxy to “Full (Strict)”, clear all Raft or page caches, and then refresh the entire wp‑content folder. If the timeout persists, proceed to the deeper methods listed below.

Understanding the Problem: Architecture & Core Benefits

A 504 error means Cloudflare was unable to receive a timely response from your WordPress origin server. In a typical Cloudflare‑enabled environment, the traffic flow is:

1. Client → Cloudflare CDN (cached or proxied).
2. Cloudflare forwards request to origin.example.com via HTTPS (SSL).
3. WordPress processes the request, often invoking multiple plugins, database queries, or external API calls.
4. Response is returned to Cloudflare, then cached if applicable.

When step 3 stalls beyond Cloudflare’s served‑by‑origin timeout (default 100 s), a 504 surfaces, regardless of whether the cache was bypassed. The root cause usually clusters around one of three domains:

• Origin server overload – CPU, memory, or I/O bottlenecks.
• Misconfigured HTTPS connection – incompatible cipher suites or mismatched certificates.
• Plugin or theme inefficiencies – poorly written code, unoptimized heavy queries, or third‑party scripts that delay response time.

Grasping this diagnostic map allows you to validate each cause efficiently.

1️⃣ Quick Configuration & Cache Reset

This first method operates at the Cloudflare and WordPress configuration levels. It addresses common misconfigurations that trigger 504s while preserving your CDN benefits.

Step 1: Verify SSL mode and Certificate

1. Log into Cloudflare → SSL/TLS tab.
2. Set SSL to “Full (Strict)”. This ensures the origin certificate is valid and chains up to a recognized CA.
3. Under Edge Certificates, confirm TLS 1.3 is enabled for optimal handshake speed.

Step 2: Flush Cloudflare Cache

1. Navigate to Caching → Purge Everything.
2. Ensure Cache Level is set to BYPASS temporarily if you suspect stale content.

Step 3: Clear WordPress Object Cache

These commands can be executed via SSH, WP-CLI, or your hosting control panel’s terminal.

Step 4: Increase WordPress Maximum Execution Time

define('WP_MAX_MEMORY_LIMIT', '256M');
define('WP_MEMORY_LIMIT', '256M');
set_time_limit(300); // 5 minutes

Add the above to your wp‑config.php if you control the file. This allows long‑running scripts to finish without hitting the PHP max execution limit.

2️⃣ Command‑Line & Configuration File Modification

Method two delves into server‑level adjustments that can eliminate timeout triggers at the network layer. These steps require shell access and administrative rights.

Step 1: Adjust Nginx or Apache Timeout Settings

If you use Nginx:

Nginx:
worker_processes auto;
worker_connections 1024;
send_timeout 120s;
proxy_connect_timeout 60s;
proxy_read_timeout 120s;
proxy_send_timeout 120s;

If

📌 บทความน่าสนใจที่เกี่ยวข้อง:

• ไทย vs เวียดนาม: เจาะกลยุทธ์ก่อนเกมชิงแชมป์ SEA V Cup 2026
• Suno AI v6 มาแล้ว! 6 ฟีเจอร์ใหม่ที่ครีเอเตอร์ต้องรู้ พร้อมเช็ก Free, Commercial Use
• การพัฒนาตัวเองและทักษะการทำงาน [พัฒนาตัวเอง, ทักษะการทำงาน, ความก้าวหน้าในอาชีพ]
• เทรนด์ AI ล่าสุดที่กำลังเปลี่ยนโลกการทำงาน [เทรนด์ AI, การทำงาน, เทคโนโลยี]