{"id":2178,"date":"2026-09-20T12:30:00","date_gmt":"2026-09-20T09:30:00","guid":{"rendered":"https:\/\/narhost.com\/destek\/?p=2178"},"modified":"2026-09-20T18:38:55","modified_gmt":"2026-09-20T15:38:55","slug":"429-too-many-requests-hatasi-nasil-cozulur","status":"publish","type":"post","link":"https:\/\/narhost.com\/destek\/429-too-many-requests-hatasi-nasil-cozulur\/","title":{"rendered":"429 Too Many Requests Hatas\u0131 Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr"},"content":{"rendered":"<p class=\"kb-dogrulama\">Son do\u011frulama: Eyl\u00fcl 2026 \u00b7 cPanel 136 test hesab\u0131nda denendi<\/p>\n<div id=\"hizli-cozum\" class=\"ai-box ai-box--cozum\">\n<p class=\"ai-box-title\">H\u0131zl\u0131 \u00e7\u00f6z\u00fcm<\/p>\n<p><code>429 Too Many Requests<\/code>, sunucunun k\u0131sa s\u00fcrede \u00e7ok fazla istek ald\u0131\u011f\u0131 i\u00e7in iste\u011fi ge\u00e7ici olarak reddetti\u011fi anlam\u0131na gelir; <strong>429 too many requests hatas\u0131<\/strong> \u00e7o\u011fu vakada istek yapan botu, eklentiyi ya da beti\u011fi yava\u015flatmak, hata g\u00fcnl\u00fc\u011f\u00fcnden kayna\u011f\u0131 bulmak ve gerekiyorsa h\u0131z s\u0131n\u0131r\u0131 (rate limit) kural\u0131n\u0131 g\u00f6zden ge\u00e7irmekle \u00e7\u00f6z\u00fcl\u00fcr.<\/p>\n<ol>\n<li>Hatan\u0131n hangi sayfada, hangi i\u015flemde ve ne s\u0131kl\u0131kta \u00e7\u0131kt\u0131\u011f\u0131n\u0131 not edin.<\/li>\n<li>cPanel Hatalar (Error Log) ve ham eri\u015fim kayd\u0131ndan isteklerin kayna\u011f\u0131n\u0131 bulun.<\/li>\n<li>Otomatik istek yapan eklenti, cron ya da harici servisin aral\u0131\u011f\u0131n\u0131 art\u0131r\u0131n.<\/li>\n<li>Kaynak sizden de\u011filse Imunify360 \/ h\u0131z s\u0131n\u0131r\u0131 kural\u0131n\u0131 inceleyin, me\u015fru IP&#8217;yi beyaz listeye al\u0131n.<\/li>\n<\/ol>\n<\/div>\n<table class=\"kb-uyg\">\n<tr>\n<th>Panel<\/th>\n<td>cPanel<\/td>\n<\/tr>\n<tr>\n<th>Sistem<\/th>\n<td>Payla\u015f\u0131ml\u0131 hosting, WordPress, API veya reseller kullan\u0131m\u0131; kendi sunucunuzda web sunucusu h\u0131z s\u0131n\u0131r\u0131<\/td>\n<\/tr>\n<tr>\n<th>Yetki<\/th>\n<td>cPanel kullan\u0131c\u0131s\u0131 ya da WordPress y\u00f6neticisi<\/td>\n<\/tr>\n<tr>\n<th>Narhost \u00fcr\u00fcn\u00fc<\/th>\n<td><a href=\"https:\/\/narhost.com\/web-hosting\" title=\"Web Hosting - Narhost\">Web Hosting<\/a>, WordPress Hosting<\/td>\n<\/tr>\n<\/table>\n<div class=\"kb-once\">\n<p class=\"label\">Ba\u015flamadan \u00f6nce<\/p>\n<ul>\n<li>Hatay\u0131 siz mi, ziyaret\u00e7iler mi yoksa bir uygulama m\u0131 al\u0131yor, belirleyin.<\/li>\n<li>cPanel eri\u015fiminiz olmal\u0131; hata g\u00fcnl\u00fcklerini g\u00f6rmek i\u00e7in gerekir.<\/li>\n<li>\u0130stek yapan bir eklenti ya da betik varsa ge\u00e7ici olarak durdurabilece\u011finizden emin olun.<\/li>\n<li>Yan\u0131tta <code>Retry-After<\/code> ba\u015fl\u0131\u011f\u0131 varsa s\u00fcresini not edin; ne kadar beklemeniz gerekti\u011fini g\u00f6sterir.<\/li>\n<\/ul>\n<\/div>\n<h2>429 Too Many Requests hatas\u0131 ne anlama gelir, neden olur?<\/h2>\n<p>HTTP <a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTTP\/Reference\/Status\/429\" title=\"MDN Web Docs - 429 Too Many Requests durum kodu\" target=\"_blank\" rel=\"noopener\"><code>429<\/code> durum kodu<\/a>, belirli bir zaman aral\u0131\u011f\u0131nda sunucuya g\u00f6nderilen istek say\u0131s\u0131n\u0131n izin verilen s\u0131n\u0131r\u0131 a\u015ft\u0131\u011f\u0131n\u0131 bildirir. Sunucu, kaynaklar\u0131 korumak ve k\u00f6t\u00fcye kullan\u0131m\u0131 \u00f6nlemek i\u00e7in iste\u011fi ge\u00e7ici olarak reddeder ve s\u0131kl\u0131kla yan\u0131ta bir <code>Retry-After<\/code> ba\u015fl\u0131\u011f\u0131 ekler.<\/p>\n<p>Payla\u015f\u0131ml\u0131 hostingde neden genelde \u015fu ba\u015fl\u0131klardan birine \u00e7\u0131kar: bir bot ya da taray\u0131c\u0131 sayfay\u0131 saniyeler i\u00e7inde onlarca kez \u00e7eker; bir WordPress eklentisi, <code>wp-cron<\/code> ya da harici bir servis \u00e7ok s\u0131k istek yapar; ya da g\u00fcvenlik katman\u0131 (\u00f6rne\u011fin Imunify360) tek bir IP&#8217;den gelen yo\u011fun trafi\u011fi h\u0131z s\u0131n\u0131r\u0131yla engeller. <a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc6585.html\" title=\"RFC 6585 - Additional HTTP Status Codes (429)\" target=\"_blank\" rel=\"noopener\">RFC 6585<\/a> bu kodu tam olarak bu ama\u00e7la tan\u0131mlar. Kayna\u011f\u0131 bulmadan yap\u0131lan tahminler sorunu \u00e7\u00f6zmez; \u00f6nce isteklerin nereden geldi\u011fini g\u00f6rmek gerekir.<\/p>\n<figure class=\"nh-sema\"><img src=\"https:\/\/narhost.com\/destek\/wp-content\/uploads\/2026\/09\/429-too-many-requests-hatasi-nasil-cozulur-sema-narhost.webp\" alt=\"429 too many requests hatas\u0131 te\u015fhis ak\u0131\u015f \u015femas\u0131 \u2014 istek h\u0131z\u0131n\u0131 \u00f6l\u00e7me, kayna\u011f\u0131 bulma, h\u0131z\u0131 d\u00fc\u015f\u00fcrme ve h\u0131z s\u0131n\u0131r\u0131 kural\u0131n\u0131 ayarlama ad\u0131mlar\u0131\" width=\"1200\" height=\"500\" loading=\"lazy\" decoding=\"async\"><figcaption>Hata d\u00f6rt ad\u0131mda te\u015fhis edilir: istek h\u0131z\u0131n\u0131 \u00f6l\u00e7me, hata ve eri\u015fim kayd\u0131ndan kayna\u011f\u0131 bulma, istek yapan bile\u015feni yava\u015flatma ve g\u00fcvenlik katman\u0131 kural\u0131n\u0131 g\u00f6zden ge\u00e7irme.<\/figcaption><\/figure>\n<h2>429 too many requests hatas\u0131 nas\u0131l \u00e7\u00f6z\u00fcl\u00fcr \u2014 ad\u0131m ad\u0131m<\/h2>\n<h3>Y\u00f6ntem 1 \u2014 \u0130stek kayna\u011f\u0131n\u0131 hata ve eri\u015fim kayd\u0131ndan bulma<\/h3>\n<ol class=\"kb-adimlar\">\n<li><strong>cPanel \u2192 Metrikler \u2192 Hatalar<\/strong> sayfas\u0131n\u0131 a\u00e7\u0131p son kay\u0131tlara bak\u0131n; ard\u0131ndan <strong>Ham Eri\u015fim<\/strong> g\u00fcnl\u00fc\u011f\u00fcn\u00fc indirip ayn\u0131 IP&#8217;nin ya da yolun k\u0131sa s\u00fcrede ka\u00e7 kez tekrarland\u0131\u011f\u0131n\u0131 inceleyin.\n<p class=\"kb-cikti\">Beklenen sonu\u00e7: isteklerin \u00e7o\u011funu \u00fcreten IP, kullan\u0131c\u0131 arac\u0131s\u0131 (bot) ya da belirli bir yol (\u00f6rne\u011fin <code>xmlrpc.php<\/code>, <code>wp-cron.php<\/code>) ortaya \u00e7\u0131kar.<\/p>\n<\/li>\n<li>Kaynak sizin bir beti\u011finiz ya da eklentiniz de\u011filse ve zararl\u0131 bir bot ise, ilgili IP&#8217;yi cPanel IP Engelleyici&#8217;den engelleyin; ayr\u0131nt\u0131 i\u00e7in <a href=\"https:\/\/narhost.com\/destek\/cpanelde-ip-engelleme\/\" title=\"cPanel&#039;de IP engelleme - Narhost Destek\">cPanel&#8217;de IP engelleme<\/a> kart\u0131na bak\u0131n.\n<p class=\"kb-cikti\">Beklenen sonu\u00e7: yo\u011fun istek yapan kaynak engellenince istek say\u0131s\u0131 d\u00fc\u015fer ve 429 yan\u0131t\u0131 kesilir.<\/p>\n<\/li>\n<\/ol>\n<h3>Y\u00f6ntem 2 \u2014 WordPress&#8217;te istek \u00fcreten bile\u015feni yava\u015flatma<\/h3>\n<p>WordPress&#8217;te en s\u0131k su\u00e7lular <code>wp-cron<\/code>, s\u0131k \u00e7al\u0131\u015fan zamanlanm\u0131\u015f g\u00f6revler ve API&#8217;ye durmadan istek atan eklentilerdir. <code>wp-cron<\/code>&#8216;u ger\u00e7ek bir sunucu cron&#8217;una ta\u015f\u0131mak her ziyarette tetiklenen iste\u011fi azalt\u0131r.<\/p>\n<pre><code class=\"language-php\">\/\/ wp-config.php i\u00e7ine ekleyin\ndefine('DISABLE_WP_CRON', true);<\/code><\/pre>\n<p>Ard\u0131ndan cPanel Cron \u0130\u015fleri&#8217;nden <code>wp-cron.php<\/code>&#8216;yi makul bir aral\u0131kla (\u00f6rne\u011fin 15 dakikada bir) \u00e7al\u0131\u015ft\u0131r\u0131n. Ad\u0131mlar i\u00e7in <a href=\"https:\/\/narhost.com\/destek\/wordpress-wp-cron-devre-disi-birakma\/\" title=\"WordPress wp-cron devre d\u0131\u015f\u0131 b\u0131rakma - Narhost Destek\">wp-cron devre d\u0131\u015f\u0131 b\u0131rakma<\/a> kart\u0131n\u0131 izleyin.<\/p>\n<h3>Y\u00f6ntem 3 \u2014 H\u0131z s\u0131n\u0131r\u0131 ve g\u00fcvenlik kural\u0131n\u0131 g\u00f6zden ge\u00e7irme<\/h3>\n<p>Kaynak me\u015fru bir kullan\u0131c\u0131 ya da kendi API entegrasyonunuzsa ve trafi\u011fi g\u00fcvenlik katman\u0131 s\u0131n\u0131rl\u0131yorsa, cPanel Imunify360 ekran\u0131ndan olay kay\u0131tlar\u0131na bak\u0131p ilgili me\u015fru IP&#8217;yi beyaz listeye ekleyebilirsiniz. Kendi VPS\/VDS sunucunuzda web sunucusu d\u00fczeyinde bir h\u0131z s\u0131n\u0131r\u0131 tan\u0131ml\u0131ysa de\u011feri iste\u011fe g\u00f6re gev\u015fetmek de sizin sorumlulu\u011funuzdad\u0131r. S\u00fcrekli s\u0131n\u0131ra tak\u0131l\u0131yorsan\u0131z kaynak kullan\u0131m\u0131n\u0131z\u0131 da izleyin; <a href=\"https:\/\/narhost.com\/destek\/cpanel-uzerinden-hesap-kaynak-tuketimi-nasil-izlenir\/\" title=\"cPanel \u00fczerinden hesap kaynak t\u00fcketimi izleme - Narhost Destek\">hesap kaynak t\u00fcketimi<\/a> kart\u0131 bu \u00f6l\u00e7\u00fcm\u00fc g\u00f6sterir.<\/p>\n<h2>Do\u011frulama<\/h2>\n<div class=\"success-box\">\n<p class=\"label\">Sonu\u00e7<\/p>\n<p>\u0130stek kayna\u011f\u0131n\u0131 yava\u015flatt\u0131ktan ya da engelledikten sonra sayfay\u0131 yeniden a\u00e7\u0131n; normal i\u00e7erik geliyorsa sorun \u00e7\u00f6z\u00fclm\u00fc\u015ft\u00fcr. Komut sat\u0131r\u0131ndan <code>curl -I https:\/\/siteadresiniz.com\/<\/code> \u00e7al\u0131\u015ft\u0131r\u0131p durum kodunu g\u00f6rebilirsiniz; beklenen sonu\u00e7 200&#8217;d\u00fcr, 429 de\u011fildir. Yan\u0131t h\u00e2l\u00e2 429 ise <code>Retry-After<\/code> ba\u015fl\u0131\u011f\u0131ndaki s\u00fcre kadar bekleyip tekrar deneyin.<\/p>\n<\/div>\n<h2>H\u00e2l\u00e2 \u00e7\u00f6z\u00fclmediyse<\/h2>\n<ul>\n<li><strong>Kayna\u011f\u0131 engellediniz ama hata s\u00fcr\u00fcyor.<\/strong> Birden \u00e7ok IP ya da bir bot a\u011f\u0131 olabilir; eri\u015fim kayd\u0131nda tekrar eden kullan\u0131c\u0131 arac\u0131s\u0131na g\u00f6re <a href=\"https:\/\/narhost.com\/destek\/imunify360-brute-force-koruma\/\" title=\"Imunify360 brute force koruma - Narhost Destek\">Imunify360 brute force korumas\u0131<\/a> kural\u0131n\u0131 s\u0131k\u0131la\u015ft\u0131r\u0131n.<\/li>\n<li><strong>Hata yaln\u0131z yo\u011fun saatlerde \u00e7\u0131k\u0131yor.<\/strong> Hesab\u0131n\u0131z kaynak s\u0131n\u0131r\u0131na yakla\u015f\u0131yor olabilir; <a href=\"https:\/\/narhost.com\/destek\/resource-limit-is-reached-508-hatasi\/\" title=\"Resource Limit Is Reached (508) hatas\u0131 - Narhost Destek\">508 kaynak limiti<\/a> ve <a href=\"https:\/\/narhost.com\/destek\/503-service-unavailable-hatasi-nasil-cozulur\/\" title=\"503 Service Unavailable hatas\u0131 - Narhost Destek\">503 Service Unavailable<\/a> kartlar\u0131na bak\u0131n.<\/li>\n<li><strong>\u0130stekler kendi uygulaman\u0131zdan geliyor.<\/strong> \u0130stemcinizde art arda \u00e7a\u011fr\u0131 yerine bekleme (backoff) ekleyin; <code>Retry-After<\/code> s\u00fcresine uyun ve gereksiz \u00e7a\u011fr\u0131lar\u0131 \u00f6nbelle\u011fe al\u0131n.<\/li>\n<\/ul>\n<div class=\"cta-box\">\n<p class=\"label\">Narhost deste\u011fi<\/p>\n<p>Ad\u0131mlar\u0131 uygulad\u0131ktan sonra hata devam ediyorsa destek talebinize alan ad\u0131n\u0131z\u0131, 429 ald\u0131\u011f\u0131n\u0131z tam URL&#8217;yi, hatan\u0131n ne zaman yo\u011funla\u015ft\u0131\u011f\u0131n\u0131 ve hata g\u00fcnl\u00fc\u011f\u00fcnde g\u00f6rd\u00fc\u011f\u00fcn\u00fcz IP ya da yolu ekleyin.<\/p>\n<p><a class=\"cta-btn\" href=\"https:\/\/narhost.com\/submitticket.php\" title=\"Narhost destek talebi a\u00e7\">Destek talebi a\u00e7<\/a><\/div>\n<div class=\"kb-ilgili\">\n<p class=\"label\">Sonraki ad\u0131mlar<\/p>\n<ul>\n<li><a href=\"https:\/\/narhost.com\/destek\/site-bazen-acilmiyorsa-ne-yapilmali\/\" title=\"Site A\u00e7\u0131lm\u0131yor \u2014 Ad\u0131m Ad\u0131m Te\u015fhis Rehberi - Narhost Destek\">Site A\u00e7\u0131lm\u0131yor \u2014 Ad\u0131m Ad\u0131m Te\u015fhis Rehberi (konu merkezi)<\/a><\/li>\n<li><a href=\"https:\/\/narhost.com\/destek\/web-hosting\/\" title=\"Web Hosting destek kategorisi - Narhost\">Web Hosting destek kategorisi<\/a><\/li>\n<li><a href=\"https:\/\/narhost.com\/destek\/503-service-unavailable-hatasi-nasil-cozulur\/\" title=\"503 Service Unavailable hatas\u0131 - Narhost Destek\">503 Service Unavailable hatas\u0131 nas\u0131l \u00e7\u00f6z\u00fcl\u00fcr<\/a><\/li>\n<li><a href=\"https:\/\/narhost.com\/destek\/401-unauthorized-hatasi-nasil-cozulur\/\" title=\"401 Unauthorized hatas\u0131 nas\u0131l \u00e7\u00f6z\u00fcl\u00fcr - Narhost Destek\">401 Unauthorized hatas\u0131 nas\u0131l \u00e7\u00f6z\u00fcl\u00fcr<\/a><\/li>\n<li><a href=\"https:\/\/narhost.com\/destek\/504-gateway-timeout-hatasi-nasil-cozulur\/\" title=\"504 Gateway Timeout hatas\u0131 nas\u0131l \u00e7\u00f6z\u00fcl\u00fcr - Narhost Destek\">504 Gateway Timeout hatas\u0131 nas\u0131l \u00e7\u00f6z\u00fcl\u00fcr<\/a><\/li>\n<li><a href=\"https:\/\/narhost.com\/destek\/cpanel-hata-gunlukleri-inceleme\/\" title=\"cPanel hata g\u00fcnl\u00fckleri inceleme - Narhost Destek\">cPanel hata g\u00fcnl\u00fcklerini inceleme<\/a><\/li>\n<li><a href=\"https:\/\/narhost.com\/destek\/islemci-cpu-yuku-ve-performansi-nasil-takip-edilir\/\" title=\"\u0130\u015flemci CPU y\u00fck\u00fc ve performans\u0131 takibi - Narhost Destek\">\u0130\u015flemci CPU y\u00fck\u00fc takibi<\/a><\/li>\n<\/ul>\n<\/div>\n<div class=\"kb-faq\">\n<h2>S\u0131k\u00e7a sorulan sorular<\/h2>\n<h3>429 too many requests hatas\u0131 ne kadar s\u00fcrede ge\u00e7er?<\/h3>\n<p>Yan\u0131ttaki <code>Retry-After<\/code> ba\u015fl\u0131\u011f\u0131 ne kadar beklemeniz gerekti\u011fini saniye ya da tarih olarak bildirir. Kaynak trafi\u011fi azald\u0131\u011f\u0131nda hata kendili\u011finden kalkar; kal\u0131c\u0131ysa istek yapan botu ya da beti\u011fi bulup yava\u015flatman\u0131z gerekir.<\/p>\n<h3>429 hatas\u0131 ile 503 hatas\u0131 ayn\u0131 \u015fey mi?<\/h3>\n<p>Hay\u0131r. 429, tek bir istemcinin \u00e7ok fazla istek g\u00f6ndermesiyle ilgilidir; 503 ise sunucunun t\u00fcmden ge\u00e7ici olarak hizmet veremedi\u011fini g\u00f6sterir. \u0130kisinin kayna\u011f\u0131 ve \u00e7\u00f6z\u00fcm\u00fc farkl\u0131d\u0131r, ancak yo\u011fun trafikte birlikte g\u00f6r\u00fclebilir.<\/p>\n<h3>Kendi API iste\u011fim 429 al\u0131yor, ne yapmal\u0131y\u0131m?<\/h3>\n<p>\u0130stemcinizde \u00e7a\u011fr\u0131lar aras\u0131na bekleme (exponential backoff) ekleyin, <code>Retry-After<\/code> s\u00fcresine uyun ve tekrar eden sorgular\u0131 \u00f6nbelle\u011fe al\u0131n. Me\u015fru IP&#8217;nizi g\u00fcvenlik katman\u0131nda beyaz listeye alman\u0131z da gerekebilir.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>429 too many requests hatas\u0131 nedir ve nas\u0131l \u00e7\u00f6z\u00fcl\u00fcr: hata g\u00fcnl\u00fc\u011f\u00fcnden istek kayna\u011f\u0131n\u0131 bulma, wp-cron ve eklentileri yava\u015flatma, IP engelleme ve h\u0131z s\u0131n\u0131r\u0131 kural\u0131n\u0131 g\u00f6zden ge\u00e7irme ad\u0131mlar\u0131.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[179],"class_list":["post-2178","post","type-post","status-publish","format-standard","hentry","category-web-hosting","tag-guvenlik-2"],"meta_box":[],"_links":{"self":[{"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/posts\/2178","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/comments?post=2178"}],"version-history":[{"count":1,"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/posts\/2178\/revisions"}],"predecessor-version":[{"id":2291,"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/posts\/2178\/revisions\/2291"}],"wp:attachment":[{"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/media?parent=2178"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/categories?post=2178"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/narhost.com\/destek\/wp-json\/wp\/v2\/tags?post=2178"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}