{"id":2670,"date":"2026-08-11T10:40:05","date_gmt":"2026-08-11T07:40:05","guid":{"rendered":"https:\/\/saviorhost.com\/blog\/504-gateway-timeout-hatasi-cozum\/"},"modified":"2026-08-11T10:41:10","modified_gmt":"2026-08-11T07:41:10","slug":"504-gateway-timeout-hatasi-cozum","status":"publish","type":"post","link":"https:\/\/saviorhost.com\/blog\/504-gateway-timeout-hatasi-cozum\/","title":{"rendered":"WordPress 504 Gateway Timeout Hatas\u0131 ve Kesin \u00c7\u00f6z\u00fcmleri"},"content":{"rendered":"<p>WordPress 504 Gateway Timeout Hatas\u0131: 2026&#8217;da Sitenizi Kurtaracak 11 Kesin \u00c7\u00f6z\u00fcm<\/p>\n<p>Gece yar\u0131s\u0131. Telefonunuza bildirim geliyor: &#8220;Siteniz \u00e7\u00f6kt\u00fc!&#8221; Hemen taray\u0131c\u0131y\u0131 a\u00e7\u0131p adresi yaz\u0131yorsunuz. Ve kar\u015f\u0131n\u0131zda o me\u015fum ifade: <strong>504 gateway timeout hatas\u0131<\/strong>. Kalp at\u0131\u015f\u0131n\u0131z h\u0131zlan\u0131yor, panikle <strong>hosting<\/strong> deste\u011fine yazmaya ba\u015fl\u0131yorsunuz. Ama ya onlar da size &#8220;log&#8217;lara bak\u0131p d\u00f6nece\u011fiz&#8221; diyorsa? Ya d\u00f6nmezler de sat\u0131\u015flar\u0131n\u0131z, ziyaret\u00e7ileriniz, reklam b\u00fct\u00e7eniz dakikalar i\u00e7inde eriyip giderse?<\/p>\n<p>Ge\u00e7ti\u011fimiz y\u0131l bir e-ticaret m\u00fc\u015fterimiz tam da bu senaryoyu ya\u015fad\u0131. Kampanya d\u00f6neminde ya\u015fanan 504 hatas\u0131 y\u00fcz\u00fcnden 4 saat boyunca sat\u0131\u015f yapamad\u0131. Sorunu \u00e7\u00f6zd\u00fc\u011f\u00fcm\u00fczde fark ettik ki mesele yaln\u0131zca bir eklenti \u00e7ak\u0131\u015fmas\u0131 de\u011fil, ayn\u0131 anda 3 farkl\u0131 fakt\u00f6r\u00fcn \u00fcst \u00fcste binmesiydi. O g\u00fcn \u00f6\u011frendik ki <strong>504 gateway timeout hatas\u0131<\/strong>, neredeyse hi\u00e7bir zaman tek bir nedenden kaynaklanm\u0131yor.<\/p>\n<p>Peki bu hata tam olarak ne? Nas\u0131l \u00e7\u00f6z\u00fcl\u00fcr? Ve en \u00f6nemlisi, bir daha asla kar\u015f\u0131n\u0131za \u00e7\u0131kmamas\u0131 i\u00e7in neler yapmal\u0131s\u0131n\u0131z? \u0130\u015fte 2026 y\u0131l\u0131nda ge\u00e7erlili\u011fini kan\u0131tlam\u0131\u015f, ad\u0131m ad\u0131m uygulayabilece\u011finiz 11 kesin \u00e7\u00f6z\u00fcm.<\/p>\n<div class=\"key-takeaways\" style=\"background:#f0f9ff;border-left:4px solid #0ea5e9;padding:20px;margin:20px 0;border-radius:8px\">\n<p><h3 id=\"%f0%9f%93%8b-onemli-noktalar\">\ud83d\udccb \u00d6nemli Noktalar<\/h3>\n<\/p>\n<ul>\n<li><strong>504 gateway timeout hatas\u0131<\/strong>, sunucunun bir \u00fcst proxy&#8217;den (Nginx, Cloudflare, CDN) zaman\u0131nda yan\u0131t alamamas\u0131d\u0131r.<\/li>\n<li>Sorunun kayna\u011f\u0131 %70 oran\u0131nda sunucu taraf\u0131ndad\u0131r; eklenti, tema veya PHP ayarlar\u0131 tetikleyici olabilir.<\/li>\n<li>Cloudflare kullan\u0131yorsan\u0131z 524 hatas\u0131 ile 504 hatas\u0131n\u0131 ay\u0131rt etmeniz gerekir \u2014 \u00e7\u00f6z\u00fcmleri farkl\u0131d\u0131r.<\/li>\n<li>PHP-FPM timeout, veritaban\u0131 ba\u011flant\u0131 sorunlar\u0131 ve wp-cron \u00e7ak\u0131\u015fmalar\u0131 en s\u0131k g\u00f6r\u00fclen 3 nedendir.<\/li>\n<li>Bu rehberdeki 11 y\u00f6ntemden en az 3&#8217;\u00fcn\u00fc ayn\u0131 anda uygulamak, kal\u0131c\u0131 \u00e7\u00f6z\u00fcm i\u00e7in \u015fartt\u0131r.<\/li>\n<\/ul>\n<\/div>\n<div class=\"wp-block-rank-math-toc-block table-of-contents\" role=\"navigation\" aria-label=\"\u0130\u00e7indekiler\">\n<p><figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"768\" src=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/08\/Icindekiler-4.jpg\" class=\"aligncenter sm-ai-image\" alt=\"\u0130\u00e7indekiler\" loading=\"lazy\" \/><\/figure>\n<h2 id=\"icindekiler\">\u0130\u00e7indekiler<\/h2>\n<\/p>\n<ul>\n<li><a href=\"#504-gateway-timeout-nedir\">504 Gateway Timeout Hatas\u0131 Tam Olarak Nedir?<\/a><\/li>\n<li><a href=\"#nedenleri\">WordPress&#8217;te 504 Hatas\u0131n\u0131n 7 Temel Nedeni<\/a><\/li>\n<li><a href=\"#hizli-kontrol\">\u00c7\u00f6z\u00fcme Ba\u015flamadan \u00d6nce Yapman\u0131z Gereken 3 H\u0131zl\u0131 Kontrol<\/a><\/li>\n<li><a href=\"#hosting-kaynakli\">Hosting Kaynakl\u0131 504 Hatalar\u0131n\u0131 Tespit ve \u00c7\u00f6z\u00fcm<\/a><\/li>\n<li><a href=\"#php-fpm\">PHP-FPM Timeout Ayarlar\u0131n\u0131 Optimize Etme<\/a><\/li>\n<li><a href=\"#nginx-apache\">Nginx ve Apache Proxy Ayarlar\u0131n\u0131 D\u00fczenleme<\/a><\/li>\n<li><a href=\"#cloudflare-cdn\">Cloudflare ve CDN Kaynakl\u0131 504 Hatalar\u0131n\u0131 Giderme<\/a><\/li>\n<li><a href=\"#wordpress-eklenti\">WordPress Eklenti ve Tema Kaynakl\u0131 Timeout Sorunlar\u0131<\/a><\/li>\n<li><a href=\"#veritabani\">Veritaban\u0131 Ba\u011flant\u0131 Timeout&#8217;lar\u0131n\u0131 Kal\u0131c\u0131 Olarak \u00c7\u00f6zme<\/a><\/li>\n<li><a href=\"#wp-cron\">WP-Cron ve Zamanlanm\u0131\u015f G\u00f6rev \u00c7ak\u0131\u015fmalar\u0131<\/a><\/li>\n<li><a href=\"#kalici-cozum\">504 Hatas\u0131n\u0131 Tamamen \u00d6nlemek \u0130\u00e7in 5 Kal\u0131c\u0131 Strateji<\/a><\/li>\n<li><a href=\"#sonuc\">Sonu\u00e7: Sitenizi Gelece\u011fe Haz\u0131rlay\u0131n<\/a><\/li>\n<li><a href=\"#faq\">S\u0131k\u00e7a Sorulan Sorular<\/a><\/li>\n<\/ul>\n<\/div>\n<p><figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"768\" src=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/08\/504-Gateway-Timeout-Hatasi-Tam-Olarak-Nedir.jpg\" class=\"aligncenter sm-ai-image\" alt=\"504 Gateway Timeout Hatas\u0131 Tam Olarak Nedir?\" loading=\"lazy\" \/><\/figure>\n<h2 id=\"504-gateway-timeout-nedir\">504 Gateway Timeout Hatas\u0131 Tam Olarak Nedir?<\/h2>\n<figure class=\"wp-block-image size-large sm-inline-image\"><img decoding=\"async\" src=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/08\/Bir-web-tarayici-penceresinde-gorunen-504-Gate-1786434009.jpg\" alt=\"Bir web taray\u0131c\u0131 penceresinde g\u00f6r\u00fcnen 504 Gateway Timeout hata mesaj\u0131. Ekran\u0131n \u00fcst k\u0131sm\u0131nda b\u00fcy\u00fck puntolarla &quot;504 Gateway Timeout&quot; yaz\u0131yor, alt\u0131nda &quot;nginx&quot; ibaresi g\u00f6r\u00fcn\u00fcyor. Arka planda soluk bir WordPress y\u00f6netici paneli sil\u00fceti var. Renk paleti: k\u0131rm\u0131z\u0131 ve gri tonlar\u0131, endi\u015fe hissi veren bir kompozisyon. Geni\u015f ekran, minimalist tasar\u0131m.\" loading=\"lazy\" \/><\/figure>\n<\/p>\n<p><strong>504 gateway timeout hatas\u0131<\/strong>, web d\u00fcnyas\u0131n\u0131n en can s\u0131k\u0131c\u0131 HTTP durum kodlar\u0131ndan biridir. Teknik olarak ifade etmek gerekirse: Bir sunucu (genellikle Nginx, Apache veya Cloudflare gibi bir proxy\/CDN), upstream olarak adland\u0131r\u0131lan bir \u00fcst sunucudan belirli bir s\u00fcre i\u00e7inde yan\u0131t alamad\u0131\u011f\u0131nda bu hatay\u0131 d\u00f6nd\u00fcr\u00fcr.<\/p>\n<p>Hadi daha basit anlatal\u0131m. WordPress sitenizi bir restoran olarak d\u00fc\u015f\u00fcn\u00fcn. Garson (proxy sunucu) sipari\u015fi mutfa\u011fa (web sunucunuza) iletiyor. Ama mutfaktan 60 saniye boyunca cevap gelmezse, garson m\u00fc\u015fteriye d\u00f6n\u00fcp &#8220;kusura bakmay\u0131n, sipari\u015finiz yeti\u015fmeyecek&#8221; diyor. \u0130\u015fte 504 hatas\u0131 tam olarak bu.<\/p>\n<p><p style=\"background:#fef9e7;border-left:4px solid #f59e0b;padding:15px;margin:20px 0;border-radius:6px\"><strong>\u26a1 Kritik Ayr\u0131m:<\/strong> 504 hatas\u0131 ile <a href=\"https:\/\/saviorhost.com\/blog\/502-bad-gateway-hatasi-cozum\/\" target=\"_blank\">502 bad gateway hatas\u0131<\/a> s\u0131kl\u0131kla kar\u0131\u015ft\u0131r\u0131l\u0131r. 502, proxy sunucunun upstream&#8217;den ge\u00e7ersiz\/bozuk bir yan\u0131t ald\u0131\u011f\u0131 anlam\u0131na gelir. 504 ise hi\u00e7 yan\u0131t alamad\u0131\u011f\u0131 anlam\u0131na gelir. Yani 502 &#8220;bozuk cevap&#8221;, 504 &#8220;cevap yok&#8221; demektir.<\/p>\n<\/p>\n<p><figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"768\" src=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/08\/WordPresste-504-Hatasinin-7-Temel-Nedeni.jpg\" class=\"aligncenter sm-ai-image\" alt=\"WordPress&apos;te 504 Hatas\u0131n\u0131n 7 Temel Nedeni\" loading=\"lazy\" \/><\/figure>\n<h2 id=\"nedenleri\">WordPress&#8217;te 504 Hatas\u0131n\u0131n 7 Temel Nedeni<\/h2>\n<figure class=\"wp-block-image size-large sm-inline-image\"><img decoding=\"async\" src=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/08\/WordPress-yonetici-panelinde-eklentiler-sayfasin-1786434015.jpg\" alt=\"WordPress y\u00f6netici panelinde eklentiler sayfas\u0131n\u0131n g\u00f6r\u00fcn\u00fcm\u00fc. Ekranda onlarca eklenti listelenmi\u015f, baz\u0131lar\u0131n\u0131n yan\u0131nda turuncu ve k\u0131rm\u0131z\u0131 uyar\u0131 ikonlar\u0131 var. Sol \u00fcstte WordPress logosu, sa\u011fda kaynak kullan\u0131m grafi\u011fi tavan yapm\u0131\u015f durumda. Koyu mod aray\u00fcz, modern dashboard tasar\u0131m\u0131.\" loading=\"lazy\" \/><\/figure>\n<\/p>\n<p>WordPress \u00f6zelinde konu\u015fursak, <strong>504 gateway timeout hatas\u0131<\/strong> genellikle \u015fu 7 nedenden kaynaklan\u0131r. Bunlar\u0131 bilmek, sorunu te\u015fhis etme s\u00fcrenizi %80 k\u0131salt\u0131r.<\/p>\n<p><h3 id=\"1-php-fpm-workerlarinin-tukenmesi\">1. PHP-FPM Worker&#8217;lar\u0131n\u0131n T\u00fckenmesi<\/h3>\n<\/p>\n<p>WordPress, PHP tabanl\u0131 bir sistemdir. Her ziyaret\u00e7i iste\u011fi bir PHP worker&#8217;\u0131 taraf\u0131ndan i\u015flenir. E\u011fer worker havuzunuzdaki t\u00fcm i\u015f\u00e7iler me\u015fgulse, yeni gelen istekler kuyrukta bekler. Bekleme s\u00fcresi proxy timeout de\u011ferini a\u015ft\u0131\u011f\u0131nda \u2014 pat! \u2014 504 hatas\u0131.<\/p>\n<p>2026 itibar\u0131yla yap\u0131lan testlerde, 4 GB RAM&#8217;e sahip bir sunucuda optimize edilmemi\u015f bir WordPress sitesi, sadece 25 e\u015fzamanl\u0131 ziyaret\u00e7ide PHP-FPM worker&#8217;lar\u0131n\u0131 t\u00fcketebiliyor (Kaynak: Kinsta Performans Raporu, 2025).<\/p>\n<p><h3 id=\"2-uzun-calisan-veritabani-sorgulari\">2. Uzun \u00c7al\u0131\u015fan Veritaban\u0131 Sorgular\u0131<\/h3>\n<\/p>\n<p>WooCommerce gibi a\u011f\u0131r eklentiler, \u00f6zellikle 50.000+ sipari\u015fi olan sitelerde, baz\u0131 veritaban\u0131 sorgular\u0131n\u0131n 10-15 saniye s\u00fcrmesine neden olabilir. Bu s\u00fcre proxy timeout&#8217;unu a\u015farsa 504 ka\u00e7\u0131n\u0131lmazd\u0131r. \u00d6zellikle <code>wp_postmeta<\/code> tablosunda indekslenmemi\u015f sorgular bu sorunun ba\u015fl\u0131ca tetikleyicisidir.<\/p>\n<p><h3 id=\"3-harici-api-baglantilarinin-tikanmasi\">3. Harici API Ba\u011flant\u0131lar\u0131n\u0131n T\u0131kanmas\u0131<\/h3>\n<\/p>\n<p>WordPress eklentilerinizin \u00e7o\u011fu harici servislere ba\u011flan\u0131r: \u00f6deme ge\u00e7itleri, e-posta servisleri, analitik ara\u00e7lar\u0131, CDN&#8217;ler. Bu servislerden herhangi biri yan\u0131t vermezse, PHP i\u015flemi onu beklerken timeout&#8217;a girer. \u00d6zellikle cURL \u00e7a\u011fr\u0131lar\u0131nda timeout ayar\u0131 yap\u0131lmam\u0131\u015f eklentiler bu konuda ba\u015f belas\u0131d\u0131r.<\/p>\n<p><h3 id=\"4-wp-cron-phpnin-kontrolden-cikmasi\">4. wp-cron.php&#8217;nin Kontrolden \u00c7\u0131kmas\u0131<\/h3>\n<\/p>\n<p>WordPress&#8217;in yerle\u015fik cron sistemi, her sayfa y\u00fcklemesinde tetiklenir. E\u011fer birikmi\u015f 50+ cron g\u00f6revi varsa ve bunlar ayn\u0131 anda \u00e7al\u0131\u015fmaya kalkarsa, sunucu kaynaklar\u0131n\u0131 s\u00f6m\u00fcrerek 504&#8217;e davetiye \u00e7\u0131kar\u0131r.<\/p>\n<p><h3 id=\"5-nginx-apache-proxy-buffer-ayarlarinin-yetersizligi\">5. Nginx\/Apache Proxy Buffer Ayarlar\u0131n\u0131n Yetersizli\u011fi<\/h3>\n<\/p>\n<p>\u00d6zellikle Nginx kullanan sunucularda, <code>proxy<em>read<\/em>timeout<\/code> ve <code>fastcgi<em>read<\/em>timeout<\/code> de\u011ferlerinin varsay\u0131lan (genellikle 30-60 saniye) b\u0131rak\u0131lmas\u0131, yo\u011fun i\u015flem yapan sayfalarda timeout&#8217;a neden olur.<\/p>\n<p><h3 id=\"6-cloudflare-cdn-ile-origin-sunucu-arasindaki-kopukluk\">6. Cloudflare\/CDN ile Origin Sunucu Aras\u0131ndaki Kopukluk<\/h3>\n<\/p>\n<p>Cloudflare&#8217;\u0131n origin sunucunuza ba\u011flanamamas\u0131 veya ba\u011flant\u0131n\u0131n \u00e7ok yava\u015f olmas\u0131 durumunda, Cloudflare 524 (kendi 504 varyant\u0131) hatas\u0131 d\u00f6nd\u00fcr\u00fcr. Bu genellikle DNS yanl\u0131\u015f yap\u0131land\u0131rmas\u0131 veya origin sunucudaki g\u00fcvenlik duvar\u0131 kurallar\u0131ndan kaynaklan\u0131r.<\/p>\n<p><h3 id=\"7-kaynak-tuketen-eklenti-veya-tema-scriptleri\">7. Kaynak T\u00fcketen Eklenti veya Tema Scriptleri<\/h3>\n<\/p>\n<p>Baz\u0131 tema ve eklentiler, \u00f6zellikle sayfa kurucular (Elementor, Divi, WPBakery), admin-ajax.php \u00fczerinden s\u00fcrekli istek yapar. Bu istekler arka planda PHP worker&#8217;lar\u0131n\u0131 me\u015fgul eder. Ayn\u0131 anda bir de yo\u011fun trafik gelirse, worker havuzu t\u00fckenir.<\/p>\n<p><figure class=\"wp-block-image size-large\"><img decoding=\"async\" width=\"1024\" height=\"768\" src=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/08\/Cozume-Baslamadan-Once-Yapmaniz-Gereken-3-Hizli-Kontrol.jpg\" class=\"aligncenter sm-ai-image\" alt=\"\u00c7\u00f6z\u00fcme Ba\u015flamadan \u00d6nce Yapman\u0131z Gereken 3 H\u0131zl\u0131 Kontrol\" loading=\"lazy\" \/><\/figure>\n<h2 id=\"hizli-kontrol\">\u00c7\u00f6z\u00fcme Ba\u015flamadan \u00d6nce Yapman\u0131z Gereken 3 H\u0131zl\u0131 Kontrol<\/h2>\n<figure class=\"wp-block-image size-large sm-inline-image\"><img decoding=\"async\" src=\"https:\/\/saviorhost.com\/blog\/wp-content\/uploads\/2026\/08\/Bir-sunucu-kontrol-panelinde-KeyHelp-PHP-FPM-aya-1786434020.jpg\" alt=\"Bir sunucu kontrol panelinde (KeyHelp) PHP-FPM ayarlar\u0131n\u0131n yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131 ekran. Ekranda pm.max_children, pm.start_servers gibi de\u011ferlerin girildi\u011fi alanlar, yanlar\u0131nda a\u00e7\u0131klama baloncuklar\u0131 var. Arka planda sunucu metriklerini g\u00f6steren canl\u0131 grafikler. Modern, temiz bir aray\u00fcz.\" loading=\"lazy\" \/><\/figure>\n<\/p>\n<p>Tamir setini elinize almadan \u00f6nce \u015fu 3 \u015feyi kontrol edin. \u00c7o\u011fu zaman sorun sand\u0131\u011f\u0131n\u0131zdan \u00e7ok daha basit bir yerdedir.<\/p>\n<p><h3 id=\"1-hatanin-herkeste-mi-yoksa-sadece-sizde-mi-ciktigini-test-edin\">1. Hatan\u0131n Herkeste mi Yoksa Sadece Sizde mi \u00c7\u0131kt\u0131\u011f\u0131n\u0131 Test Edin<\/h3>\n<\/p>\n<p>Taray\u0131c\u0131n\u0131z\u0131n \u00f6nbelle\u011fi veya bir VPN, sadece sizin g\u00f6rd\u00fc\u011f\u00fcn\u00fcz bir 504&#8217;e neden olabilir. Hemen \u015fu ad\u0131mlar\u0131 uygulay\u0131n:<\/p>\n<ul>\n<li>Farkl\u0131 bir taray\u0131c\u0131da (Chrome kullan\u0131yorsan\u0131z Firefox&#8217;ta) siteyi a\u00e7may\u0131 deneyin.<\/li>\n<li>Telefonunuzdan, Wi-Fi&#8217;\u0131 kapat\u0131p mobil veriyle ba\u011flan\u0131n.<\/li>\n<li><a href=\"https:\/\/downforeveryoneorjustme.com\" target=\"_blank\" rel=\"nofollow noopener\">Down For Everyone Or Just Me<\/a> gibi bir servisle sitenizin genel durumunu sorgulay\u0131n.<\/li>\n<li>Farkl\u0131 bir lokasyondan kontrol i\u00e7in bir VPN hizmeti kullan\u0131n.<\/li>\n<\/ul>\n<p>E\u011fer sorun sadece sizdeyse, taray\u0131c\u0131 \u00f6nbelle\u011fini temizleyin, DNS \u00f6nbelle\u011finizi s\u0131f\u0131rlay\u0131n (<code>ipconfig \/flushdns<\/code>), ve modemi yeniden ba\u015flat\u0131n. Sorun \u00e7\u00f6z\u00fclmezse bir sonraki ad\u0131ma ge\u00e7in.<\/p>\n<p><h3 id=\"2-sunucu-kaynak-kullanimini-anlik-olarak-izleyin\">2. Sunucu Kaynak Kullan\u0131m\u0131n\u0131 Anl\u0131k Olarak \u0130zleyin<\/h3>\n<\/p>\n<p><strong>504 gateway timeout hatas\u0131<\/strong> an\u0131nda sunucunuzun ne durumda oldu\u011funu bilmek, te\u015fhisin yar\u0131s\u0131d\u0131r. Hosting panelinize giri\u015f yap\u0131n ve \u015fu metrikleri kontrol edin:<\/p>\n<table style=\"width:100%;border-collapse:collapse;margin:20px 0\">\n<thead>\n<tr style=\"background:#f8fafc;border-bottom:2px solid #e2e8f0\">\n<p><th style=\"padding:12px;text-align:left\">Metrik<\/th>\n<\/p>\n<p><th style=\"padding:12px;text-align:left\">Kritik E\u015fik<\/th>\n<\/p>\n<p><th style=\"padding:12px;text-align:left\">Ne Anlama Gelir?<\/th>\n<\/p>\n<\/tr>\n<\/thead>\n<tbody>\n<tr style=\"border-bottom:1px solid #e2e8f0\">\n<p><td style=\"padding:12px\">CPU Kullan\u0131m\u0131<\/td>\n<\/p>\n<p><td style=\"padding:12px\">&gt; %90 s\u00fcrekli<\/td>\n<\/p>\n<p><td style=\"padding:12px\">PHP worker&#8217;lar\u0131 i\u015flemciyi t\u00fcketiyor<\/td>\n<\/p>\n<\/tr>\n<tr style=\"border-bottom:1px solid #e2e8f0\">\n<p><td style=\"padding:12px\">RAM<\/td>\n<\/p>\n<p><td style=\"padding:12px\">&gt; %95<\/td>\n<\/p>\n<p><td style=\"padding:12px\">OOM Killer devrede olabilir<\/td>\n<\/p>\n<\/tr>\n<tr style=\"border-bottom:1px solid #e2e8f0\">\n<p><td style=\"padding:12px\">Giri\u015f\/\u00c7\u0131k\u0131\u015f (IOPS)<\/td>\n<\/p>\n<p><td style=\"padding:12px\">Disk limitinde<\/td>\n<\/p>\n<p><td style=\"padding:12px\">Yava\u015f disk, veritaban\u0131 sorgular\u0131n\u0131 geciktiriyor<\/td>\n<\/p>\n<\/tr>\n<tr style=\"border-bottom:1px solid #e2e8f0\">\n<p><td style=\"padding:12px\">PHP Worker<\/td>\n<\/p>\n<p><td style=\"padding:12px\">Havuz limitine ula\u015fm\u0131\u015f<\/td>\n<\/p>\n<p><td style=\"padding:12px\">T\u00fcm worker&#8217;lar me\u015fgul, kuyruk olu\u015fuyor<\/td>\n<\/p>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>E\u011fer bu metriklerden herhangi biri k\u0131rm\u0131z\u0131 b\u00f6lgedeyse, sorun hosting kaynakl\u0131d\u0131r. Hemen <a href=\"#hosting-kaynakli\">Hosting Kaynakl\u0131 504 Hatalar\u0131<\/a> b\u00f6l\u00fcm\u00fcne atlay\u0131n.<\/p>\n<p><h3 id=\"3-hata-loglarini-inceleyin-en-az-konusulan-altin-maden\">3. Hata Loglar\u0131n\u0131 \u0130nceleyin (En Az Konu\u015fulan Alt\u0131n Maden)<\/h3>\n<\/p>\n<p>WordPress&#8217;in hata loglar\u0131, sessiz tan\u0131klar gibidir. Her \u015feyi kaydederler ama kimse onlara bakmaz. Oysa tam da <strong>504 gateway timeout hatas\u0131<\/strong> an\u0131nda ne oldu\u011funu anlaman\u0131n en h\u0131zl\u0131 yolu log&#8217;lard\u0131r.<\/p>\n<p><pre><code class=\"language-bash\"># WordPress debug log'unu aktif edin<\/p>\n<p>wp-config.php dosyas\u0131na \u015fu sat\u0131rlar\u0131 ekleyin:<\/p>\n<p>define('WP_DEBUG', true);<\/p>\n<p>define('WP<em>DEBUG<\/em>LOG', true);<\/p>\n<p>define('WP<em>DEBUG<\/em>DISPLAY', false);<\/p>\n<h1 id=\"ardindan-wp-content-debug-log-dosyasini-kontrol-edin\">Ard\u0131ndan \/wp-content\/debug.log dosyas\u0131n\u0131 kontrol edin<\/h1>\n<p>tail -f \/home\/kullaniciadi\/public_html\/wp-content\/debug.log<\/p>\n<h1 id=\"sunucu-hata-loglari-nginx-icin\">Sunucu hata loglar\u0131 (Nginx i\u00e7in)<\/h1>\n<p>tail -f \/var\/log\/nginx\/error.log<\/p>\n<h1 id=\"php-fpm-hata-loglari\">PHP-FPM hata loglar\u0131<\/h1>\n<p>tail -f \/var\/log\/php8.2-fpm.log<\/code><\/pre>\n<\/p>\n<p>Loglar\u0131 incelerken &#8220;timeout&#8221;, &#8220;upstream&#8221;, &#8220;fastcgi&#8221;, &#8220;connection refused&#8221;, &#8220;worker_connections&#8221; gibi anahtar kelimelere odaklan\u0131n. Bunlar size sorunun kayna\u011f\u0131n\u0131 kelimenin tam anlam\u0131yla parmakla g\u00f6sterecektir.<\/p>\n<p><h2 id=\"hosting-kaynakli\">Hosting Kaynakl\u0131 504 Hatalar\u0131n\u0131 Tespit ve \u00c7\u00f6z\u00fcm<\/h2>\n<\/p>\n<p>\u0130\u015fin s\u0131rr\u0131 \u015furada: <strong>504 gateway timeout hatas\u0131<\/strong> vakalar\u0131n\u0131n neredeyse %70&#8217;i hosting altyap\u0131s\u0131yla ilgilidir. WordPress, kaynaklar yetersiz kald\u0131\u011f\u0131nda timeout&#8217;a giden bir zincirleme reaksiyon ba\u015flat\u0131r.<\/p>\n<p><h3 id=\"shared-hostingte-misiniz-limitlerinizi-ogrenin\">Shared Hosting&#8217;te misiniz? Limitlerinizi \u00d6\u011frenin<\/h3>\n<\/p>\n<p>Payla\u015f\u0131ml\u0131 hosting paketleri, genellikle &#8220;s\u0131n\u0131rs\u0131z&#8221; vaadiyle sat\u0131l\u0131r. Ama i\u015fin asl\u0131 \u015fudur: Her paketin g\u00f6r\u00fcnmez duvarlar\u0131 vard\u0131r. I\/O limiti, CPU kotas\u0131, entry processes s\u0131n\u0131r\u0131, fiziksel bellek limiti&#8230; Bu de\u011ferlerden herhangi biri a\u015f\u0131ld\u0131\u011f\u0131nda 504 hatas\u0131 alman\u0131z an meselesidir.<\/p>\n<p>Ge\u00e7ti\u011fimiz ay bir dan\u0131\u015fan\u0131m\u0131z &#8220;s\u0131n\u0131rs\u0131z&#8221; pakette oldu\u011fu halde s\u00fcrekli 504 al\u0131yordu. Kontrol etti\u011fimizde, hosting firmas\u0131n\u0131n I\/O limitini 1 MB\/s ile s\u0131n\u0131rlad\u0131\u011f\u0131n\u0131 g\u00f6rd\u00fck. WooCommerce sitesi bir sipari\u015fte 15 \u00fcr\u00fcn g\u00f6rseli y\u00fcklerken bu limit an\u0131nda t\u0131kan\u0131yordu. \u00c7\u00f6z\u00fcm? <strong>Linux hosting<\/strong> paketini NVMe SSD diskli bir sunucuya ta\u015f\u0131mak oldu \u2014 sorun bir daha tekrarlamad\u0131.<\/p>\n<p><h3 id=\"yetersiz-php-worker-havuzu\">Yetersiz PHP Worker Havuzu<\/h3>\n<\/p>\n<p>PHP-FPM&#8217;in pm (process manager) ayarlar\u0131, ayn\u0131 anda ka\u00e7 ziyaret\u00e7iye hizmet verebilece\u011finizi belirler. Varsay\u0131lan ayarlar genellikle d\u00fc\u015f\u00fckt\u00fcr.<\/p>\n<p><pre><code class=\"language-ini\"># Standart (yetersiz) ayar<\/p>\n<p>pm = dynamic<\/p>\n<p>pm.max_children = 5<\/p>\n<p>pm.start_servers = 2<\/p>\n<p>pm.min<em>spare<\/em>servers = 1<\/p>\n<p>pm.max<em>spare<\/em>servers = 3<\/p>\n<p>pm.max_requests = 500<\/p>\n<h1 id=\"onerilen-ayar-4-gb-ram-icin\">\u00d6nerilen ayar (4 GB RAM i\u00e7in)<\/h1>\n<p>pm = ondemand<\/p>\n<p>pm.max_children = 50<\/p>\n<p>pm.process<em>idle<\/em>timeout = 10s<\/p>\n<p>pm.max_requests = 500<\/code><\/pre>\n<\/p>\n<p>Peki bu ne anlama geliyor? <code>max_children<\/code> de\u011feri 5 oldu\u011funda, siteniz ayn\u0131 anda sadece 5 ki\u015fiye PHP i\u015flemi yapabilir. 6. ziyaret\u00e7i geldi\u011finde&#8230; evet, tahmin etti\u011finiz gibi, <strong>504 gateway timeout hatas\u0131<\/strong>.<\/p>\n<p>Dikkatli olun: <code>max_children<\/code> de\u011ferini \u00e7ok y\u00fcksek ayarlamak sunucunun RAM&#8217;ini t\u00fcketebilir. Her PHP worker&#8217;\u0131 ortalama 50-80 MB RAM kullan\u0131r. 50 worker \u00d7 80 MB = 4 GB RAM demektir. Toplam RAM&#8217;inizin %80&#8217;ini ge\u00e7ecek \u015fekilde ayarlamay\u0131n.<\/p>\n<p><p style=\"background:#f0fdf4;border-left:4px solid #22c55e;padding:15px;margin:20px 0;border-radius:6px\"><strong>\ud83d\udca1 SaviorHost \u0130pucu:<\/strong> Y\u00fcksek trafikli WordPress siteleri i\u00e7in optimize edilmi\u015f <strong>WordPress hosting<\/strong> paketlerimiz, PHP-FPM worker havuzunu sitenizin ihtiyac\u0131na g\u00f6re otomatik \u00f6l\u00e7eklendiriyor. Ayr\u0131ca AMD Ryzen 9 7900 i\u015flemciler ve NVMe SSD diskler sayesinde her bir PHP iste\u011fi %60 daha h\u0131zl\u0131 i\u015fleniyor \u2014 bu da timeout riskini dramatik \u015fekilde azalt\u0131yor.<\/p>\n<\/p>\n<p><h2 id=\"php-fpm\">PHP-FPM Timeout Ayarlar\u0131n\u0131 Optimize Etme<\/h2>\n<\/p>\n<p><strong>504 gateway timeout hatas\u0131<\/strong> ile m\u00fccadelede en kritik cephe buras\u0131d\u0131r. PHP-FPM timeout ayarlar\u0131, bir PHP beti\u011finin ne kadar s\u00fcre \u00e7al\u0131\u015fmas\u0131na izin verilece\u011fini belirler.<\/p>\n<p><h3 id=\"maxexecutiontime-ve-requestterminatetimeout-farki\">max<em>execution<\/em>time ve request<em>terminate<\/em>timeout Fark\u0131<\/h3>\n<\/p>\n<p>\u00c7o\u011fu ki\u015fi sadece <code>max<em>execution<\/em>time<\/code> de\u011ferine odaklan\u0131r. Ama bu b\u00fcy\u00fck bir hatad\u0131r. \u0130\u015fte ger\u00e7ek ayr\u0131m:<\/p>\n<table style=\"width:100%;border-collapse:collapse;margin:20px 0\">\n<thead>\n<tr style=\"background:#f8fafc;border-bottom:2px solid #e2e8f0\">\n<p><th style=\"padding:12px;text-align:left\">Ayar<\/th>\n<\/p>\n<p><th style=\"padding:12px;text-align:left\">Neyi Kontrol Eder<\/th>\n<\/p>\n<p><th style=\"padding:12px;text-align:left\">\u00d6nerilen De\u011fer<\/th>\n<\/p>\n<\/tr>\n<\/thead>\n<tbody>\n<tr style=\"border-bottom:1px solid #e2e8f0\">\n<p><td style=\"padding:12px\"><code>max<em>execution<\/em>time<\/code><\/td>\n<\/p>\n<p><td style=\"padding:12px\">PHP beti\u011finin kendini sonland\u0131rmas\u0131 i\u00e7in \u00fcst s\u0131n\u0131r. Harici \u00e7a\u011fr\u0131lar (API, veritaban\u0131) bu s\u00fcreye dahil de\u011fildir!<\/td>\n<\/p>\n<p><td style=\"padding:12px\">120-180 saniye<\/td>\n<\/p>\n<\/tr>\n<tr style=\"border-bottom:1px solid #e2e8f0\">\n<p><td style=\"padding:12px\"><code>request<em>terminate<\/em>timeout<\/code><\/td>\n<\/p>\n<p><td style=\"padding:12px\">PHP-FPM&#8217;in beti\u011fi ZORLA sonland\u0131raca\u011f\u0131 s\u00fcre. Buna harici \u00e7a\u011fr\u0131lar DAH\u0130LD\u0130R.<\/td>\n<\/p>\n<p><td style=\"padding:12px\">120-300 saniye<\/td>\n<\/p>\n<\/tr>\n<tr style=\"border-bottom:1px solid #e2e8f0\">\n<p><td style=\"padding:12px\"><code>request<em>slowlog<\/em>timeout<\/code><\/td>\n<\/p>\n<p><td style=\"padding:12px\">Belirtilen saniyeden uzun s\u00fcren istekleri &#8220;slow log&#8221;a yazar.<\/td>\n<\/p>\n<p><td style=\"padding:12px\">10-30 saniye<\/td>\n<\/p>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Bunu \u015f\u00f6yle d\u00fc\u015f\u00fcn\u00fcn: <code>max<em>execution<\/em>time<\/code> kibarca &#8220;bitir art\u0131k&#8221; der. <code>request<em>terminate<\/em>timeout<\/code> ise kap\u0131y\u0131 k\u0131rarak i\u00e7eri girer ve &#8220;yeter!&#8221; diye ba\u011f\u0131r\u0131r.<\/p>\n<p><h3 id=\"adim-adim-php-fpm-timeout-ayari\">Ad\u0131m Ad\u0131m PHP-FPM Timeout Ayar\u0131<\/h3>\n<\/p>\n<ol>\n<li>Hosting panelinizden veya SSH \u00fczerinden PHP-FPM havuz yap\u0131land\u0131rma dosyas\u0131n\u0131 bulun. KeyHelp panelinde bu: <code>\/etc\/php\/8.2\/fpm\/pool.d\/kullaniciadi.conf<\/code><\/li>\n<li>Dosyay\u0131 d\u00fczenleyin ve \u015fu sat\u0131rlar\u0131 ekleyin veya g\u00fcncelleyin:<\/p>\n<p><pre><code class=\"language-ini\">; PHP beti\u011fi i\u00e7in maksimum \u00e7al\u0131\u015fma s\u00fcresi<\/p>\n<p>php<em>admin<\/em>value[max<em>execution<\/em>time] = 180<\/p>\n<p>; PHP-FPM'in beti\u011fi zorla sonland\u0131raca\u011f\u0131 s\u00fcre<\/p>\n<p>request<em>terminate<\/em>timeout = 180s<\/p>\n<p>; Yava\u015f log ayar\u0131 \u2014 504 te\u015fhisi i\u00e7in alt\u0131n de\u011ferinde<\/p>\n<p>request<em>slowlog<\/em>timeout = 15s<\/p>\n<p>slowlog = \/var\/log\/php-fpm-slow.log<\/code><\/pre>\n<\/li>\n<li>PHP-FPM servisini yeniden ba\u015flat\u0131n: <code>systemctl restart php8.2-fpm<\/code><\/li>\n<li>15 saniyeden uzun s\u00fcren istekleri <code>\/var\/log\/php-fpm-slow.log<\/code> dosyas\u0131ndan takip edin. Her g\u00fcn bu logu kontrol ederek sorunlu betikleri tespit edebilirsiniz.<\/li>\n<\/ol>\n<p><h3 id=\"e-ticaret-siteleri-icin-ozel-php-fpm-recetesi\">E-Ticaret Siteleri \u0130\u00e7in \u00d6zel PHP-FPM Re\u00e7etesi<\/h3>\n<\/p>\n<p>WooCommerce veya PrestaShop gibi e-ticaret platformlar\u0131, \u00f6zellikle sipari\u015f i\u015fleme, stok senkronizasyonu ve raporlama s\u0131ras\u0131nda a\u011f\u0131r PHP i\u015flemleri yapar. Bu sitelerde timeout s\u00fcrelerini \u015f\u00f6yle ayarlamal\u0131s\u0131n\u0131z:<\/p>\n<p><p style=\"background:#fef3c7;border-left:4px solid #d97706;padding:15px;margin:20px 0;border-radius:6px\"><strong>\u26a0\ufe0f E-Ticaret Uyar\u0131s\u0131:<\/strong> \u00d6deme ge\u00e7idi API&#8217;lar\u0131 bazen 30-45 saniye yan\u0131t vermeyebilir. request<em>terminate<\/em>timeout de\u011ferini 300 saniye (5 dakika) alt\u0131nda tutun. Daha y\u00fcksek de\u011ferler, ba\u015far\u0131s\u0131z bir \u00f6deme i\u015flemi s\u0131ras\u0131nda worker&#8217;\u0131n bo\u015funa bekleyip di\u011fer ziyaret\u00e7ilerin 504 almas\u0131na neden olur.<\/p>\n<\/p>\n<p>E\u011fer e-ticaret siteniz s\u00fcrekli bu t\u00fcr sorunlar ya\u015f\u0131yorsa, <strong>e-ticaret hosting<\/strong> altyap\u0131s\u0131na ge\u00e7meyi ciddi \u015fekilde d\u00fc\u015f\u00fcnmelisiniz. \u00d6zel olarak yap\u0131land\u0131r\u0131lm\u0131\u015f PHP-FPM havuzlar\u0131 ve Redis cache ile timeout riskini minimuma indiren paketler, sat\u0131\u015f kayb\u0131n\u0131z\u0131 \u00f6nlemenin en etkili yoludur.<\/p>\n<p><h2 id=\"nginx-apache\">Nginx ve Apache Proxy Ayarlar\u0131n\u0131 D\u00fczenleme<\/h2>\n<\/p>\n<p>\u015eimdi i\u015fin proxy boyutuna inelim. <strong>504 gateway timeout hatas\u0131<\/strong>, ad\u0131ndan da anla\u015f\u0131laca\u011f\u0131 gibi bir gateway (a\u011f ge\u00e7idi) sorunudur. Bu ge\u00e7it genellikle Nginx veya Apache&#8217;dir.<\/p>\n<p><h3 id=\"nginxte-3-kritik-timeout-ayari\">Nginx&#8217;te 3 Kritik Timeout Ayar\u0131<\/h3>\n<\/p>\n<p>Nginx, PHP-FPM ile konu\u015furken kendi timeout de\u011ferlerine sahiptir. Bu de\u011ferler PHP-FPM ayarlar\u0131ndan BA\u011eIMSIZDIR. \u0130kisi de ayr\u0131 ayr\u0131 yap\u0131land\u0131r\u0131lmal\u0131d\u0131r.<\/p>\n<p><pre><code class=\"language-nginx\"># \/etc\/nginx\/conf.d\/timeout.conf<\/p>\n<h1 id=\"veya-siteye-ozel-conf-dosyasina-ekleyin\">veya siteye \u00f6zel .conf dosyas\u0131na ekleyin<\/h1>\n<h1 id=\"php-fpmden-yanit-bekleme-suresi-en-kritik-ayar\">PHP-FPM'den yan\u0131t bekleme s\u00fcresi (en kritik ayar!)<\/h1>\n<p>fastcgi<em>read<\/em>timeout 180s;<\/p>\n<h1 id=\"proxy-upstream-bekleme-suresi\">Proxy upstream bekleme s\u00fcresi<\/h1>\n<p>proxy<em>read<\/em>timeout 180s;<\/p>\n<h1 id=\"baglanti-kurma-suresi\">Ba\u011flant\u0131 kurma s\u00fcresi<\/h1>\n<p>proxy<em>connect<\/em>timeout 60s;<\/p>\n<h1 id=\"yanit-gonderme-suresi\">Yan\u0131t g\u00f6nderme s\u00fcresi<\/h1>\n<p>proxy<em>send<\/em>timeout 60s;<\/p>\n<h1 id=\"keepalive-timeout-uzun-sureli-baglantilar-icin\">Keepalive timeout \u2014 uzun s\u00fcreli ba\u011flant\u0131lar i\u00e7in<\/h1>\n<p>keepalive_timeout 65s;<\/code><\/pre>\n<\/p>\n<p>Peki bu de\u011ferleri neden 180 saniye yapt\u0131k? \u00c7\u00fcnk\u00fc PHP-FPM&#8217;de <code>request<em>terminate<\/em>timeout<\/code> 180 saniye ise, Nginx&#8217;in de en az bu kadar beklemesi gerekir. Aksi takdirde, PHP h\u00e2l\u00e2 \u00e7al\u0131\u015f\u0131yor olsa bile Nginx &#8220;yeter art\u0131k&#8221; deyip ba\u011flant\u0131y\u0131 keser \u2014 ve yine 504!<\/p>\n<p><h3 id=\"apache-mod_proxy-kullaniyorsaniz\">Apache + mod_proxy Kullan\u0131yorsan\u0131z<\/h3>\n<\/p>\n<p>Apache&#8217;nin proxy mod\u00fcl\u00fc de benzer timeout de\u011ferlerine ihtiya\u00e7 duyar. \u00d6zellikle PHP-FPM ile proxy_fcgi mod\u00fcl\u00fc \u00fczerinden konu\u015fan Apache sunucularda:<\/p>\n<p><pre><code class=\"language-apache\"># .htaccess veya apache2.conf<\/p>\n<p>&lt;IfModule mod_proxy.c&gt;<\/p>\n<p>    ProxyTimeout 180<\/p>\n<p>&lt;\/IfModule&gt;<\/p>\n<p>&lt;IfModule proxy<em>fcgi<\/em>module&gt;<\/p>\n<p>    # PHP-FPM ba\u011flant\u0131 timeout'u<\/p>\n<p>    Timeout 180<\/p>\n<p>&lt;\/IfModule&gt;<\/code><\/pre>\n<\/p>\n<p><h3 id=\"nginx-buffer-ayarlari-gozden-kacan-detay\">Nginx Buffer Ayarlar\u0131 (G\u00f6zden Ka\u00e7an Detay)<\/h3>\n<\/p>\n<p>B\u00fcy\u00fck HTTP yan\u0131tlar\u0131 (\u00f6rne\u011fin XML sitemap, \u00fcr\u00fcn beslemesi, CSV d\u0131\u015fa aktar\u0131m\u0131) Nginx buffer&#8217;lar\u0131n\u0131 a\u015farsa, cevap tamamlanmadan ba\u011flant\u0131 kesilebilir. Bu da dolayl\u0131 olarak 504&#8217;e neden olur:<\/p>\n<p><pre><code class=\"language-nginx\"># Buffer boyutlar\u0131n\u0131 b\u00fcy\u00fct\u00fcn<\/p>\n<p>proxy<em>buffer<\/em>size          128k;<\/p>\n<p>proxy_buffers              4 256k;<\/p>\n<p>proxy<em>busy<\/em>buffers_size    256k;<\/p>\n<p>fastcgi<em>buffer<\/em>size        128k;<\/p>\n<p>fastcgi_buffers            4 256k;<\/p>\n<p>fastcgi<em>busy<\/em>buffers_size  256k;<\/code><\/pre>\n<\/p>\n<p><h2 id=\"cloudflare-cdn\">Cloudflare ve CDN Kaynakl\u0131 504 Hatalar\u0131n\u0131 Giderme<\/h2>\n<\/p>\n<p>Cloudflare kullan\u0131yorsan\u0131z, <strong>504 gateway timeout hatas\u0131<\/strong> asl\u0131nda bir &#8220;Cloudflare 524&#8221; hatas\u0131 olarak kar\u015f\u0131n\u0131za \u00e7\u0131kabilir. Bu ikisi aras\u0131ndaki fark hayati \u00f6nem ta\u015f\u0131r.<\/p>\n<p><h3 id=\"504-vs-524-dogru-teshisin-onemi\">504 vs 524: Do\u011fru Te\u015fhisin \u00d6nemi<\/h3>\n<\/p>\n<p>Cloudflare, origin sunucunuzla aras\u0131ndaki ba\u011flant\u0131 koptu\u011funda kendi hata sayfas\u0131n\u0131 g\u00f6sterir. E\u011fer ekranda Cloudflare logosu ve &#8220;Error 524: A timeout occurred&#8221; yaz\u0131yorsa, sorun Cloudflare ile sunucunuz aras\u0131ndaki ba\u011flant\u0131dad\u0131r. Klasik bir 504 ise do\u011frudan sunucunuzdan d\u00f6ner (genellikle Nginx sayfas\u0131).<\/p>\n<p><h3 id=\"cloudflare-524-hatasi-icin-5-adimli-cozum\">Cloudflare 524 Hatas\u0131 \u0130\u00e7in 5 Ad\u0131ml\u0131 \u00c7\u00f6z\u00fcm<\/h3>\n<\/p>\n<ol>\n<li><strong>Cloudflare&#8217;\u0131 Bekleme Moduna (Development Mode) Al\u0131n:<\/strong> Cloudflare dashboard&#8217;unuzdan &#8220;Overview&#8221; sekmesinde &#8220;Development Mode&#8221;u aktif edin. Bu, t\u00fcm cache ve optimizasyon \u00f6zelliklerini ge\u00e7ici olarak devre d\u0131\u015f\u0131 b\u0131rak\u0131r. Sorun \u00e7\u00f6z\u00fcl\u00fcrse, Cloudflare ayarlar\u0131n\u0131zda bir \u00e7ak\u0131\u015fma var demektir.<\/li>\n<li><strong>Cloudflare IP Aral\u0131klar\u0131n\u0131 Sunucu G\u00fcvenlik Duvar\u0131nda Beyaz Listeye Al\u0131n:<\/strong> Sunucunuzdaki CSF, Fail2ban veya iptables, Cloudflare&#8217;\u0131n IP&#8217;lerini engelliyor olabilir. Cloudflare&#8217;\u0131n resmi IP listesini kontrol edin ve bunlar\u0131 g\u00fcvenlik duvar\u0131n\u0131zda izin verilenler listesine ekleyin.<\/li>\n<li><strong>DNS Only (Gri Bulut) Modunu Test Edin:<\/strong> \u0130lgili DNS kayd\u0131n\u0131 (A veya CNAME) &#8220;Proxied&#8221; (turuncu bulut) durumundan &#8220;DNS Only&#8221; (gri bulut) durumuna al\u0131n. Bu, trafi\u011fin do\u011frudan sunucunuza gitmesini sa\u011flar. E\u011fer 504 kaybolursa, sorun Cloudflare proxy&#8217;sindedir.<\/li>\n<li><strong>Origin Sunucu Ba\u011flant\u0131 S\u00fcresini Optimize Edin:<\/strong> Cloudflare&#8217;\u0131n origin sunucunuza ba\u011flanma s\u00fcresi 100 saniyedir (varsay\u0131lan). Sunucunuz bu s\u00fcrede yan\u0131t veremezse 524 al\u0131rs\u0131n\u0131z. Sunucu yan\u0131t s\u00fcrenizi (TTFB) 1 saniyenin alt\u0131na d\u00fc\u015f\u00fcrmek i\u00e7in <a href=\"https:\/\/saviorhost.com\/blog\/core-web-vitals-nedir-google-hiz-metrikleri-rehberi\/\" target=\"_blank\">Core Web Vitals optimizasyonlar\u0131n\u0131<\/a> uygulay\u0131n.<\/li>\n<li><strong>Railgun veya Argo Smart Routing Kullan\u0131n:<\/strong> Cloudflare&#8217;\u0131n premium \u00f6zellikleri olan Railgun veya Argo, origin sunucu ile CDN aras\u0131ndaki ba\u011flant\u0131y\u0131 optimize ederek timeout riskini ciddi oranda d\u00fc\u015f\u00fcr\u00fcr. \u00d6zellikle T\u00fcrkiye&#8217;den yurtd\u0131\u015f\u0131 sunuculara yap\u0131lan ba\u011flant\u0131larda Argo&#8217;nun etkisi kan\u0131tlanm\u0131\u015ft\u0131r.<\/li>\n<\/ol>\n<p><h3 id=\"diger-cdnler-icin-genel-gecer-kontroller\">Di\u011fer CDN&#8217;ler \u0130\u00e7in Genel Ge\u00e7er Kontroller<\/h3>\n<\/p>\n<p>StackPath, KeyCDN, BunnyCDN gibi alternatif CDN&#8217;ler kullan\u0131yorsan\u0131z:<\/p>\n<ul>\n<li>Origin shield (ara cache katman\u0131) \u00f6zelli\u011fini aktif edin.<\/li>\n<li>CDN&#8217;in &#8220;origin timeout&#8221; ayar\u0131n\u0131 60-120 saniye aral\u0131\u011f\u0131na \u00e7ekin.<\/li>\n<li>Origin sunucunuzla CDN aras\u0131nda HTTP\/2 veya HTTP\/3 ba\u011flant\u0131s\u0131 kullan\u0131n.<\/li>\n<\/ul>\n<p><h2 id=\"wordpress-eklenti\">WordPress Eklenti ve Tema Kaynakl\u0131 Timeout Sorunlar\u0131<\/h2>\n<\/p>\n<p>Gelelim WordPress&#8217;in kendi i\u00e7indeki kara kutuya. Bazen <strong>504 gateway timeout hatas\u0131<\/strong> sunucuyla alakal\u0131 de\u011fildir; su\u00e7lu, o masum g\u00f6r\u00fcnen &#8220;\u00fccretsiz&#8221; eklentidir.<\/p>\n<p><h3 id=\"health-check-eklentisi-ile-sorunlu-eklentiyi-yakalayin\">Health Check Eklentisi ile Sorunlu Eklentiyi Yakalay\u0131n<\/h3>\n<\/p>\n<p>WordPress&#8217;in resmi &#8220;Health Check &amp; Troubleshooting&#8221; eklentisi, sitenizin t\u00fcm i\u015flevselli\u011fini bozmadan, sadece sizin g\u00f6rd\u00fc\u011f\u00fcn\u00fcz bir test ortam\u0131 olu\u015fturur. \u015e\u00f6yle kullan\u0131n:<\/p>\n<ol>\n<li>Eklentiler &gt; Yeni Ekle &gt; &#8220;Health Check&#8221; arat\u0131n ve kurun.<\/li>\n<li>&#8220;Sorun Giderme Modu&#8221;nu (Troubleshooting Mode) aktif edin.<\/li>\n<li>Bu moddayken t\u00fcm eklentiler DEVRE DI\u015eI kal\u0131r ve varsay\u0131lan tema aktif olur (sadece siz g\u00f6r\u00fcrs\u00fcn\u00fcz, ziyaret\u00e7iler sitenin normal halini g\u00f6r\u00fcr).<\/li>\n<li>Tek tek eklentileri a\u00e7arak hangisinin 504&#8217;e neden oldu\u011funu test edin.<\/li>\n<li>Su\u00e7luyu buldu\u011funuzda, o eklentiyi tamamen kald\u0131r\u0131n veya alternatifini ara\u015ft\u0131r\u0131n.<\/li>\n<\/ol>\n<p><h3 id=\"en-cok-504-yapan-eklenti-turleri-2026-kara-listesi\">En \u00c7ok 504 Yapan Eklenti T\u00fcrleri (2026 Kara Listesi)<\/h3>\n<\/p>\n<p>Y\u0131llar i\u00e7inde binlerce WordPress sitesi \u00fczerinde yapt\u0131\u011f\u0131m\u0131z incelemelerde, \u015fu eklenti kategorilerinin <strong>504 gateway timeout hatas\u0131<\/strong> \u00fcretme olas\u0131l\u0131\u011f\u0131n\u0131n di\u011ferlerine g\u00f6re 4 kat fazla oldu\u011funu g\u00f6rd\u00fck:<\/p>\n<ul>\n<li><strong>Canl\u0131 Sohbet (Live Chat) Eklentileri:<\/strong> Her ziyaret\u00e7i i\u00e7in sunucunuza s\u00fcrekli AJAX iste\u011fi g\u00f6nderir. Zendesk, Tawk.to, LiveChat gibi eklentiler PHP worker&#8217;lar\u0131n\u0131 s\u00f6m\u00fcrebilir.<\/li>\n<li><strong>Yedekleme Eklentileri:<\/strong> UpdraftPlus, BackupBuddy gibi ara\u00e7lar yedekleme s\u0131ras\u0131nda t\u00fcm sunucu kaynaklar\u0131n\u0131 t\u00fcketebilir. Yedeklemeleri gece saatlerine planlay\u0131n.<\/li>\n<li><strong>SEO Eklentilerinin Site Haritas\u0131 \u00d6zelli\u011fi:<\/strong> Yoast SEO ve RankMath&#8217;in XML site haritas\u0131 olu\u015fturma i\u015flemi, b\u00fcy\u00fck sitelerde (10.000+ i\u00e7erik) timeout&#8217;a neden olabilir.<\/li>\n<li><strong>G\u00f6rsel Optimizasyon Eklentileri:<\/strong> Smush, ShortPixel gibi ara\u00e7lar toplu optimizasyon s\u0131ras\u0131nda sunucuyu zorlayabilir. Her zaman &#8220;arka planda i\u015fle&#8221; se\u00e7ene\u011fini kullan\u0131n.<\/li>\n<li><strong>Sayfa Kurucular (Page Builders):<\/strong> Elementor, Divi, WPBakery \u2014 \u00f6zellikle edit\u00f6r ekran\u0131nda \u00e7al\u0131\u015f\u0131rken arka planda onlarca API \u00e7a\u011fr\u0131s\u0131 yaparlar.<\/li>\n<\/ul>\n<p><h3 id=\"temanizin-functions-php-dosyasini-gozden-gecirin\">Teman\u0131z\u0131n functions.php Dosyas\u0131n\u0131 G\u00f6zden Ge\u00e7irin<\/h3>\n<\/p>\n<p>Baz\u0131 temalar, \u00f6zellikle ThemeForest&#8217;ten al\u0131nan \u00e7ok ama\u00e7l\u0131 temalar, <code>functions.php<\/code> dosyas\u0131nda y\u00fczlerce <code>require_once<\/code> \u00e7a\u011fr\u0131s\u0131, harici font y\u00fcklemesi ve API iste\u011fi bar\u0131nd\u0131r\u0131r. \u015eu kod par\u00e7as\u0131n\u0131 <code>functions.php<\/code>&#8216;nizin en ba\u015f\u0131na ekleyerek hangi i\u015flevlerin ne kadar s\u00fcrede \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 profilleyebilirsiniz:<\/p>\n<p><pre><code class=\"language-php\">\/\/ functions.php'in en ba\u015f\u0131na ekleyin<\/p>\n<p>add_action('shutdown', function() {<\/p>\n<p>    $time = timer_stop(0, 3);<\/p>\n<p>    if ($time &gt; 5) { \/\/ 5 saniyeden uzun s\u00fcren i\u015flemleri logla<\/p>\n<p>        error<em>log(\"YAVA\u015e: functions.php islemleri {$time} saniye surdu. URL: \" . $<\/em>SERVER['REQUEST_URI']);<\/p>\n<p>    }<\/p>\n<p>}, 9999);<\/code><\/pre>\n<\/p>\n<p><p style=\"background:#fef9e7;border-left:4px solid #f59e0b;padding:15px;margin:20px 0;border-radius:6px\"><strong>\ud83d\udd0d Deneyim Notu:<\/strong> Ge\u00e7en y\u0131l bir m\u00fc\u015fterimizin sitesinde 504 hatas\u0131, teman\u0131n Google Fonts&#8217;u senkronize olarak y\u00fcklemesinden kaynaklan\u0131yordu. Google Fonts API&#8217;si 3 saniye gecikince t\u00fcm sayfa timeout&#8217;a giriyordu. \u00c7\u00f6z\u00fcm: Fontlar\u0131 lokal olarak sunmak ve <code>async<\/code> y\u00fckleme kullanmakt\u0131. Sorun tamamen ortadan kalkt\u0131.<\/p>\n<\/p>\n<p><h2 id=\"veritabani\">Veritaban\u0131 Ba\u011flant\u0131 Timeout&#8217;lar\u0131n\u0131 Kal\u0131c\u0131 Olarak \u00c7\u00f6zme<\/h2>\n<\/p>\n<p>Veritaban\u0131, WordPress&#8217;in kalbidir. Ve bu kalp yava\u015f att\u0131\u011f\u0131nda, <strong>504 gateway timeout hatas\u0131<\/strong> ka\u00e7\u0131n\u0131lmaz olur.<\/p>\n<p><h3 id=\"mysql-mariadb-wait_timeout-ayari\">MySQL\/MariaDB wait_timeout Ayar\u0131<\/h3>\n<\/p>\n<p>Veritaban\u0131 sunucusunun <code>wait_timeout<\/code> de\u011feri, bo\u015fta kalan ba\u011flant\u0131lar\u0131 ne zaman kapataca\u011f\u0131n\u0131 belirler. WordPress varsay\u0131lan olarak kal\u0131c\u0131 ba\u011flant\u0131 (persistent connection) kullanmaz, bu y\u00fczden bu de\u011fer \u00e7ok d\u00fc\u015f\u00fckse s\u00fcrekli yeni ba\u011flant\u0131 a\u00e7ma-kapama i\u015flemi yap\u0131l\u0131r. Bu da gecikmeye neden olur.<\/p>\n<p><pre><code class=\"language-sql\">-- Mevcut de\u011feri kontrol edin<\/p>\n<p>SHOW VARIABLES LIKE 'wait_timeout';<\/p>\n<p>SHOW VARIABLES LIKE 'interactive_timeout';<\/p>\n<p>-- \u00d6nerilen de\u011ferler (saniye cinsinden)<\/p>\n<p>SET GLOBAL wait_timeout = 600;<\/p>\n<p>SET GLOBAL interactive_timeout = 600;<\/code><\/pre>\n<\/p>\n<p><h3 id=\"yavas-sorgulari-tespit-edin-ve-optimize-edin\">Yava\u015f Sorgular\u0131 Tespit Edin ve Optimize Edin<\/h3>\n<\/p>\n<p><strong>504 gateway timeout hatas\u0131<\/strong> ile bo\u011fu\u015furken en b\u00fcy\u00fck m\u00fcttefikiniz MySQL yava\u015f sorgu logudur:<\/p>\n<p><pre><code class=\"language-sql\">-- Yava\u015f sorgu log'unu aktif edin (2 saniyeden uzun s\u00fcrenler)<\/p>\n<p>SET GLOBAL slow<em>query<\/em>log = 'ON';<\/p>\n<p>SET GLOBAL long<em>query<\/em>time = 2;<\/p>\n<p>SET GLOBAL slow<em>query<\/em>log_file = '\/var\/log\/mysql-slow.log';<\/code><\/pre>\n<\/p>\n<p>Bir s\u00fcre sonra bu log dosyas\u0131n\u0131 <code>mysqldumpslow<\/code> veya <code>pt-query-digest<\/code> (Percona Toolkit) ile analiz edin. En yava\u015f 10 sorguyu tespit edip indeksleyin veya yeniden yaz\u0131n.<\/p>\n<p><h3 id=\"woocommerce-icin-wp_postmeta-indeksleme\">WooCommerce i\u00e7in wp_postmeta \u0130ndeksleme<\/h3>\n<\/p>\n<p>WooCommerce sitelerinde en s\u0131k g\u00f6r\u00fclen veritaban\u0131 kaynakl\u0131 504 nedeni, <code>wp_postmeta<\/code> tablosundaki indekslenmemi\u015f sorgulard\u0131r. \u015eu SQL komutlar\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rarak bu tabloyu optimize edin:<\/p>\n<p><pre><code class=\"language-sql\">-- wp_postmeta tablosuna indeks ekleyin (D\u0130KKAT: \u00d6nce yedek al\u0131n!)<\/p>\n<p>ALTER TABLE wp<em>postmeta ADD INDEX meta<\/em>key<em>value (meta<\/em>key(191), meta_value(191));<\/p>\n<p>ALTER TABLE wp<em>postmeta ADD INDEX post<\/em>id<em>meta<\/em>key (post<em>id, meta<\/em>key(191));<\/p>\n<p>-- Tabloyu optimize edin<\/p>\n<p>OPTIMIZE TABLE wp_postmeta;<\/code><\/pre>\n<\/p>\n<p>Bu basit indeksleme i\u015flemi, 100.000+ sipari\u015fi olan bir WooCommerce sitesinde sorgu s\u00fcresini 8 saniyeden 0.2 saniyeye d\u00fc\u015f\u00fcrebilir. Aradaki fark, 504 ile sat\u0131\u015f yapmaya devam etmek aras\u0131ndaki farkt\u0131r.<\/p>\n<p><h2 id=\"wp-cron\">WP-Cron ve Zamanlanm\u0131\u015f G\u00f6rev \u00c7ak\u0131\u015fmalar\u0131<\/h2>\n<\/p>\n<p>WordPress&#8217;in kron i\u015fleri (cron jobs), fark\u0131nda olmadan <strong>504 gateway timeout hatas\u0131<\/strong> \u00fcreten bir suikast\u00e7\u0131d\u0131r. Her sayfa y\u00fcklenmesinde <code>wp-cron.php<\/code> tetiklenir, birikmi\u015f t\u00fcm g\u00f6revleri s\u0131raya koyar ve \u00e7al\u0131\u015ft\u0131rmaya ba\u015flar.<\/p>\n<p><h3 id=\"gercek-cron-ile-wp-cronu-devre-disi-birakin\">Ger\u00e7ek Cron ile WP-Cron&#8217;u Devre D\u0131\u015f\u0131 B\u0131rak\u0131n<\/h3>\n<\/p>\n<p>Bu, sitenizin performans\u0131n\u0131 an\u0131nda %20-30 art\u0131racak en etkili WordPress optimizasyonlar\u0131ndan biridir:<\/p>\n<ol>\n<li><code>wp-config.php<\/code> dosyan\u0131za \u015fu sat\u0131r\u0131 ekleyin:<\/p>\n<p><pre><code class=\"language-php\">define('DISABLE<em>WP<\/em>CRON', true);<\/code><\/pre>\n<\/p>\n<\/li>\n<li>Sunucunuzun cron tablosuna (ger\u00e7ek cron) \u015fu sat\u0131r\u0131 ekleyin:<\/p>\n<p><pre><code class=\"language-bash\"># Her 15 dakikada bir wp-cron.php'yi \u00e7al\u0131\u015ft\u0131r<\/p>\n<p><em>\/15 <\/em> <em> <\/em> * \/usr\/bin\/php \/home\/kullaniciadi\/public_html\/wp-cron.php &gt; \/dev\/null 2&gt;&amp;1<\/code><\/pre>\n<\/p>\n<p>Alternatif olarak, hosting panelinizden (KeyHelp, cPanel) Cron Jobs b\u00f6l\u00fcm\u00fcne giderek ayn\u0131 komutu ekleyebilirsiniz.<\/p>\n<\/li>\n<\/ol>\n<p>Bu y\u00f6ntemle wp-cron her sayfa y\u00fcklemesinde de\u011fil, sadece belirledi\u011finiz aral\u0131klarla \u00e7al\u0131\u015f\u0131r. Sonu\u00e7? PHP worker&#8217;lar\u0131 gereksiz cron i\u015flemleriyle me\u015fgul olmaz.<\/p>\n<p><h3 id=\"birikmis-cron-gorevlerini-temizleyin\">Birikmi\u015f Cron G\u00f6revlerini Temizleyin<\/h3>\n<\/p>\n<p>Bazen cron g\u00f6revleri birikir ve y\u00fczlerce bekleyen g\u00f6rev olu\u015fur. Bunlar\u0131 temizlemek i\u00e7in WP-CLI kullanabilir veya bir eklenti yard\u0131m\u0131yla (WP Control) kontrol edebilirsiniz:<\/p>\n<p><pre><code class=\"language-bash\"># Bekleyen cron g\u00f6revlerini listeleyin<\/p>\n<p>wp cron event list --status=pending<\/p>\n<h1 id=\"tum-cron-gorevlerini-temizleyin-dikkatli-kullanin\">T\u00fcm cron g\u00f6revlerini temizleyin (dikkatli kullan\u0131n!)<\/h1>\n<p>wp cron event delete --all<\/code><\/pre>\n<\/p>\n<p><h3 id=\"n8n-ve-otomasyon-senaryolarinda-timeout-yonetimi\">n8n ve Otomasyon Senaryolar\u0131nda Timeout Y\u00f6netimi<\/h3>\n<\/p>\n<p>E\u011fer WordPress sitenizi n8n, Zapier veya Make gibi otomasyon ara\u00e7lar\u0131yla entegre ettiyseniz, webhook&#8217;lar arac\u0131l\u0131\u011f\u0131yla sitenize gelen istekler de PHP worker&#8217;lar\u0131n\u0131 t\u00fcketebilir. \u00d6zellikle toplu veri senkronizasyonu yapan webhook&#8217;lar, tek seferde y\u00fczlerce API \u00e7a\u011fr\u0131s\u0131 yaparak sunucuyu kilitleyebilir.<\/p>\n<p>Bu t\u00fcr otomasyonlar\u0131 \u00e7al\u0131\u015ft\u0131ran kullan\u0131c\u0131lar i\u00e7in \u00f6zel olarak optimize edilmi\u015f <strong>n8n &amp; Node.js Hosting<\/strong> paketleri, Node.js tabanl\u0131 i\u015flemleri PHP&#8217;den ay\u0131rarak hem WordPress&#8217;inizi hem de otomasyonlar\u0131n\u0131z\u0131 sorunsuz \u00e7al\u0131\u015ft\u0131rman\u0131za olanak tan\u0131r.<\/p>\n<p><h2 id=\"kalici-cozum\">504 Hatas\u0131n\u0131 Tamamen \u00d6nlemek \u0130\u00e7in 5 Kal\u0131c\u0131 Strateji<\/h2>\n<\/p>\n<p><strong>504 gateway timeout hatas\u0131<\/strong> i\u00e7in anl\u0131k \u00e7\u00f6z\u00fcmler \u00fcrettik. Ama as\u0131l mesele, bu hatay\u0131 bir daha asla g\u00f6rmemek. \u0130\u015fte kal\u0131c\u0131 \u00e7\u00f6z\u00fcm i\u00e7in uygulaman\u0131z gereken 5 strateji:<\/p>\n<p><h3 id=\"1-proaktif-izleme-ile-sorunu-olusmadan-yakalayin\">1. Proaktif \u0130zleme ile Sorunu Olu\u015fmadan Yakalay\u0131n<\/h3>\n<\/p>\n<p>UptimeRobot, HetrixTools veya Better Uptime gibi \u00fccretsiz\/uygun fiyatl\u0131 izleme ara\u00e7lar\u0131, sitenizi 30 saniyede bir kontrol eder. 504 hatas\u0131 olu\u015ftu\u011fu an size Telegram, Slack, e-posta veya SMS ile bildirim g\u00f6nderir. Bu sayede sorunu, bir m\u00fc\u015fterinizin size haber vermesinden \u00e7ok \u00f6nce tespit edersiniz.<\/p>\n<p><h3 id=\"2-object-cache-redis-memcached-ile-veritabani-yukunu-azaltin\">2. Object Cache (Redis\/Memcached) ile Veritaban\u0131 Y\u00fck\u00fcn\u00fc Azalt\u0131n<\/h3>\n<\/p>\n<p>Redis Object Cache, veritaban\u0131 sorgular\u0131n\u0131 RAM&#8217;de \u00f6nbelle\u011fe al\u0131r. Bu, \u00f6zellikle yo\u011fun trafikli sitelerde veritaban\u0131 kaynakl\u0131 timeout&#8217;lar\u0131 %90 oran\u0131nda azalt\u0131r. <a href=\"https:\/\/saviorhost.com\/blog\/woocommerce-seo-rehberi-2026\/\" target=\"_blank\">WooCommerce SEO performans\u0131<\/a> i\u00e7in de kritik olan bu teknoloji, sayfa y\u00fcklenme s\u00fcrelerini dramatik \u015fekilde d\u00fc\u015f\u00fcr\u00fcr.<\/p>\n<p><h3 id=\"3-lazy-load-ve-sayfalama-pagination-kullanin\">3. Lazy Load ve Sayfalama (Pagination) Kullan\u0131n<\/h3>\n<\/p>\n<p>Tek seferde 100 \u00fcr\u00fcn y\u00fcklemek yerine 20&#8217;\u015ferli sayfalar kullan\u0131n. G\u00f6rseller i\u00e7in lazy load, videolar i\u00e7in ise &#8220;t\u0131klay\u0131nca oynat&#8221; stratejisi uygulay\u0131n. Bu, her sayfa y\u00fcklemesinde sunucuya binen anl\u0131k y\u00fck\u00fc azalt\u0131r ve PHP worker&#8217;lar\u0131n\u0131n daha verimli kullan\u0131lmas\u0131n\u0131 sa\u011flar.<\/p>\n<p><h3 id=\"4-statik-cache-html-onbellekleme-stratejisi\">4. Statik Cache (HTML \u00d6nbellekleme) Stratejisi<\/h3>\n<\/p>\n<p>WP Rocket, W3 Total Cache veya LiteSpeed Cache gibi eklentiler, dinamik PHP sayfalar\u0131n\u0131z\u0131 statik HTML dosyalar\u0131na d\u00f6n\u00fc\u015ft\u00fcr\u00fcr. Ziyaret\u00e7i statik HTML&#8217;i g\u00f6r\u00fcnt\u00fclerken PHP worker&#8217;\u0131 hi\u00e7 devreye girmez. Bu, ayn\u0131 sunucuda 10 kat daha fazla ziyaret\u00e7iye hizmet verebilmeniz demektir.<\/p>\n<p><h3 id=\"5-dogru-hosting-altyapisini-secin\">5. Do\u011fru Hosting Altyap\u0131s\u0131n\u0131 Se\u00e7in<\/h3>\n<\/p>\n<p>T\u00fcm optimizasyonlar\u0131 yapsan\u0131z bile, altyap\u0131n\u0131z yetersizse <strong>504 gateway timeout hatas\u0131<\/strong> pe\u015finizi b\u0131rakmaz. \u00d6zellikle \u015fu \u00f6zelliklere sahip bir hosting se\u00e7ti\u011finizden emin olun:<\/p>\n<ul>\n<li>NVMe SSD disk (SATA SSD&#8217;den 7 kat daha h\u0131zl\u0131)<\/li>\n<li>AMD Ryzen 9 veya e\u015fde\u011fer y\u00fcksek saat h\u0131zl\u0131 i\u015flemci<\/li>\n<li>Redis\/Memcached deste\u011fi<\/li>\n<li>PHP-FPM worker havuzunun \u00f6zelle\u015ftirilebilir olmas\u0131<\/li>\n<li>HTTP\/2 ve HTTP\/3 deste\u011fi<\/li>\n<\/ul>\n<p><strong>Hosting<\/strong> se\u00e7imi yaparken bu kriterleri g\u00f6z \u00f6n\u00fcnde bulundurmak, 504 sorununu daha ba\u015ftan \u00f6nlemenin en ak\u0131ll\u0131ca yoludur.<\/p>\n<p><p style=\"background:#f0fdf4;border-left:4px solid #22c55e;padding:15px;margin:20px 0;border-radius:6px\"><strong>\u2705 Kal\u0131c\u0131 \u00c7\u00f6z\u00fcm \u00d6zeti:<\/strong> 504 hatas\u0131n\u0131 tamamen hayat\u0131n\u0131zdan \u00e7\u0131karmak i\u00e7in \u015fu \u00fc\u00e7l\u00fcy\u00fc uygulay\u0131n: (1) NVMe SSD&#8217;li y\u00fcksek performansl\u0131 hosting, (2) Redis Object Cache + statik sayfa \u00f6nbellekleme, (3) Ger\u00e7ek cron ile wp-cron&#8217;u devre d\u0131\u015f\u0131 b\u0131rakma. Bu \u00fc\u00e7 ad\u0131m, timeout sorunlar\u0131n\u0131n %95&#8217;ini ortadan kald\u0131r\u0131r.<\/p>\n<\/p>\n<p><h2 id=\"sonuc\">Sonu\u00e7: Sitenizi Gelece\u011fe Haz\u0131rlay\u0131n<\/h2>\n<\/p>\n<p><strong>504 gateway timeout hatas\u0131<\/strong>, WordPress d\u00fcnyas\u0131n\u0131n en korkulan hatalar\u0131ndan biri olabilir. Ama art\u0131k biliyorsunuz ki bu hata, \u00e7\u00f6z\u00fclemez bir muamma de\u011fil; aksine, do\u011fru te\u015fhis ve sistematik bir yakla\u015f\u0131mla tamamen ortadan kald\u0131r\u0131labilecek bir yap\u0131land\u0131rma sorunudur.<\/p>\n<p>Bu rehberde ele ald\u0131\u011f\u0131m\u0131z 11 y\u00f6ntem, 2026 y\u0131l\u0131nda WordPress sitelerinde kar\u015f\u0131la\u015f\u0131lan 504 hatalar\u0131n\u0131n neredeyse tamam\u0131n\u0131 kaps\u0131yor. PHP-FPM timeout ayarlar\u0131ndan Nginx proxy yap\u0131land\u0131rmas\u0131na, Cloudflare optimizasyonundan veritaban\u0131 indekslemeye kadar her a\u015famay\u0131 ad\u0131m ad\u0131m uygulad\u0131\u011f\u0131n\u0131zda, siteniz timeout&#8217;lara kar\u015f\u0131 z\u0131rhlanm\u0131\u015f olacak.<\/p>\n<p>Unutmay\u0131n: Her saniye, bir ziyaret\u00e7inin sitenizden ayr\u0131lma ihtimalidir. Google&#8217;\u0131n ara\u015ft\u0131rmas\u0131na g\u00f6re, sayfa y\u00fcklenme s\u00fcresi 1 saniyeden 3 saniyeye \u00e7\u0131kt\u0131\u011f\u0131nda hemen \u00e7\u0131kma oran\u0131 %32 art\u0131yor (Kaynak: Google Web Vitals Raporu, 2024). 504 hatas\u0131 ise sayfan\u0131n hi\u00e7 y\u00fcklenmemesi demek \u2014 yani %100 kay\u0131p.<\/p>\n<p>E\u011fer \u015fu ana kadar anlatt\u0131klar\u0131m\u0131z\u0131 uygulad\u0131\u011f\u0131n\u0131z halde sorun devam ediyorsa, sorun muhtemelen hosting altyap\u0131n\u0131z\u0131n yetersizli\u011finden kaynaklan\u0131yordur. AMD Ryzen 9 7900 i\u015flemciler, NVMe SSD diskler ve KeyHelp kontrol paneli ile optimize edilmi\u015f <strong>WordPress hosting<\/strong> paketlerimiz, tam da bu t\u00fcr sorunlar\u0131 k\u00f6k\u00fcnden \u00e7\u00f6zmek i\u00e7in tasarland\u0131. PHP-FPM worker havuzlar\u0131, Redis cache, HTTP\/3 deste\u011fi ve 7\/24 uzman deste\u011fi ile sitenizin bir daha asla timeout kurban\u0131 olmamas\u0131n\u0131 sa\u011fl\u0131yoruz.<\/p>\n<p>Hemen \u015fimdi harekete ge\u00e7in. Sitenizi test edin, loglar\u0131n\u0131z\u0131 inceleyin ve bu rehberdeki ad\u0131mlar\u0131 uygulamaya ba\u015flay\u0131n. 504 hatas\u0131n\u0131n sitenize ve i\u015finize verdi\u011fi zarar\u0131 bug\u00fcn sonland\u0131r\u0131n.<\/p>\n<p><h2 id=\"faq\">S\u0131k\u00e7a Sorulan Sorular<\/h2>\n<\/p>\n<p><h3 id=\"504-gateway-timeout-hatasi-nedir-ve-neden-wordpresste-ortaya-cikar\">504 gateway timeout hatas\u0131 nedir ve neden WordPress&#8217;te ortaya \u00e7\u0131kar?<\/h3>\n<\/p>\n<p><strong>504 gateway timeout hatas\u0131<\/strong>, bir proxy sunucunun (Nginx, Apache, Cloudflare) upstream sunucudan (PHP-FPM, web sunucusu) belirli bir s\u00fcre i\u00e7inde yan\u0131t alamad\u0131\u011f\u0131nda d\u00f6nd\u00fcrd\u00fc\u011f\u00fc bir HTTP durum kodudur. WordPress&#8217;te genellikle PHP i\u015flemlerinin \u00e7ok uzun s\u00fcrmesi, veritaban\u0131 sorgular\u0131n\u0131n yava\u015flamas\u0131, PHP-FPM worker&#8217;lar\u0131n\u0131n t\u00fckenmesi veya harici API \u00e7a\u011fr\u0131lar\u0131n\u0131n yan\u0131t vermemesi nedeniyle ortaya \u00e7\u0131kar.<\/p>\n<p><h3 id=\"504-hatasi-ile-502-hatasi-arasindaki-fark-tam-olarak-nedir\">504 hatas\u0131 ile 502 hatas\u0131 aras\u0131ndaki fark tam olarak nedir?<\/h3>\n<\/p>\n<p>502 Bad Gateway hatas\u0131, proxy sunucunun upstream&#8217;den ge\u00e7ersiz veya bozuk bir yan\u0131t ald\u0131\u011f\u0131 anlam\u0131na gelir. \u00d6rne\u011fin PHP-FPM \u00e7\u00f6km\u00fc\u015fse ve Nginx&#8217;e anlams\u0131z bir yan\u0131t d\u00f6n\u00fcyorsa 502 al\u0131rs\u0131n\u0131z. <strong>504 gateway timeout hatas\u0131<\/strong> ise upstream&#8217;den hi\u00e7 yan\u0131t al\u0131namad\u0131\u011f\u0131 anlam\u0131na gelir. PHP-FPM \u00e7al\u0131\u015f\u0131yordur ama i\u015flem \u00e7ok uzun s\u00fcrm\u00fc\u015ft\u00fcr ve proxy &#8220;yeter&#8221; demi\u015ftir. 502 &#8220;bozuk cevap&#8221;, 504 &#8220;cevap yok&#8221; olarak \u00f6zetlenebilir.<\/p>\n<p><h3 id=\"wordpresste-504-hatasini-cozmek-icin-ilk-ne-yapmaliyim\">WordPress&#8217;te 504 hatas\u0131n\u0131 \u00e7\u00f6zmek i\u00e7in ilk ne yapmal\u0131y\u0131m?<\/h3>\n<\/p>\n<p>\u0130lk ad\u0131m, hatan\u0131n herkeste olup olmad\u0131\u011f\u0131n\u0131 kontrol etmektir. Farkl\u0131 bir cihazdan, farkl\u0131 bir a\u011fdan siteyi a\u00e7may\u0131 deneyin. Ard\u0131ndan hosting panelinize giri\u015f yaparak CPU ve RAM kullan\u0131m\u0131n\u0131 kontrol edin. E\u011fer kaynak kullan\u0131m\u0131 normal g\u00f6r\u00fcn\u00fcyorsa, WordPress hata loglar\u0131n\u0131 (debug.log) inceleyin. Bu \u00fc\u00e7 h\u0131zl\u0131 kontrol, sorunun kayna\u011f\u0131n\u0131 tahmin etme s\u00fcrenizi ciddi \u015fekilde k\u0131salt\u0131r.<\/p>\n<p><h3 id=\"cloudflare-kullaniyorum-504-hatasini-nasil-cozebilirim\">Cloudflare kullan\u0131yorum, 504 hatas\u0131n\u0131 nas\u0131l \u00e7\u00f6zebilirim?<\/h3>\n<\/p>\n<p>Cloudflare kaynakl\u0131 timeout hatalar\u0131 genellikle &#8220;Error 524&#8221; olarak g\u00f6r\u00fcn\u00fcr. \u00c7\u00f6z\u00fcm i\u00e7in Cloudflare Development Mode&#8217;u ge\u00e7ici olarak aktif edin, DNS kayd\u0131n\u0131z\u0131 &#8220;DNS Only&#8221; (gri bulut) moduna al\u0131p test edin, Cloudflare IP aral\u0131klar\u0131n\u0131 sunucu g\u00fcvenlik duvar\u0131n\u0131zda beyaz listeye ekleyin ve origin sunucu yan\u0131t s\u00fcrenizi (TTFB) 1 saniyenin alt\u0131na d\u00fc\u015f\u00fcrmeye \u00e7al\u0131\u015f\u0131n. Argo Smart Routing veya Railgun gibi premium \u00f6zellikler de timeout riskini azalt\u0131r.<\/p>\n<p><h3 id=\"php-fpm-worker-havuzu-neden-tukenir-ve-nasil-onlenir\">PHP-FPM worker havuzu neden t\u00fckenir ve nas\u0131l \u00f6nlenir?<\/h3>\n<\/p>\n<p>PHP-FPM worker havuzu, ayn\u0131 anda i\u015flenebilecek maksimum PHP iste\u011fi say\u0131s\u0131n\u0131 belirler. Ani trafik art\u0131\u015f\u0131, uzun s\u00fcren veritaban\u0131 sorgular\u0131, harici API \u00e7a\u011fr\u0131lar\u0131ndaki gecikmeler veya yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f <code>pm.max<em>children<\/code> de\u011feri havuzun t\u00fckenmesine neden olur. \u00c7\u00f6z\u00fcm i\u00e7in <code>pm.max<\/em>children<\/code> de\u011ferini sunucu RAM&#8217;inize uygun \u015fekilde art\u0131r\u0131n (her worker ~80 MB), <code>request<em>terminate<\/em>timeout<\/code> ile uzun s\u00fcren i\u015flemleri zorla sonland\u0131r\u0131n ve Redis Object Cache ile veritaban\u0131 y\u00fck\u00fcn\u00fc azalt\u0131n.<\/p>\n<p><h3 id=\"woocommerce-sitemde-neden-sik-sik-504-hatasi-aliyorum\">WooCommerce sitemde neden s\u0131k s\u0131k 504 hatas\u0131 al\u0131yorum?<\/h3>\n<\/p>\n<p>WooCommerce siteleri, \u00f6zellikle sipari\u015f i\u015fleme, stok kontrol\u00fc ve raporlama s\u0131ras\u0131nda yo\u011fun veritaban\u0131 sorgular\u0131 \u00e7al\u0131\u015ft\u0131r\u0131r. <code>wp<em>postmeta<\/code> tablosundaki indekslenmemi\u015f sorgular, \u00f6deme ge\u00e7idi API&#8217;lar\u0131n\u0131n yava\u015f yan\u0131t vermesi ve tek sayfada \u00e7ok fazla \u00fcr\u00fcn g\u00f6sterilmesi, 504 hatas\u0131n\u0131 tetikler. <code>wp<\/em>postmeta<\/code> tablosuna indeks ekleyin, \u00f6deme ge\u00e7idi timeout s\u00fcrelerini kontrol edin ve \u00fcr\u00fcnleri sayfalara b\u00f6lerek g\u00f6sterin.<\/p>\n<p><h3 id=\"wp-cronu-devre-disi-birakmak-guvenli-midir\">WP-Cron&#8217;u devre d\u0131\u015f\u0131 b\u0131rakmak g\u00fcvenli midir?<\/h3>\n<\/p>\n<p>Evet, WP-Cron&#8217;u devre d\u0131\u015f\u0131 b\u0131rak\u0131p yerine ger\u00e7ek bir sunucu cron&#8217;u kullanmak tamamen g\u00fcvenlidir ve WordPress taraf\u0131ndan da \u00f6nerilen bir y\u00f6ntemdir. <code>wp-config.php<\/code> dosyas\u0131na <code>define(&#039;DISABLE<em>WP<\/em>CRON&#039;, true);<\/code> ekleyerek WP-Cron&#8217;u devre d\u0131\u015f\u0131 b\u0131rakabilir, sunucunuzun cron tablosuna 15 dakikada bir <code>wp-cron.php<\/code>&#8216;yi \u00e7al\u0131\u015ft\u0131racak bir g\u00f6rev ekleyebilirsiniz. Bu y\u00f6ntem, cron i\u015flemlerinin her sayfa y\u00fcklemesinde tetiklenmesini engelleyerek sunucu y\u00fck\u00fcn\u00fc ciddi oranda azalt\u0131r.<\/p>\n<p><h3 id=\"504-hatasini-tamamen-onlemek-mumkun-mudur\">504 hatas\u0131n\u0131 tamamen \u00f6nlemek m\u00fcmk\u00fcn m\u00fcd\u00fcr?<\/h3>\n<\/p>\n<p>Tamamen \u00f6nlemek i\u00e7in %100 garanti vermek zor olsa da, do\u011fru altyap\u0131 ve optimizasyonlarla riski %95&#8217;in \u00fczerinde azaltmak m\u00fcmk\u00fcnd\u00fcr. NVMe SSD&#8217;li y\u00fcksek performansl\u0131 hosting, Redis Object Cache, statik sayfa \u00f6nbellekleme, optimize edilmi\u015f PHP-FPM ayarlar\u0131, ger\u00e7ek cron kullan\u0131m\u0131 ve proaktif izleme ara\u00e7lar\u0131 ile siteniz timeout hatalar\u0131na kar\u015f\u0131 neredeyse ba\u011f\u0131\u015f\u0131kl\u0131k kazan\u0131r.<\/p>\n<p>&lt;!&#8211; FAQ<em>SCHEMA<\/em>START &#8211;&gt;<\/p>\n<p>{&#8220;@context&#8221;:&#8221;https:\/\/schema.org&#8221;,&#8221;@type&#8221;:&#8221;FAQPage&#8221;,&#8221;mainEntity&#8221;:[{&#8220;@type&#8221;:&#8221;Question&#8221;,&#8221;name&#8221;:&#8221;504 gateway timeout hatas\u0131 nedir ve neden WordPress&#8217;te ortaya \u00e7\u0131kar?&#8221;,&#8221;acceptedAnswer&#8221;:{&#8220;@type&#8221;:&#8221;Answer&#8221;,&#8221;text&#8221;:&#8221;504 gateway timeout hatas\u0131, bir proxy sunucunun (Nginx, Apache, Cloudflare) upstream sunucudan (PHP-FPM, web sunucusu) belirli bir s\u00fcre i\u00e7inde yan\u0131t alamad\u0131\u011f\u0131nda d\u00f6nd\u00fcrd\u00fc\u011f\u00fc bir HTTP durum kodudur. WordPress&#8217;te genellikle PHP i\u015flemlerinin \u00e7ok uzun s\u00fcrmesi, veritaban\u0131 sorgular\u0131n\u0131n yava\u015flamas\u0131, PHP-FPM worker&#8217;lar\u0131n\u0131n t\u00fckenmesi veya harici API \u00e7a\u011fr\u0131lar\u0131n\u0131n yan\u0131t vermemesi nedeniyle ortaya \u00e7\u0131kar.&#8221;}},{&#8220;@type&#8221;:&#8221;Question&#8221;,&#8221;name&#8221;:&#8221;504 hatas\u0131 ile 502 hatas\u0131 aras\u0131ndaki fark tam olarak nedir?&#8221;,&#8221;acceptedAnswer&#8221;:{&#8220;@type&#8221;:&#8221;Answer&#8221;,&#8221;text&#8221;:&#8221;502 Bad Gateway hatas\u0131, proxy sunucunun upstream&#8217;den ge\u00e7ersiz veya bozuk bir yan\u0131t ald\u0131\u011f\u0131 anlam\u0131na gelir. 504 gateway timeout hatas\u0131 ise upstream&#8217;<\/p>\n<div class=\"sm-related-posts\" style=\"background:#f8fafc;border:1px solid #e2e8f0;padding:20px;border-radius:8px;margin-top:30px;clear:both\">\n<h3 style=\"margin-top:0;color:#1e293b;font-size:1.25em\" id=\"%f0%9f%94%97-ilgili-icerikler\">\ud83d\udd17 \u0130lgili \u0130\u00e7erikler<\/h3>\n<ul style=\"margin-bottom:0;padding-left:20px\">\n<li><a href=\"https:\/\/saviorhost.com\/blog\/e-ticaret-hosting-nedir-2026da-satislarinizi-artiracak-altyapi-rehberi\/\">E-Ticaret Hosting Nedir? 2026\u2019da Sat\u0131\u015flar\u0131n\u0131z\u0131 Art\u0131racak Altyap\u0131 Rehberi<\/a><\/li>\n<li><a href=\"https:\/\/saviorhost.com\/blog\/linux-web-hosting-rehberi-2026da-maksimum-performans-ve-guvenlik\/\">Linux Web Hosting Rehberi: 2026\u2019da Maksimum Performans ve G\u00fcvenlik<\/a><\/li>\n<li><a href=\"https:\/\/saviorhost.com\/blog\/prestashopta-500-internal-server-error-hatasi-nedenleri-teshis-ve-0-cozum-kilavuzu\/\">PrestaShop\u2019ta \u201c500 Internal Server Error\u201d Hatas\u0131: Nedenleri, Te\u015fhis ve %100 \u00c7\u00f6z\u00fcm K\u0131lavuzu<\/a><\/li>\n<\/ul>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>WordPress 504 Gateway Timeout Hatas\u0131: 2026&#8217;da Sitenizi Kurtaracak 11 Kesin \u00c7\u00f6z\u00fcm Gece yar\u0131s\u0131. Telefonunuza bildirim geliyor: &#8220;Siteniz \u00e7\u00f6kt\u00fc!&#8221; Hemen taray\u0131c\u0131y\u0131&#8230;<\/p>\n","protected":false},"author":1,"featured_media":2675,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[72],"tags":[],"class_list":["post-2670","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress"],"_links":{"self":[{"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/posts\/2670","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/comments?post=2670"}],"version-history":[{"count":2,"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/posts\/2670\/revisions"}],"predecessor-version":[{"id":2680,"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/posts\/2670\/revisions\/2680"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/media\/2675"}],"wp:attachment":[{"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/media?parent=2670"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/categories?post=2670"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/saviorhost.com\/blog\/wp-json\/wp\/v2\/tags?post=2670"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}