How to Fix 504 Gateway Timeout in Nginx & Apache (Step-by-Step Guide)

By /

The 504 Gateway Timeout error occurs when an upstream server (such as PHP-FPM or Apache) takes too long to process a request and fails to respond within the gateway’s timeout window (Nginx or Cloudflare proxy). To fix it, you need to increase the max_execution_time in PHP, adjust proxy_read_timeout in Nginx configuration, optimize heavy database queries, and ensure your server resources are not running at 100% CPU utilization.

WordPress administration me sabse zyada frustrating errors me se ek 504 Gateway Timeout hai. Jab aap apni website ka koi heavy page load karte hain, WooCommerce checkout complete karte hain, ya WordPress dashboard me bulk plugin update run karte hain, toh browser par achanak error pop up hota hai:

504 Gateway Timeout

Jaisa ki humne apne TTFB Optimization Guide aur E-Commerce Server Sizing Guide me discuss kiya tha, yeh error tab aata hai jab server ka upstream process request complete karne me standard time limit se zyada samay leta hai.

Is technical troubleshooting guide me hum Nginx aur Apache dono servers ke liye 504 error ke root causes ko analyze karenge aur step-by-step resolution command execute karenge.

Understanding the Request Flow: Where Does a 504 Error Happen?

Standard web architecture me request ka flow kuch is tarah hota hai:

[Visitor Browser] 
       │
       ▼
[Reverse Proxy / Nginx / Cloudflare] (Times out if backend doesn't reply in 60s)
       │
       ▼
[Backend Server / Apache / PHP-FPM] (Stuck processing heavy SQL query or script)
  1. The Gateway (Nginx / Cloudflare): Yeh front-facing server client request ko accept karta hai aur backend ko forward karta hai. Iska ek strict timer (e.g., 60 seconds) hota hai.
  2. The Upstream (Apache / PHP-FPM / MySQL): Agar backend PHP script ya database query ko execute hone me 60 second se zyada lagte hain, toh Nginx connection drop kar deta hai aur user ko 504 Gateway Timeout dikha deta hai.

Step 1: Increase PHP Execution Time and Memory Limits

Sabse common wajah hoti hai PHP script ka execution time limit cross ho jana. Isko fix karne ke liye cPanel ya server terminal ke zariye limits badhayein:

  1. cPanel me MultiPHP INI Editor ya wp-config.php file open karein.
  2. Apne server par yeh limits update karein:

Ini, TOML

max_execution_time = 300
max_input_time = 300
memory_limit = 512M

Isse PHP script ko heavy background operations (jaise XML sitemap generation ya bulk product import) ke liye sufficient processing window mil jayegi.

Step 2: Fixing 504 Timeout on Nginx Web Servers

Agar aapka server Nginx ya Nginx + Apache proxy combination par chal raha hai, toh aapko Nginx configuration files me timeout values increase karni hongi.

Apne server terminal par nginx.conf ya virtual host file open karein (/etc/nginx/conf.d/ ya /etc/nginx/sites-available/):

Nginx

http {
    proxy_connect_timeout 300s;
    proxy_send_timeout 300s;
    proxy_read_timeout 300s;
    fastcgi_send_timeout 300s;
    fastcgi_read_timeout 300s;
}
  • proxy_read_timeout: Nginx ko batata hai ki upstream server se response aane ke liye kitna wait karna hai. Default 60s se badha kar 300s kar dein.
  • Configuration save karne ke baad Nginx syntax check karke reload karein:

Bash

sudo nginx -t
sudo systemctl reload nginx

Step 3: Fixing 504 Timeout on Apache & PHP-FPM Servers

Agar aapka server pure Apache ya Apache + PHP-FPM par configured hai, toh timeout limits Apache configuration (httpd.conf ya apache2.conf) aur PHP-FPM pool (www.conf) me update karni hongi:

  1. Apache Timeout Directive:

Apache

Timeout 300
ProxyTimeout 300
  1. PHP-FPM Request Termination (/etc/php/8.x/fpm/pool.d/www.conf):

Ini, TOML

request_terminate_timeout = 300

Iske baad Apache aur PHP-FPM service restart karein:

Bash

sudo systemctl restart apache2
sudo systemctl restart php8.x-fpm

Step 4: Check for Database Locks and Slow Queries

Kayi baar 504 error server timeout ki wajah se nahi, balki database table lock hone ki wajah se aata hai.

  • Transient Clean-up: wp_options table me bloated autoloaded data ya stuck database transients query execution ko freeze kar dete hain.
  • Query Monitor: Staging site par Query Monitor plugin install karke check karein ki kaunsi plugin query database ko hang kar rahi hai.

Enterprise Infrastructure Stability with AGM Web Hosting

Agar aapko baar-baar server-level timeout errors face karne padte hain, toh shared hosting ke tight resource constraints iski main root cause hote hain.

  • Dedicated vCPU & RAM: AGM Web Hosting ke cloud plans me guaranteed resources milte hain jo heavy PHP scripts ko bina bottleneck ke execute karte hain.
  • Optimized LiteSpeed Stack: Built-in server level caching aur pre-configured timeout parameters.

Apne business ko stable aur high-performance hosting par migrate karne ke liye visit karein AGM Web Hosting India.

Frequently Asked Questions (MEGA FAQ)

1. 504 Gateway Timeout aur 504 Bad Gateway me kya antar hai?

Dono lagbhag same gateway communication issues hain. 504 tab aata hai jab upstream server time limit ke andar reply nahi karta, jabki 502 tab aata hai jab gateway ko invalid response milta hai.

2. Kya Cloudflare ki wajah se 504 error aa sakta hai?

Haan! Agar aapki site par Cloudflare proxy (orange cloud) active hai aur aapka origin server request process hone me 100 seconds se zyada leta hai, toh Cloudflare khud 504 Gateway Timeout throw kar deta hai.

3. WooCommerce checkout ke waqt 504 error kyu aata hai?

Payment gateway APIs (jaise Razorpay, Stripe) ke webhook callhone ke dauran agar server response delay hota hai, toh checkout page par 504 error trigger ho jata hai.

4. Nginx timeout badhane ke baad bhi error theek kyu nahi ho raha?

Timeout badhana sirf symptom fix karta hai. Agar koi infinite loop ya broken database query hai, toh wo 300 second baad fir se timeout ho jayegi. Root cause identify karna zaroori hai.

5. Kya .htaccess file se 504 error fix kiya ja sakta hai?

Apache servers par .htaccess me php_value max_execution_time 300 add karke execution time badhaya ja sakta hai, lekin Nginx par yeh file kaam nahi karti.

6. WP-Cron jobs ki wajah se 504 error aa sakta hai?

Haan, agar background cron tasks ek sath heavy database queries run karte hain, toh server temporarily freeze ho sakta hai. System cron (crontab) set karna behtar hota hai.

7. Server CPU utilization 100% hone par kya karein?

top ya htop command run karke check karein ki konsa process (apache, nginx, mysql) CPU consume kar raha hai, aur zaroorat padne par server resources scale karein.

8. Kya caching plugin 504 error ko rokh sakta hai?

Haan, page caching static HTML serve karti hai jisse PHP-FPM execute hi nahi hota, aur server par load zero ho jata hai.

9. Log files kahan milti hain error debug karne ke liye?

Nginx error logs /var/log/nginx/error.log par aur Apache logs /var/log/apache2/error.log par milte hain.

10. Kya Free SSL certificate expire hone par 504 error aa sakta hai?

Nahi, SSL expiry se SSL handshake error (ERR_CERT_DATE_INVALID) aata hai, 504 timeout error nahi.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top