{"id":982,"date":"2026-09-28T10:42:22","date_gmt":"2026-09-28T10:42:22","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=982"},"modified":"2026-09-28T09:21:40","modified_gmt":"2026-09-28T09:21:40","slug":"wordpress-dosya-yukleme-limiti-nasil-artirilir","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/wordpress-dosya-yukleme-limiti-nasil-artirilir\/","title":{"rendered":"WordPress Dosya Y\u00fckleme Limiti Nas\u0131l Art\u0131r\u0131l\u0131r?"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">H\u0131zl\u0131 \u00d6zet &#8211; WordPress Dosya Y\u00fckleme Limiti<\/p>\n<p>WordPress dosya y\u00fckleme limiti, PHP ve web sunucusu ayarlar\u0131n\u0131n en d\u00fc\u015f\u00fck olan\u0131yla belirlenir. Limit art\u0131r\u0131l\u0131rken her katman\u0131 ayr\u0131 kontrol edin.<\/p>\n<ul>\n<li><strong>PHP s\u0131n\u0131rlar\u0131n\u0131 art\u0131r\u0131n<\/strong> \u2014 upload_max_filesize ve post_max_size de\u011ferlerini ihtiyaca g\u00f6re y\u00fckseltin.<\/li>\n<li><strong>Nginx&#039;i kontrol edin<\/strong> \u2014 413 hatas\u0131nda client_max_body_size de\u011ferini inceleyin.<\/li>\n<li><strong>Apache&#039;yi do\u011frulay\u0131n<\/strong> \u2014 mod_php kullan\u0131yorsan\u0131z .htaccess veya panel ayarlar\u0131n\u0131 kontrol edin.<\/li>\n<li><strong>Belle\u011fi kar\u0131\u015ft\u0131rmay\u0131n<\/strong> \u2014 memory_limit dosya boyutundan farkl\u0131 olarak PHP i\u015fleminin RAM s\u0131n\u0131r\u0131d\u0131r.<\/li>\n<li><strong>Servisi yenileyin<\/strong> \u2014 PHP-FPM, Apache veya Nginx de\u011fi\u015fiklikten sonra yeniden y\u00fcklenmelidir.<\/li>\n<li><strong>Alt s\u0131n\u0131r\u0131 bulun<\/strong> \u2014 Ger\u00e7ek y\u00fckleme limiti PHP, Nginx, proxy ve panel aras\u0131ndaki en d\u00fc\u015f\u00fck de\u011ferdir.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">WordPress dosya y\u00fckleme limitini y\u00fckseltmek i\u00e7in PHP&#039;de upload_max_filesize ve post_max_size de\u011ferlerini, Nginx kullan\u0131l\u0131yorsa client_max_body_size ayar\u0131n\u0131 birlikte kontrol edin. Servisleri yeniden y\u00fckledikten sonra panelde g\u00f6r\u00fcnen de\u011feri do\u011frulay\u0131n. 413 hatas\u0131 s\u00fcr\u00fcyorsa CDN, proxy veya hosting paketinin s\u0131n\u0131r\u0131n\u0131 inceleyin.<\/p>\n<div class=\"aiw-toc\" style=\"border:1px solid #dbe3ea;border-radius:8px;padding:16px 20px;margin:0 0 28px\">\n<p class=\"aiw-toc-head\"><strong>\u0130\u00e7indekiler<\/strong><span class=\"aiw-toc-meta\"> \u00b7 9 dk okuma<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#wordpress-dosya-yukleme-limiti-neden-dusuk-gorunur\">WordPress dosya y\u00fckleme limiti neden d\u00fc\u015f\u00fck g\u00f6r\u00fcn\u00fcr?<\/a><\/li>\n<li><a href=\"#wordpress-dosya-yukleme-limiti-nasil-ogrenilir\">WordPress dosya y\u00fckleme limiti nas\u0131l \u00f6\u011frenilir?<\/a><\/li>\n<li><a href=\"#php-ini-ile-limit-artirma-adimlari\">php.ini ile limit art\u0131rma ad\u0131mlar\u0131<\/a><\/li>\n<li><a href=\"#nginx-kullanirken-413-hatasi-nasil-cozulur\">Nginx kullan\u0131rken 413 hatas\u0131 nas\u0131l \u00e7\u00f6z\u00fcl\u00fcr?<\/a><\/li>\n<li><a href=\"#apache-htaccess-ve-hosting-paneli-secenekleri\">Apache, .htaccess ve hosting paneli se\u00e7enekleri<\/a><\/li>\n<li><a href=\"#bellek-siniri-ile-yukleme-siniri-ayni-sey-mi\">Bellek s\u0131n\u0131r\u0131 ile y\u00fckleme s\u0131n\u0131r\u0131 ayn\u0131 \u015fey mi?<\/a><\/li>\n<li><a href=\"#degisiklik-neden-etkili-olmadi\">De\u011fi\u015fiklik neden etkili olmad\u0131?<\/a><\/li>\n<li><a href=\"#yuksek-limit-guvenli-mi\">Y\u00fcksek limit g\u00fcvenli mi?<\/a><\/li>\n<li><a href=\"#limit-artirmadan-once-ve-sonra-kontrol-edin\">Limit Art\u0131rmadan \u00d6nce ve Sonra Kontrol Edin<\/a><\/li>\n<li><a href=\"#sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/a><\/li>\n<li><a href=\"#kaynaklar\">Kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"wordpress-dosya-yukleme-limiti-neden-dusuk-gorunur\">WordPress dosya y\u00fckleme limiti neden d\u00fc\u015f\u00fck g\u00f6r\u00fcn\u00fcr?<\/h2>\n<p>WordPress dosya y\u00fckleme limiti tek bir ayardan olu\u015fmaz. PHP i\u00e7indeki <code>upload_max_filesize<\/code> ve <code>post_max_size<\/code>, web sunucusundaki <code>client_max_body_size<\/code>, WordPress bellek s\u0131n\u0131r\u0131 ve hosting paneli ayn\u0131 iste\u011fin farkl\u0131 katmanlar\u0131n\u0131 y\u00f6netir. Bu de\u011ferlerden biri d\u00fc\u015f\u00fck kald\u0131\u011f\u0131nda y\u00fckleme ekran\u0131nda en d\u00fc\u015f\u00fck s\u0131n\u0131r uygulan\u0131r.<\/p>\n<p>Hata mesaj\u0131 da sorunun yerini daralt\u0131r. WordPress&#8217;in &#8220;y\u00fcklenen dosya bu site i\u00e7in izin verilen boyutu a\u015f\u0131yor&#8221; uyar\u0131s\u0131 \u00e7o\u011funlukla PHP veya WordPress ayarlar\u0131n\u0131 g\u00f6sterir. Nginx&#8217;in <code>413 Request Entity Too Large<\/code> yan\u0131t\u0131 ise iste\u011fin PHP&#8217;ye ula\u015fmadan web sunucusunda reddedildi\u011fini anlat\u0131r.<\/p>\n<table>\n<thead>\n<tr>\n<th>Ayar<\/th>\n<th>G\u00f6revi<\/th>\n<th>Kontrol noktas\u0131<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>upload_max_filesize<\/code><\/td>\n<td>Tek bir dosyan\u0131n en y\u00fcksek boyutu<\/td>\n<td>PHP<\/td>\n<\/tr>\n<tr>\n<td><code>post_max_size<\/code><\/td>\n<td>POST iste\u011finin toplam boyutu<\/td>\n<td>PHP<\/td>\n<\/tr>\n<tr>\n<td><code>client_max_body_size<\/code><\/td>\n<td>Nginx istek g\u00f6vdesi s\u0131n\u0131r\u0131<\/td>\n<td>Nginx<\/td>\n<\/tr>\n<tr>\n<td><code>memory_limit<\/code><\/td>\n<td>PHP i\u015fleminin bellek s\u0131n\u0131r\u0131<\/td>\n<td>PHP ve WordPress<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Ne yap\u0131lmal\u0131:<\/strong> \u00d6nce hatay\u0131 ve web iste\u011finde kullan\u0131lan aktif PHP de\u011ferlerini tespit edin. Ard\u0131ndan en d\u00fc\u015f\u00fck kalan katman\u0131 y\u00fckseltin.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">\u0130pucu<\/p>\n<p>\u0130pucu: De\u011fi\u015fiklikten \u00f6nce WordPress panelinde g\u00f6r\u00fcnen mevcut limiti not edin. Ayn\u0131 ekran\u0131 de\u011fi\u015fiklikten sonra yenilemek, ayar\u0131n web taraf\u0131ndaki PHP&#039;ye ula\u015f\u0131p ula\u015fmad\u0131\u011f\u0131n\u0131 h\u0131zl\u0131ca g\u00f6sterir.<\/p>\n<\/div>\n<h2 id=\"wordpress-dosya-yukleme-limiti-nasil-ogrenilir\">WordPress dosya y\u00fckleme limiti nas\u0131l \u00f6\u011frenilir?<\/h2>\n<p>\u0130lk kontrol WordPress y\u00f6netim panelindeki <em>Ortam &gt; Yeni Ekle<\/em> ekran\u0131d\u0131r. WordPress burada izin verilen en y\u00fcksek dosya boyutunu g\u00f6sterir. WooCommerce veya bir form eklentisi farkl\u0131 bir y\u00fckleme alan\u0131 kullan\u0131yorsa o alan\u0131n kendi s\u0131n\u0131r\u0131 da bulunabilir.<\/p>\n<p>SSH eri\u015fiminiz varsa komut sat\u0131r\u0131ndaki PHP&#8217;nin hangi yap\u0131land\u0131rma dosyas\u0131n\u0131 kulland\u0131\u011f\u0131n\u0131 \u00f6\u011frenin:<\/p>\n<pre><code>php --ini\nphp -i | grep -E 'upload_max_filesize|post_max_size|memory_limit'<\/code><\/pre>\n<p>Bu \u00e7\u0131kt\u0131 yaln\u0131zca CLI PHP&#8217;yi g\u00f6sterir. PHP-FPM ile \u00e7al\u0131\u015fan site farkl\u0131 bir <code>php.ini<\/code> dosyas\u0131 kullanabilece\u011fi i\u00e7in CLI de\u011ferleri tek ba\u015f\u0131na yeterli de\u011fildir. Web taraf\u0131ndaki de\u011feri do\u011frulamak i\u00e7in ge\u00e7ici bir PHP bilgi dosyas\u0131 kullan\u0131labilir; kontrol biter bitmez dosyay\u0131 silin.<\/p>\n<pre><code>&lt;?php\nphpinfo();<\/code><\/pre>\n<p>Dosyay\u0131 \u00f6rne\u011fin <code>info.php<\/code> ad\u0131yla yay\u0131n k\u00f6k\u00fcne koyun, taray\u0131c\u0131dan a\u00e7\u0131n ve <code>Loaded Configuration File<\/code> sat\u0131r\u0131n\u0131 kontrol edin. Bu dosya PHP s\u00fcr\u00fcm\u00fc, mod\u00fcller ve yap\u0131land\u0131rma de\u011ferleri hakk\u0131nda ayr\u0131nt\u0131 verir. \u0130nternete a\u00e7\u0131k b\u0131rak\u0131lmas\u0131, sunucu hakk\u0131nda gereksiz bilgi s\u0131zd\u0131r\u0131r.<\/p>\n<p>PHP belgelerinde <code>post_max_size<\/code> de\u011ferinin form verileriyle birlikte dosya y\u00fcklerini de kapsad\u0131\u011f\u0131 belirtilir. Tek dosya s\u0131n\u0131r\u0131n\u0131 128M yap\u0131p toplam POST s\u0131n\u0131r\u0131n\u0131 32M b\u0131rak\u0131rsan\u0131z 128M de\u011feri pratikte kullan\u0131lamaz.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131:<\/strong> Paneldeki de\u011feri, CLI PHP \u00e7\u0131kt\u0131s\u0131n\u0131 ve web iste\u011finde kullan\u0131lan PHP-FPM s\u00fcr\u00fcm\u00fcn\u00fc ayr\u0131 ayr\u0131 do\u011frulay\u0131n.<\/p>\n<h2 id=\"php-ini-ile-limit-artirma-adimlari\">php.ini ile limit art\u0131rma ad\u0131mlar\u0131<\/h2>\n<p>VPS veya y\u00f6netilen bir Linux sunucusunda kal\u0131c\u0131 y\u00f6ntem, ilgili PHP s\u00fcr\u00fcm\u00fcn\u00fcn <code>php.ini<\/code> dosyas\u0131n\u0131 d\u00fczenlemektir. Yol da\u011f\u0131t\u0131ma ve PHP s\u00fcr\u00fcm\u00fcne g\u00f6re de\u011fi\u015fir. Ubuntu \u00fczerinde PHP 8.2 ve PHP-FPM i\u00e7in yayg\u0131n yol \u015f\u00f6yledir:<\/p>\n<pre><code>\/etc\/php\/8.2\/fpm\/php.ini<\/code><\/pre>\n<p>Dosyada a\u015fa\u011f\u0131daki de\u011ferleri sitenin ger\u00e7ek ihtiyac\u0131na g\u00f6re de\u011fi\u015ftirin:<\/p>\n<pre><code>file_uploads = On\nupload_max_filesize = 128M\npost_max_size = 136M\nmemory_limit = 256M\nmax_execution_time = 300\nmax_input_time = 300<\/code><\/pre>\n<p><code>post_max_size<\/code> de\u011ferini <code>upload_max_filesize<\/code> de\u011ferinden biraz y\u00fcksek tutmak genellikle daha g\u00fcvenlidir; form alanlar\u0131 da POST g\u00f6vdesinde yer al\u0131r. 128M&#8217;lik tek dosya i\u00e7in 136M makul bir ba\u015flang\u0131\u00e7t\u0131r. Ayn\u0131 formda birden fazla dosya y\u00fckleniyorsa toplam boyutu ayr\u0131ca hesaplay\u0131n.<\/p>\n<p><code>memory_limit<\/code> diskteki dosya boyutunu belirlemez. WordPress&#8217;in g\u00f6rsel olu\u015fturma, s\u0131k\u0131\u015ft\u0131rma veya eklenti i\u015flemleri s\u0131ras\u0131nda kullanabilece\u011fi PHP belle\u011fini s\u0131n\u0131rlar. PHP-FPM worker say\u0131s\u0131 y\u00fcksekse bu de\u011feri gereksiz art\u0131rmak toplam RAM t\u00fcketimini h\u0131zland\u0131rabilir.<\/p>\n<p>Ayar de\u011fi\u015fikli\u011finden sonra PHP-FPM&#8217;i yeniden y\u00fckleyin:<\/p>\n<pre><code>sudo systemctl reload php8.2-fpm\nsudo systemctl reload nginx<\/code><\/pre>\n<p>Da\u011f\u0131t\u0131m\u0131n\u0131zda servis ad\u0131 farkl\u0131 olabilir. <code>systemctl status php8.2-fpm<\/code> ile do\u011fru birimi do\u011frulay\u0131n. Apache mod_php kullan\u0131l\u0131yorsa PHP-FPM servisini yeniden y\u00fcklemek yerine Apache yap\u0131land\u0131rmas\u0131n\u0131 yenilemeniz gerekebilir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131:<\/strong> De\u011ferleri de\u011fi\u015ftirdikten sonra ilgili PHP-FPM servisini yeniden y\u00fckleyin ve WordPress panelinden yeni s\u0131n\u0131r\u0131 tekrar okuyun.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>Dikkat: upload_max_filesize de\u011ferini art\u0131r\u0131p post_max_size de\u011ferini daha d\u00fc\u015f\u00fck b\u0131rakmay\u0131n. PHP toplam POST iste\u011fi s\u0131n\u0131r\u0131na tak\u0131l\u0131r ve tek dosya i\u00e7in verdi\u011finiz y\u00fcksek de\u011fer kullan\u0131lamaz.<\/p>\n<\/div>\n<h2 id=\"nginx-kullanirken-413-hatasi-nasil-cozulur\">Nginx kullan\u0131rken 413 hatas\u0131 nas\u0131l \u00e7\u00f6z\u00fcl\u00fcr?<\/h2>\n<p>Nginx, PHP&#8217;ye ula\u015fmadan \u00f6nce iste\u011fi reddedebilir. Nginx belgelerinde <code>client_max_body_size<\/code> i\u00e7in varsay\u0131lan de\u011ferin 1 MB oldu\u011fu belirtilir. B\u00fcy\u00fck bir tema, eklenti veya medya dosyas\u0131nda bu de\u011fer a\u015f\u0131l\u0131rsa 413 yan\u0131t\u0131 g\u00f6r\u00fclebilir.<\/p>\n<p>Site yap\u0131land\u0131rmas\u0131ndaki <code>server<\/code> blo\u011funa a\u015fa\u011f\u0131daki sat\u0131r\u0131 ekleyebilirsiniz:<\/p>\n<pre><code>server {\n    server_name example.com www.example.com;\n    client_max_body_size 128M;\n\n    # Di\u011fer site ayarlar\u0131\n}<\/code><\/pre>\n<p>Dosya genellikle <code>\/etc\/nginx\/sites-available\/example.com<\/code> alt\u0131nda bulunur ve <code>sites-enabled<\/code> \u00fczerinden etkinle\u015ftirilir. De\u011fi\u015fikli\u011fi uygulamadan \u00f6nce s\u00f6zdizimini kontrol edin:<\/p>\n<pre><code>sudo nginx -t\nsudo systemctl reload nginx<\/code><\/pre>\n<p><code>nginx -t<\/code> \u00e7\u0131kt\u0131s\u0131nda <code>syntax is ok<\/code> ve <code>test is successful<\/code> g\u00f6rmeden servisi yeniden ba\u015flatmay\u0131n. <code>reload<\/code>, \u00e7al\u0131\u015fan ba\u011flant\u0131lar\u0131 m\u00fcmk\u00fcn oldu\u011funca koruyarak yeni yap\u0131land\u0131rmay\u0131 y\u00fckler.<\/p>\n<p>PHP&#8217;de 128M, Nginx&#8217;te 64M varsa ger\u00e7ek \u00fcst s\u0131n\u0131r 64M olur. Tersi durumda PHP iste\u011fi kabul etse bile dosya y\u00fckleme ba\u015flamadan Nginx reddeder. Reverse proxy veya CDN kullan\u0131l\u0131yorsa aradaki katman\u0131n kendi s\u0131n\u0131r\u0131n\u0131 da kontrol edin.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131:<\/strong> 413 hatas\u0131nda \u00f6nce <code>client_max_body_size<\/code> de\u011ferini, ard\u0131ndan Nginx hata g\u00fcnl\u00fc\u011f\u00fcn\u00fc kontrol edin.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">\u00d6rnek<\/p>\n<p>\u00d6rnek senaryo: PHP ve WordPress 128M kabul ediyor, fakat Nginx 20M s\u0131n\u0131r\u0131nda kal\u0131yorsa 25 MB dosyada 413 hatas\u0131 g\u00f6r\u00fcl\u00fcr. PHP de\u011ferlerini tekrar tekrar de\u011fi\u015ftirmek yerine client_max_body_size ayar\u0131n\u0131 d\u00fczeltmek gerekir.<\/p>\n<\/div>\n<h2 id=\"apache-htaccess-ve-hosting-paneli-secenekleri\">Apache, .htaccess ve hosting paneli se\u00e7enekleri<\/h2>\n<p>Apache ve PHP&#8217;nin nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131 hosting mimarisine g\u00f6re de\u011fi\u015fir. Apache mod_php kullan\u0131lan sistemlerde <code>.htaccess<\/code> i\u00e7ine PHP de\u011ferleri eklenebilir:<\/p>\n<pre><code>php_value upload_max_filesize 128M\nphp_value post_max_size 136M\nphp_value memory_limit 256M\nphp_value max_execution_time 300\nphp_value max_input_time 300<\/code><\/pre>\n<p>Bu direktifler PHP-FPM veya CGI yap\u0131land\u0131rmas\u0131nda desteklenmeyebilir. Yanl\u0131\u015f yerde kullan\u0131ld\u0131\u011f\u0131nda 500 Internal Server Error al\u0131nabilir. B\u00f6yle bir durumda sat\u0131rlar\u0131 geri al\u0131n ve Apache hata g\u00fcnl\u00fc\u011f\u00fcn\u00fc inceleyin.<\/p>\n<p>cPanel ve Plesk gibi panellerde PHP s\u00fcr\u00fcm\u00fc ile <code>upload_max_filesize<\/code>, <code>post_max_size<\/code> ve <code>memory_limit<\/code> de\u011ferleri genellikle aray\u00fczden de\u011fi\u015ftirilebilir. Panelde se\u00e7ilen PHP s\u00fcr\u00fcm\u00fcn\u00fcn sitenin ger\u00e7ekten kulland\u0131\u011f\u0131 s\u00fcr\u00fcm oldu\u011funa dikkat edin. Hosting paneli hakk\u0131nda se\u00e7im yaparken <a href=\"https:\/\/www.vps.tc\/blog\/tr\/cpanel-ve-plesk-farki-hangisini-secmeli\/\">cPanel ve Plesk Fark\u0131: Hangisini Se\u00e7meli?<\/a> kar\u015f\u0131la\u015ft\u0131rmas\u0131ndaki y\u00f6netim modeli ayr\u0131m\u0131 yard\u0131mc\u0131 olabilir.<\/p>\n<p>Baz\u0131 payla\u015f\u0131ml\u0131 hosting paketleri bu ayarlar\u0131 kullan\u0131c\u0131ya kapat\u0131r. <code>php.ini<\/code>, <code>.user.ini<\/code> veya <code>.htaccess<\/code> de\u011fi\u015fikli\u011fi etkisiz kal\u0131yorsa sa\u011flay\u0131c\u0131n\u0131n paket s\u0131n\u0131r\u0131 uygulan\u0131yor olabilir. Bu durumda destek ekibinden izin verilen en y\u00fcksek de\u011ferleri \u00f6\u011frenin.<\/p>\n<p><code>.user.ini<\/code> kullanan PHP kurulumlar\u0131nda \u00f6rnek dosya \u015f\u00f6yledir:<\/p>\n<pre><code>upload_max_filesize=128M\npost_max_size=136M\nmemory_limit=256M<\/code><\/pre>\n<p>PHP&#8217;nin <code>.user.ini<\/code> dosyalar\u0131n\u0131 belirli aral\u0131klarla yeniden okumas\u0131 m\u00fcmk\u00fcnd\u00fcr. De\u011fi\u015fikli\u011fin hemen g\u00f6r\u00fcnmemesi normaldir; PHP-FPM \u00f6nbelle\u011fi veya hosting panelinin uygulama katman\u0131 da devrede olabilir.<\/p>\n<h2 id=\"bellek-siniri-ile-yukleme-siniri-ayni-sey-mi\">Bellek s\u0131n\u0131r\u0131 ile y\u00fckleme s\u0131n\u0131r\u0131 ayn\u0131 \u015fey mi?<\/h2>\n<p>Hay\u0131r. Dosya y\u00fckleme limiti, HTTP iste\u011fiyle kabul edilecek boyutu belirler. WordPress bellek s\u0131n\u0131r\u0131 ise PHP&#8217;nin \u00e7al\u0131\u015fma s\u0131ras\u0131nda kullanabilece\u011fi RAM miktar\u0131yla ilgilidir. B\u00fcy\u00fck bir ZIP dosyas\u0131 \u00e7o\u011funlukla disk alan\u0131 ve istek s\u00fcresi gerektirir. Y\u00fcksek \u00e7\u00f6z\u00fcn\u00fcrl\u00fckl\u00fc bir JPEG&#8217;i yeniden boyutland\u0131rmak ise daha fazla bellek t\u00fcketebilir.<\/p>\n<p>WordPress i\u00e7in <code>wp-config.php<\/code> dosyas\u0131na \u015fu sabitler eklenebilir:<\/p>\n<pre><code>define( 'WP_MEMORY_LIMIT', '256M' );\ndefine( 'WP_MAX_MEMORY_LIMIT', '512M' );<\/code><\/pre>\n<p><code>WP_MEMORY_LIMIT<\/code> normal site i\u015flemlerinde, <code>WP_MAX_MEMORY_LIMIT<\/code> ise y\u00f6netim ekran\u0131 ve baz\u0131 a\u011f\u0131r i\u015flemlerde kullan\u0131l\u0131r. PHP&#8217;nin <code>memory_limit<\/code> de\u011feri daha d\u00fc\u015f\u00fckse WordPress bu s\u0131n\u0131r\u0131 a\u015famaz. Yaln\u0131zca <code>wp-config.php<\/code> de\u011fi\u015ftirerek her bellek hatas\u0131n\u0131 \u00e7\u00f6zemezsiniz.<\/p>\n<p><code>Allowed memory size exhausted<\/code> mesaj\u0131 al\u0131yorsan\u0131z bellek kullan\u0131m\u0131n\u0131, PHP-FPM worker say\u0131s\u0131n\u0131 ve eklentileri inceleyin. WordPress belle\u011fiyle ilgili ayr\u0131 bir kontrol listesi i\u00e7in <a href=\"https:\/\/www.vps.tc\/blog\/tr\/wordpress-bellek-siniri-hatasi-nasil-cozulur\/\">WordPress Bellek S\u0131n\u0131r\u0131 Hatas\u0131 Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr?<\/a> sayfas\u0131na bakabilirsiniz.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131:<\/strong> Y\u00fckleme boyutunu ve PHP belle\u011fini ayr\u0131 metrikler olarak de\u011ferlendirin; birini y\u00fckseltmek di\u011ferini otomatik olarak de\u011fi\u015ftirmez.<\/p>\n<h2 id=\"degisiklik-neden-etkili-olmadi\">De\u011fi\u015fiklik neden etkili olmad\u0131?<\/h2>\n<p>En s\u0131k neden yanl\u0131\u015f PHP s\u00fcr\u00fcm\u00fcn\u00fcn yap\u0131land\u0131r\u0131lmas\u0131d\u0131r. Sunucuda PHP 8.1 ve 8.2 birlikte kurulu olabilir; Nginx sitesi 8.2-FPM&#8217;e ba\u011fl\u0131yken 8.1&#8217;in <code>php.ini<\/code> dosyas\u0131 d\u00fczenlenebilir. Site yap\u0131land\u0131rmas\u0131ndaki socket yolunu kontrol edin:<\/p>\n<pre><code>grep -R \"fastcgi_pass\" \/etc\/nginx\/sites-enabled\/\nps aux | grep php-fpm<\/code><\/pre>\n<p>Bir ba\u015fka ihtimal, ayar\u0131n daha d\u00fc\u015f\u00fck bir katmanda ezilmesidir. Nginx 32M, PHP 128M ise WordPress 32M&#8217;den b\u00fcy\u00fck dosyay\u0131 alamaz. CDN, reverse proxy, g\u00fcvenlik duvar\u0131 veya hosting paneli de iste\u011fi uygulamaya ula\u015fmadan kesebilir.<\/p>\n<p>\u00d6nbellek de kontrol edilmelidir. PHP-FPM yeniden y\u00fcklenmemi\u015f, Apache eski worker&#8217;larla \u00e7al\u0131\u015f\u0131yor veya panel de\u011fi\u015fikli\u011fi hen\u00fcz uygulanmam\u0131\u015f olabilir. WordPress&#8217;in g\u00f6sterdi\u011fi de\u011feri de\u011fi\u015fiklikten \u00f6nce ve sonra not edin; tahmin yerine \u00f6l\u00e7\u00fcm yap\u0131n.<\/p>\n<p>Disk alan\u0131n\u0131 da kontrol edin. B\u00fcy\u00fck dosya i\u00e7in hem ge\u00e7ici y\u00fckleme dizininde hem de WordPress&#8217;in <code>wp-content\/uploads<\/code> yolunda yer gerekir:<\/p>\n<pre><code>df -h\nsudo du -sh \/tmp \/var\/www\/example.com\/wp-content\/uploads<\/code><\/pre>\n<p>\u0130zin sorunlar\u0131 farkl\u0131 bir belirti \u00fcretir. Web sunucusu kullan\u0131c\u0131s\u0131n\u0131n yazma yetkisi yoksa limit art\u0131r\u0131lm\u0131\u015f olsa bile y\u00fckleme tamamlanmaz. Sorunu \u00e7\u00f6zmek i\u00e7in dizinleri rastgele <code>chmod 777<\/code> yapmak g\u00fcvenli de\u011fildir.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">Sahadan not<\/p>\n<p>Bir sunucuda PHP-FPM limitini de\u011fi\u015ftirdim fakat WordPress paneli eski de\u011feri g\u00f6stermeye devam etti. Nginx yap\u0131land\u0131rmas\u0131ndaki fastcgi_pass sat\u0131r\u0131n\u0131n PHP 8.1 socket&#039;ine, d\u00fczenledi\u011fim dosyan\u0131n ise PHP 8.2-FPM&#039;e ait oldu\u011funu fark ettim; socket yolunu d\u00fczelttikten sonra systemctl reload php8.2-fpm ile de\u011feri do\u011frulad\u0131m.<\/p>\n<\/div>\n<h2 id=\"yuksek-limit-guvenli-mi\">Y\u00fcksek limit g\u00fcvenli mi?<\/h2>\n<p>128M veya 512M de\u011feri tek ba\u015f\u0131na g\u00fcvenlik a\u00e7\u0131\u011f\u0131 de\u011fildir; kaynak t\u00fcketimini ve sald\u0131r\u0131 y\u00fczeyini b\u00fcy\u00fctebilir. WordPress yaln\u0131zca izin verilen dosya t\u00fcrlerini kabul etmeli, y\u00f6netici hesaplar\u0131 \u00e7ok fakt\u00f6rl\u00fc kimlik do\u011frulamayla korunmal\u0131 ve y\u00fckleme dizininde \u00e7al\u0131\u015ft\u0131r\u0131labilir betiklerin y\u00fcr\u00fct\u00fclmesi engellenmelidir.<\/p>\n<p>Gere\u011finden y\u00fcksek <code>max_execution_time<\/code> ve <code>max_input_time<\/code> de\u011ferleri, yava\u015f ba\u011flant\u0131lar\u0131n PHP worker&#8217;lar\u0131n\u0131 uzun s\u00fcre me\u015fgul etmesine yol a\u00e7abilir. VPS kaynaklar\u0131 s\u0131n\u0131rl\u0131ysa e\u015fzamanl\u0131 y\u00fcklemeler s\u0131ras\u0131nda CPU, RAM, disk I\/O ve PHP-FPM s\u00fcre\u00e7lerini izleyin.<\/p>\n<p>Medya a\u011f\u0131rl\u0131kl\u0131 sitelerde CDN kullanmak dosya y\u00fckleme limitini ortadan kald\u0131rmaz; CDN \u00e7o\u011funlukla da\u011f\u0131t\u0131m\u0131 h\u0131zland\u0131r\u0131r. \u0130\u00e7eri\u011fin uygulamaya y\u00fcklenmesi s\u0131ras\u0131nda origin sunucunun PHP ve web sunucusu s\u0131n\u0131rlar\u0131 ge\u00e7erlili\u011fini korur. WordPress&#8217;in VPS \u00fczerinde kurulumu i\u00e7in <a href=\"https:\/\/www.vps.tc\/blog\/tr\/vpste-wordpress-kurulumu-adim-adim\/\">VPS&#8217;te WordPress Kurulumu: Ad\u0131m Ad\u0131m Rehber<\/a>, Nginx yap\u0131land\u0131rmas\u0131 i\u00e7in <a href=\"https:\/\/www.vps.tc\/blog\/tr\/ubuntu-nginx-kurulumu-ilk-yapilandirma\/\">Ubuntu&#8217;da Nginx Kurulumu ve \u0130lk Yap\u0131land\u0131rma<\/a> ilgili altyap\u0131 ad\u0131mlar\u0131n\u0131 a\u00e7\u0131klar.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131:<\/strong> \u0130htiya\u00e7 duyulan en y\u00fcksek dosya boyutunu belirleyin, limiti bunun biraz \u00fczerine \u00e7\u0131kar\u0131n ve b\u00fcy\u00fck y\u00fcklemeleri loglarla izleyin.<\/p>\n<h2 id=\"limit-artirmadan-once-ve-sonra-kontrol-edin\">Limit Art\u0131rmadan \u00d6nce ve Sonra Kontrol Edin<\/h2>\n<ul class=\"aiw-checklist\">\n<li>\u0130htiyac\u0131n\u0131z olan en b\u00fcy\u00fck dosya boyutunu belirleyin.<\/li>\n<li>WordPress panelindeki mevcut y\u00fckleme limitini not edin.<\/li>\n<li>PHP&#039;nin web taraf\u0131nda kulland\u0131\u011f\u0131 php.ini dosyas\u0131n\u0131 bulun.<\/li>\n<li>upload_max_filesize ve post_max_size de\u011ferlerini birlikte y\u00fckseltin.<\/li>\n<li>Nginx veya Apache yap\u0131land\u0131rmas\u0131ndaki istek s\u0131n\u0131r\u0131n\u0131 kontrol edin.<\/li>\n<li>PHP-FPM ya da web sunucusunu g\u00fcvenli bi\u00e7imde yeniden y\u00fckleyin.<\/li>\n<li>Yeni de\u011ferle k\u00fc\u00e7\u00fck ve b\u00fcy\u00fck bir test dosyas\u0131 y\u00fckleyip loglar\u0131 inceleyin.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>\u0130htiyac\u0131n\u0131z olan en b\u00fcy\u00fck dosya boyutunu \u00f6l\u00e7erek yaln\u0131zca gerekli katmanlar\u0131 de\u011fi\u015ftirin. Bir sonraki y\u00fcklemede panel de\u011ferini ve sunucu logunu birlikte kontrol etmek, s\u0131n\u0131r\u0131n nerede kald\u0131\u011f\u0131n\u0131 h\u0131zl\u0131ca g\u00f6sterecektir.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/tr\/vps\">VPS paketlerini inceleyin<\/a><\/p>\n<\/div>\n<h2 id=\"sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/h2>\n<div class=\"aiw-faq\">\n<details class=\"aiw-faq-item\" open>\n<summary>WordPress dosya y\u00fckleme limiti en fazla ka\u00e7 MB olmal\u0131?<\/summary>\n<p>Sabit bir do\u011fru de\u011fer yoktur. Sitenin en b\u00fcy\u00fck tema, eklenti veya medya dosyas\u0131n\u0131 belirleyip bunun biraz \u00fczerine \u00e7\u0131k\u0131n. 128M bir\u00e7ok medya sitesi i\u00e7in yeterli olabilir; b\u00fcy\u00fck yedek veya video dosyalar\u0131 i\u00e7in daha y\u00fcksek de\u011fer gerekebilir. Gereksiz \u015fekilde 1G gibi limitler belirlemek PHP worker kaynak t\u00fcketimini art\u0131rabilir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>WordPress y\u00fckleme limiti art\u0131r\u0131lm\u0131yorsa ne yap\u0131lmal\u0131?<\/summary>\n<p>\u00d6nce web taraf\u0131nda kullan\u0131lan PHP s\u00fcr\u00fcm\u00fcn\u00fc ve php.ini dosyas\u0131n\u0131 do\u011frulay\u0131n. Ard\u0131ndan Nginx&#039;te client_max_body_size, Apache&#039;de ilgili PHP ayarlar\u0131 ve varsa CDN veya reverse proxy s\u0131n\u0131r\u0131n\u0131 kontrol edin. Hosting paketi kullan\u0131c\u0131 de\u011fi\u015fikliklerini k\u0131s\u0131tl\u0131yor olabilir. Panel eski de\u011feri g\u00f6steriyorsa PHP-FPM veya Apache yeniden y\u00fcklenmemi\u015f olabilir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>413 Request Entity Too Large hatas\u0131 neden olur?<\/summary>\n<p>413 hatas\u0131, HTTP iste\u011finin web sunucusunda tan\u0131mlanan g\u00f6vde boyutunu a\u015fmas\u0131yla olu\u015fur. Nginx kullan\u0131yorsan\u0131z server veya location blo\u011fundaki client_max_body_size de\u011ferini kontrol edin. PHP upload_max_filesize de\u011feri y\u00fcksek olsa bile Nginx daha d\u00fc\u015f\u00fck s\u0131n\u0131r uyguluyorsa dosya PHP&#039;ye ula\u015fmadan reddedilir. De\u011fi\u015fiklikten sonra nginx -t ile s\u00f6zdizimini do\u011frulay\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>upload_max_filesize ile post_max_size aras\u0131ndaki fark nedir?<\/summary>\n<p>upload_max_filesize tek bir dosyan\u0131n en y\u00fcksek boyutunu belirler. post_max_size ise dosyalar, form alanlar\u0131 ve di\u011fer POST verileri dahil olmak \u00fczere t\u00fcm iste\u011fin toplam boyutunu s\u0131n\u0131rlar. Bu nedenle post_max_size genellikle upload_max_filesize de\u011ferinden y\u00fcksek tutulur. Bir formda birden fazla dosya y\u00fckleniyorsa toplam boyutu ayr\u0131ca hesaplay\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>WordPress dosya y\u00fckleme limiti .htaccess ile art\u0131r\u0131l\u0131r m\u0131?<\/summary>\n<p>Apache mod_php kullan\u0131l\u0131yorsa .htaccess i\u00e7inde php_value direktifleriyle baz\u0131 PHP de\u011ferleri de\u011fi\u015ftirilebilir. PHP-FPM, CGI veya hosting taraf\u0131ndan k\u0131s\u0131tlanm\u0131\u015f sistemlerde bu y\u00f6ntem \u00e7al\u0131\u015fmayabilir ve 500 hatas\u0131na yol a\u00e7abilir. Sat\u0131r eklemeden \u00f6nce PHP \u00e7al\u0131\u015fma modelini \u00f6\u011frenin. cPanel gibi panellerde ayn\u0131 ayarlar\u0131 aray\u00fczden de\u011fi\u015ftirmek daha g\u00fcvenli olabilir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>WordPress dosya y\u00fckleme limiti ile bellek s\u0131n\u0131r\u0131 ayn\u0131 m\u0131?<\/summary>\n<p>Ayn\u0131 de\u011fildir. Dosya y\u00fckleme limiti HTTP iste\u011finin kabul edilecek boyutunu, memory_limit ise PHP i\u015fleminin kullanabilece\u011fi RAM miktar\u0131n\u0131 belirler. B\u00fcy\u00fck bir dosya y\u00fcklemek ile o dosyay\u0131 yeniden boyutland\u0131rmak farkl\u0131 kaynaklar t\u00fcketebilir. Bellek hatas\u0131nda PHP loglar\u0131n\u0131, eklentileri ve PHP-FPM kaynak kullan\u0131m\u0131n\u0131 inceleyin; yaln\u0131zca y\u00fckleme limitini art\u0131rmak sorunu \u00e7\u00f6zmez.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"kaynaklar\">Kaynaklar<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/www.php.net\/manual\/en\/ini.core.php\" target=\"_blank\" rel=\"noopener\">PHP Manual &#8211; Core php.ini Directives<\/a> \u2014 php.net<\/li>\n<li><a href=\"https:\/\/nginx.org\/en\/docs\/http\/ngx_http_core_module.html#client_max_body_size\" target=\"_blank\" rel=\"noopener\">Nginx &#8211; client_max_body_size<\/a> \u2014 nginx.org<\/li>\n<li><a href=\"https:\/\/developer.wordpress.org\/apis\/wp-config-php\/\" target=\"_blank\" rel=\"noopener\">WordPress Developer Resources &#8211; wp-config.php<\/a> \u2014 developer.wordpress.org<\/li>\n<li><a href=\"https:\/\/developer.wordpress.org\/advanced-administration\/wordpress\/wp-config\/\" target=\"_blank\" rel=\"noopener\">WordPress.org &#8211; wp-config.php Configuration<\/a> \u2014 developer.wordpress.org<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>WordPress dosya y\u00fckleme limitini PHP, Nginx, Apache veya hosting paneli \u00fczerinden art\u0131rma ad\u0131mlar\u0131n\u0131; 413 hatas\u0131 ve bellek s\u0131n\u0131r\u0131yla birlikte a\u00e7\u0131kl\u0131yoruz.<\/p>\n","protected":false},"author":2,"featured_media":980,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[666],"tags":[],"class_list":["post-982","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cms"],"lang":"tr","translations":{"tr":982,"en":983},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/982","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=982"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/982\/revisions"}],"predecessor-version":[{"id":984,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/982\/revisions\/984"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/980"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=982"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=982"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=982"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}