{"id":522,"date":"2026-09-06T09:15:53","date_gmt":"2026-09-06T09:15:53","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=522"},"modified":"2026-09-06T00:36:43","modified_gmt":"2026-09-06T00:36:43","slug":"err-connection-reset-hatasi-nedir-nasil-cozulur","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/err-connection-reset-hatasi-nedir-nasil-cozulur\/","title":{"rendered":"ERR_CONNECTION_RESET Hatas\u0131 Nedir ve Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr?"},"content":{"rendered":"
\u0130\u00e7indekiler<\/strong><\/p>\n
    \n
  1. ERR_CONNECTION_RESET hatas\u0131 nedir?<\/a><\/li>\n
  2. ERR_CONNECTION_RESET neden olur?<\/a><\/li>\n
  3. Site mi, internet ba\u011flant\u0131s\u0131 m\u0131 sorunlu nas\u0131l anla\u015f\u0131l\u0131r?<\/a><\/li>\n
  4. ERR_CONNECTION_RESET sunucu taraf\u0131nda nas\u0131l \u00e7\u00f6z\u00fcl\u00fcr?<\/a><\/li>\n
  5. Taray\u0131c\u0131da ve bilgisayarda hangi ad\u0131mlar denenebilir?<\/a><\/li>\n
  6. Bir IPv6 hatas\u0131n\u0131 nas\u0131l ay\u0131rt ederim?<\/a><\/li>\n
  7. Proxy, VPN ve MTU ba\u011flant\u0131y\u0131 neden s\u0131f\u0131rlayabilir?<\/a><\/li>\n
  8. Hosting m\u00fc\u015fterileri i\u00e7in kontrol s\u0131ras\u0131<\/a><\/li>\n
  9. Hangi \u00e7\u00f6z\u00fcm ne zaman i\u015fe yarar?<\/a><\/li>\n
  10. S\u0131k Sorulan Sorular<\/a><\/li>\n
  11. Kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n

    ERR_CONNECTION_RESET hatas\u0131 nedir?<\/h2>\n

    ERR_CONNECTION_RESET<\/code>, taray\u0131c\u0131 ile web sunucusu aras\u0131ndaki TCP ba\u011flant\u0131s\u0131n\u0131n veri aktar\u0131m\u0131 tamamlanmadan kapat\u0131ld\u0131\u011f\u0131n\u0131 g\u00f6sterir. Kapatma i\u015flemini sunucu, g\u00fcvenlik duvar\u0131, proxy, VPN, DNS y\u00f6nlendirmesi, a\u011f cihaz\u0131 veya istemci taraf\u0131ndaki bir yaz\u0131l\u0131m ba\u015flatm\u0131\u015f olabilir. Hata yaln\u0131zca bir siteyi etkiliyorsa sunucu ve DNS taraf\u0131na, t\u00fcm sitelerde g\u00f6r\u00fcl\u00fcyorsa yerel a\u011fa odaklan\u0131r\u0131m.<\/p>\n

    Chrome ve Chromium tabanl\u0131 taray\u0131c\u0131lar bu ifadeyi, ba\u011flant\u0131n\u0131n beklenmedik bi\u00e7imde s\u0131f\u0131rland\u0131\u011f\u0131n\u0131 anlatmak i\u00e7in kullan\u0131r. Bu, sunucunun kesin olarak kapal\u0131 oldu\u011fu anlam\u0131na gelmez. TCP ba\u011flant\u0131s\u0131 kurulmu\u015f olabilir; ard\u0131ndan u\u00e7lardan biri ya da aradaki bir a\u011f cihaz\u0131 RST<\/code> paketi g\u00f6ndererek oturumu sonland\u0131rm\u0131\u015f olabilir.<\/p>\n

    HTTP katman\u0131na ula\u015fmadan \u00f6nce ba\u011flant\u0131 kopabildi\u011fi i\u00e7in web sunucusunun eri\u015fim logunda hi\u00e7 kay\u0131t g\u00f6r\u00fcnmeyebilir. Bu ayr\u0131m benim i\u00e7in \u00f6nemli. Log yoksa hemen nginx yap\u0131land\u0131rmas\u0131na sar\u0131lmak yerine DNS, IPv4 ve IPv6, g\u00fcvenlik duvar\u0131 ve a\u011f yolunu kontrol ederim.<\/p>\n

    ERR_CONNECTION_RESET neden olur?<\/h2>\n

    Hatan\u0131n ad\u0131 taray\u0131c\u0131dan geliyor, fakat sebep \u00e7o\u011fu zaman taray\u0131c\u0131n\u0131n i\u00e7inde bulunmuyor. A\u015fa\u011f\u0131daki tablo, ilk bak\u0131\u015fta hangi katmana y\u00f6nelmem gerekti\u011fini g\u00f6steriyor.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
    Olas\u0131 neden<\/th>\nTipik belirti<\/th>\n\u0130lk kontrol<\/th>\n<\/tr>\n<\/thead>\n
    Sunucu servisi \u00e7al\u0131\u015fm\u0131yor<\/td>\nSite hi\u00e7bir a\u011fdan a\u00e7\u0131lmaz<\/td>\nsystemctl status nginx<\/code> ve dinleyen portlar<\/td>\n<\/tr>\n
    G\u00fcvenlik duvar\u0131 veya WAF<\/td>\nBaz\u0131 IP’lerden eri\u015fim kesilir<\/td>\nnftables, fail2ban ve WAF loglar\u0131<\/td>\n<\/tr>\n
    Yanl\u0131\u015f proxy yap\u0131land\u0131rmas\u0131<\/td>\nProxy arkas\u0131ndaki uygulamada kopma g\u00f6r\u00fcl\u00fcr<\/td>\nnginx error log ve upstream ba\u011flant\u0131s\u0131<\/td>\n<\/tr>\n
    IPv6 problemi<\/td>\nIPv6 kullanan istemcilerde sorun vard\u0131r, IPv4 kullananlarda yoktur<\/td>\ncurl -4<\/code> ve curl -6<\/code> kar\u015f\u0131la\u015ft\u0131rmas\u0131<\/td>\n<\/tr>\n
    VPN, modem veya ISS<\/td>\nAyn\u0131 site mobil veride a\u00e7\u0131l\u0131r<\/td>\nVPN’i kapatmak ve farkl\u0131 a\u011fdan denemek<\/td>\n<\/tr>\n
    MTU veya a\u011f yolu sorunu<\/td>\nK\u00fc\u00e7\u00fck istekler \u00e7al\u0131\u015f\u0131r, baz\u0131 HTTPS istekleri kopar<\/td>\nmtr<\/code>, paket boyutu ve t\u00fcnel ayarlar\u0131<\/td>\n<\/tr>\n
    Taray\u0131c\u0131 uzant\u0131s\u0131 veya bozuk \u00f6nbellek<\/td>\nGizli pencerede sayfa a\u00e7\u0131l\u0131r<\/td>\nUzant\u0131lar\u0131 kapatmak ve geli\u015ftirici ara\u00e7lar\u0131n\u0131 denemek<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    RFC 9293’te tan\u0131mlanan TCP davran\u0131\u015f\u0131nda RST<\/code>, mevcut bir ba\u011flant\u0131n\u0131n beklenmedik bi\u00e7imde sonland\u0131r\u0131lmas\u0131nda kullan\u0131lan kontrol bitlerinden biridir. Taray\u0131c\u0131n\u0131n g\u00f6sterdi\u011fi hata bu a\u011f olay\u0131n\u0131n kullan\u0131c\u0131 aray\u00fcz\u00fcndeki kar\u015f\u0131l\u0131\u011f\u0131d\u0131r. “Reset atan kesinlikle web sunucusudur” demek bu y\u00fczden fazla iddial\u0131 olur.<\/p>\n

    Site mi, internet ba\u011flant\u0131s\u0131 m\u0131 sorunlu nas\u0131l anla\u015f\u0131l\u0131r?<\/h2>\n

    \u00d6nce sorunun kapsam\u0131n\u0131 daralt\u0131n. Ayn\u0131 alan ad\u0131n\u0131 telefondaki mobil veriyle, ba\u015fka bir Wi-Fi ba\u011flant\u0131s\u0131yla ve m\u00fcmk\u00fcnse farkl\u0131 bir cihazla a\u00e7\u0131n. Yaln\u0131zca kendi bilgisayar\u0131n\u0131zda g\u00f6r\u00fcl\u00fcyorsa taray\u0131c\u0131, yerel DNS, VPN veya g\u00fcvenlik yaz\u0131l\u0131m\u0131 \u00f6ne \u00e7\u0131kar. Farkl\u0131 a\u011flarda da g\u00f6r\u00fcl\u00fcyorsa sunucu, DNS veya hosting taraf\u0131n\u0131 incelemek gerekir.<\/p>\n

    Terminalde ilk bakt\u0131\u011f\u0131m \u00e7\u0131kt\u0131lar genellikle dig<\/code> ve curl<\/code> olur:<\/p>\n

    dig +short A example.com\ndig +short AAAA example.com\ncurl -IvsS --connect-timeout 10 https:\/\/example.com\/<\/code><\/pre>\n
    \u0130lk iki sat\u0131r IPv4 ve IPv6 adreslerini g\u00f6sterir. curl<\/code> \u00e7\u0131kt\u0131s\u0131nda hangi adrese ba\u011flan\u0131ld\u0131\u011f\u0131n\u0131, TLS g\u00f6r\u00fc\u015fmesinin ba\u015flay\u0131p ba\u015flamad\u0131\u011f\u0131n\u0131 ve ba\u011flant\u0131n\u0131n nerede kesildi\u011fini g\u00f6rebilirsiniz. -I<\/code> yaln\u0131zca HTTP ba\u015fl\u0131klar\u0131n\u0131 ister; -v<\/code> ise te\u015fhis i\u00e7in ayr\u0131nt\u0131l\u0131 ba\u011flant\u0131 bilgisini a\u00e7ar.<\/p>\n
    IPv4 ve IPv6’y\u0131 ayr\u0131ca deneyin:<\/p>\n
    curl -4Iv https:\/\/example.com\/\ncurl -6Iv https:\/\/example.com\/<\/code><\/pre>\n
    curl -4<\/code> ba\u015far\u0131l\u0131, curl -6<\/code> reset ile bitiyorsa A kayd\u0131 ve IPv4 yolu sa\u011flamken AAAA kayd\u0131, IPv6 y\u00f6nlendirmesi veya sunucunun IPv6 dinleme ayar\u0131 sorunlu olabilir. Taray\u0131c\u0131 bazen IPv6’y\u0131 se\u00e7ti\u011fi i\u00e7in hata yaln\u0131zca belirli ba\u011flant\u0131larda g\u00f6r\u00fcn\u00fcr.<\/p>\n
    DNS \u00e7\u00f6z\u00fcl\u00fcyor ama ba\u011flant\u0131 kurulam\u0131yorsa<\/h3>\n
    DNS’in do\u011fru IP’yi d\u00f6nd\u00fcrmesi, o IP’deki 443 portunun eri\u015filebilir oldu\u011fu anlam\u0131na gelmez. Alan ad\u0131, eski bir sunucunun adresine veya yanl\u0131\u015f bir AAAA kayd\u0131na gidiyor olabilir. DNS TTL s\u00fcresi dolana kadar baz\u0131 istemciler eski cevab\u0131 \u00f6nbelle\u011finde tutabilir; her hatay\u0131 “DNS yay\u0131lmas\u0131” diye a\u00e7\u0131klamak yine de do\u011fru de\u011fildir.<\/p>\n
    Sunucunun kendi taraf\u0131ndan dinleyen portlar\u0131 kontrol ederim:<\/p>\n
    sudo ss -lntp | grep -E ':(80|443)'\nsudo systemctl status nginx --no-pager<\/code><\/pre>\n
    Burada 0.0.0.0:443<\/code> IPv4 \u00fczerinde, [::]:443<\/code> ise IPv6 \u00fczerinde dinleme oldu\u011funu g\u00f6sterebilir. Yaln\u0131zca birini g\u00f6r\u00fcyorsan\u0131z DNS kay\u0131tlar\u0131 ile servis dinleme adreslerinin ayn\u0131 protokol\u00fc destekleyip desteklemedi\u011fine bak\u0131n.<\/p>\n
    ERR_CONNECTION_RESET sunucu taraf\u0131nda nas\u0131l \u00e7\u00f6z\u00fcl\u00fcr?<\/h2>\n
    Sunucuya SSH ile eri\u015febiliyorsan\u0131z \u00e7\u00f6z\u00fcm\u00fc rastgele servis yeniden ba\u015flatmakla ba\u015flatmay\u0131n. \u00d6nce semptomu ve zaman\u0131 kaydedin. Log okumadan yeniden ba\u015flatmak problemi gizleyebilir; \u00f6zellikle ba\u011flant\u0131 say\u0131s\u0131, kernel mesaj\u0131 veya WAF engeli gibi ge\u00e7ici kan\u0131tlar kaybolabilir.<\/p>\n
    1. Nginx veya Apache loglar\u0131n\u0131 inceleyin<\/h3>\n
    Nginx kullan\u0131yorsan\u0131z alan ad\u0131na ait eri\u015fim ve hata loglar\u0131n\u0131 izleyin:<\/p>\n
    sudo tail -f \/var\/log\/nginx\/access.log \/var\/log\/nginx\/error.log<\/code><\/pre>\n
    \u0130stek eri\u015fim logunda olu\u015fuyor, fakat istemci reset al\u0131yorsa sorun proxy, upstream uygulama veya yan\u0131t \u00fcretimi s\u0131ras\u0131nda olabilir. Hi\u00e7 kay\u0131t olu\u015fmuyorsa trafik nginx’e ula\u015fmadan \u00f6nce kesiliyor olabilir. Apache kullanan sistemlerde da\u011f\u0131t\u0131ma g\u00f6re \/var\/log\/apache2\/<\/code> veya \/var\/log\/httpd\/<\/code> alt\u0131n\u0131 kontrol edin.<\/p>\n
    Son hata kay\u0131tlar\u0131n\u0131 daha kontroll\u00fc g\u00f6rmek i\u00e7in:<\/p>\n
    sudo journalctl -u nginx --since '15 minutes ago' --no-pager\nsudo nginx -t<\/code><\/pre>\n
    nginx -t<\/code> yap\u0131land\u0131rma s\u00f6zdizimini do\u011frular; mevcut ba\u011flant\u0131lar\u0131n neden koptu\u011funu a\u00e7\u0131klamaz. Test ge\u00e7se bile upstream uygulamas\u0131 \u00e7\u00f6km\u00fc\u015f, dosya tan\u0131t\u0131c\u0131s\u0131 s\u0131n\u0131r\u0131 dolmu\u015f veya kernel ba\u011flant\u0131lar\u0131 reddediyor olabilir.<\/p>\n
    2. Uygulama servisini ve upstream ba\u011flant\u0131s\u0131n\u0131 kontrol edin<\/h3>\n
    Reverse proxy arkas\u0131nda \u00e7al\u0131\u015fan PHP-FPM, Node.js, Python veya ba\u015fka bir uygulama yan\u0131t vermiyorsa nginx istemciye beklenmeyen bir hata d\u00f6nd\u00fcrebilir. Uygulama portunu ve servis durumunu ayr\u0131 kontrol edin:<\/p>\n
    sudo ss -lntp\nsudo systemctl --failed\nsudo journalctl -u php8.2-fpm --since '30 minutes ago' --no-pager<\/code><\/pre>\n
    Buradaki servis ad\u0131 sisteminizde farkl\u0131 olabilir. Ubuntu \u00fczerinde PHP s\u00fcr\u00fcm\u00fcne g\u00f6re php8.1-fpm<\/code> veya php8.3-fpm<\/code> g\u00f6rmeniz normaldir. Nginx’in proxy_pass<\/code> ya da fastcgi_pass<\/code> hedefi ger\u00e7ekten dinleyen soket veya porta i\u015faret etmeli.<\/p>\n
    3. G\u00fcvenlik duvar\u0131 ve fail2ban kay\u0131tlar\u0131na bak\u0131n<\/h3>\n
    Tek bir istemcinin ba\u011flant\u0131s\u0131 kesiliyor, ba\u015fka bir a\u011fdan site a\u00e7\u0131l\u0131yorsa engelleme ihtimali y\u00fckselir. SSH portunu de\u011fi\u015ftirmeyi g\u00fcvenlik \u00e7\u00f6z\u00fcm\u00fc saymam; fail2ban ve nftables kurallar\u0131n\u0131 ger\u00e7ekten okumak, yanl\u0131\u015f engellemeyi buldurur.<\/p>\n
    sudo nft list ruleset\nsudo fail2ban-client status\nsudo fail2ban-client status sshd<\/code><\/pre>\n
    \u00dcretim sisteminde kural\u0131 g\u00f6rmeden silmek yerine \u00f6nce kaynak IP’yi, zinciri ve saya\u00e7lar\u0131 not edin. WAF, CDN veya hosting panelindeki g\u00fcvenlik katman\u0131 da ayn\u0131 \u015fekilde incelenmeli. Bir istemci IP’sinin ban listesinde olmas\u0131, taray\u0131c\u0131daki reset mesaj\u0131n\u0131 a\u00e7\u0131klayabilir.<\/p>\n
    4. Kaynak limitlerini ve kernel mesajlar\u0131n\u0131 inceleyin<\/h3>\n
    Web sunucusu dosya tan\u0131t\u0131c\u0131s\u0131, bellek veya ba\u011flant\u0131 kuyru\u011fu limitlerine dayanm\u0131\u015fsa hata d\u00fczensiz g\u00f6r\u00fcnebilir. A\u015fa\u011f\u0131daki komutlar tek ba\u015f\u0131na te\u015fhis koymaz; hangi y\u00f6ne bakaca\u011f\u0131n\u0131z\u0131 s\u00f6yler:<\/p>\n
    free -h\nuptime\nsudo dmesg -T | tail -n 80\nsudo ss -s<\/code><\/pre>\n
    dmesg<\/code> i\u00e7inde bellek yetersizli\u011fi, a\u011f s\u00fcr\u00fcc\u00fcs\u00fc veya ba\u011flant\u0131 tablosu ile ilgili kay\u0131tlar aranabilir. ss -s<\/code> ba\u011flant\u0131 durumlar\u0131n\u0131n \u00f6zetini verir.<\/p>\n
    Gece vardiyalar\u0131ndan birinde istemciler ba\u011flant\u0131 kopmas\u0131 bildiriyordu. \u0130lk bak\u0131\u015fta nginx’e odakland\u0131m, fakat ncdu<\/code> ile bakt\u0131\u011f\u0131mda \/var<\/code> b\u00f6l\u00fcm\u00fcn\u00fcn loglarla doldu\u011funu g\u00f6rd\u00fcm; uygulaman\u0131n logrotate ayar\u0131 unutulmu\u015ftu. Disk tamamen dolmadan log rotasyonunu d\u00fczelttim, ard\u0131ndan nginx logunda yeni ba\u011flant\u0131lar\u0131n normale d\u00f6nd\u00fc\u011f\u00fcn\u00fc do\u011frulad\u0131m. O olaydan beri disk kullan\u0131m\u0131n\u0131 CPU kadar erken kontrol ediyorum.<\/p>\n
    Taray\u0131c\u0131da ve bilgisayarda hangi ad\u0131mlar denenebilir?<\/h2>\n
    Sunucuda sorun g\u00f6r\u00fcnm\u00fcyorsa istemci taraf\u0131nda \u015fu s\u0131ray\u0131 izleyin:<\/p>\n
      \n
    1. Sayfay\u0131 gizli pencerede a\u00e7\u0131n ve uzant\u0131lar\u0131 ge\u00e7ici olarak devre d\u0131\u015f\u0131 b\u0131rak\u0131n.<\/li>\n
    2. VPN, kurumsal proxy ve antivir\u00fcs\u00fcn HTTPS tarama \u00f6zelli\u011fini ge\u00e7ici olarak kapat\u0131p tekrar deneyin.<\/li>\n
    3. Farkl\u0131 bir DNS \u00e7\u00f6z\u00fcmleyicisiyle kar\u015f\u0131la\u015ft\u0131rma yap\u0131n; \u00f6nce mevcut DNS yan\u0131t\u0131n\u0131 kaydedin.<\/li>\n
    4. Modem ve yerel a\u011f cihazlar\u0131n\u0131 yeniden ba\u015flatmadan \u00f6nce ba\u015fka bir a\u011fdan test edin.<\/li>\n
    5. \u0130\u015fletim sisteminin tarih-saat ayar\u0131n\u0131 ve sistem proxy ayar\u0131n\u0131 kontrol edin.<\/li>\n<\/ol>\n
      Taray\u0131c\u0131 \u00f6nbelle\u011fini temizlemek bazen i\u015fe yarar, fakat bu ad\u0131m a\u011f seviyesindeki reset’i onarmaz. Ayn\u0131 URL curl<\/code> ile de reset veriyorsa sorun b\u00fcy\u00fck ihtimalle yaln\u0131zca taray\u0131c\u0131 \u00f6nbelle\u011fi de\u011fildir.<\/p>\n
      Windows ve Linux DNS \u00f6nbelle\u011fi<\/h3>\n
      Windows’ta DNS \u00f6nbelle\u011fini temizlemek i\u00e7in:<\/p>\n
      ipconfig \/flushdns<\/code><\/pre>\n
      Linux’ta \u00f6nbellekleme servisine g\u00f6re komut de\u011fi\u015fir. systemd-resolved<\/code> kullan\u0131l\u0131yorsa:<\/p>\n
      sudo resolvectl flush-caches\nresolvectl statistics<\/code><\/pre>\n
      Bu komutlar yaln\u0131zca yerel DNS \u00f6nbelle\u011fini temizler. Alan ad\u0131n\u0131n yanl\u0131\u015f IP’ye i\u015faret eden kayd\u0131n\u0131 d\u00fczeltmez; kay\u0131t panelindeki A veya AAAA de\u011ferini ayr\u0131ca do\u011frulamak gerekir.<\/p>\n
      Bir IPv6 hatas\u0131n\u0131 nas\u0131l ay\u0131rt ederim?<\/h2>\n
      IPv6 taraf\u0131ndaki sorunlar, IPv4 ba\u011flant\u0131s\u0131 \u00e7al\u0131\u015fan bir sistemde kolayca g\u00f6zden ka\u00e7ar. Benzer durumda \u00f6nce iki protokol\u00fc ayr\u0131 ayr\u0131 test ederim; taray\u0131c\u0131n\u0131n hangi yolu se\u00e7ti\u011fini tahmin etmek yerine \u00e7\u0131kt\u0131ya bakmak daha h\u0131zl\u0131d\u0131r.<\/p>\n
      $ curl -4I https:\/\/ornek-site.test\nHTTP\/2 200\n\n$ curl -6I https:\/\/ornek-site.test\ncurl: (35) Recv failure: Connection reset by peer<\/code><\/pre>\n
      Bu \u00e7\u0131kt\u0131, HTTP ba\u015fl\u0131klar\u0131n\u0131n IPv4 yolundan geldi\u011fini ve IPv6 taraf\u0131nda TLS veya HTTP a\u015famas\u0131na ula\u015fmadan ba\u011flant\u0131n\u0131n kapand\u0131\u011f\u0131n\u0131 g\u00f6sterir. AAAA kayd\u0131 eski VPS’i g\u00f6steriyor olabilir; IPv6 firewall kural\u0131 eksik kalm\u0131\u015f veya web servisi yaln\u0131zca IPv4 adresinde dinliyor olabilir.<\/p>\n
      DNS yap\u0131land\u0131rmas\u0131n\u0131 de\u011fi\u015ftirirken A, AAAA, CDN origin adresi ve sunucunun ger\u00e7ek dinleme adresini birlikte kontrol edin. Alan ad\u0131 yap\u0131s\u0131 i\u00e7in Alt Alan Ad\u0131 (Subdomain) Nedir? Kullan\u0131m Rehberi<\/a><\/em> yaz\u0131s\u0131ndaki kay\u0131t mant\u0131\u011f\u0131 da yard\u0131mc\u0131 olabilir; kritik nokta, her alt alan ad\u0131n\u0131n do\u011fru IP ailesine gitmesidir.<\/p>\n
      Proxy, VPN ve MTU ba\u011flant\u0131y\u0131 neden s\u0131f\u0131rlayabilir?<\/h2>\n
      VPN veya kurumsal proxy, istemci ile web sunucusu aras\u0131na yeni bir a\u011f katman\u0131 ekler. T\u00fcnel i\u00e7indeki MTU de\u011feri do\u011fru ayarlanmad\u0131\u011f\u0131nda b\u00fcy\u00fck paketler par\u00e7alanabilir ya da sessizce d\u00fc\u015febilir. Baz\u0131 cihazlar ICMP mesajlar\u0131n\u0131 engelledi\u011fi i\u00e7in ba\u011flant\u0131, taray\u0131c\u0131 taraf\u0131nda genel bir reset hatas\u0131na d\u00f6n\u00fc\u015febilir.<\/p>\n
      Yol hakk\u0131nda fikir edinmek i\u00e7in:<\/p>\n
      mtr -rwzc 50 example.com<\/code><\/pre>\n
      Bu sat\u0131rdaki -r<\/code> rapor bi\u00e7imini, -w<\/code> geni\u015f \u00e7\u0131kt\u0131y\u0131, -c 50<\/code> ise g\u00f6nderilecek test say\u0131s\u0131n\u0131 belirler. MTR’deki tek bir ara d\u00fc\u011f\u00fcmde g\u00f6r\u00fclen kay\u0131p, sonraki d\u00fc\u011f\u00fcmlerde kay\u0131p yoksa ger\u00e7ek u\u00e7tan uca kay\u0131p olmayabilir; baz\u0131 y\u00f6nlendiriciler te\u015fhis paketlerine d\u00fc\u015f\u00fck \u00f6ncelik verir. Yaln\u0131zca tabloya bak\u0131p ISS’yi su\u00e7lamak yerine son hedefteki kayba odaklan\u0131n.<\/p>\n
      VPN kapal\u0131yken site a\u00e7\u0131l\u0131yor, VPN a\u00e7\u0131kken reset al\u0131yorsan\u0131z VPN sunucusunun \u00e7\u0131k\u0131\u015f IP’si engellenmi\u015f, t\u00fcnel MTU’su uyumsuz veya proxy TLS trafi\u011fini bozuyor olabilir. VPS taraf\u0131nda paket boyutlar\u0131yla oynarken \u00f6l\u00e7\u00fcm yapmadan kal\u0131c\u0131 sysctl ayar\u0131 eklemeyin. Bir ayar\u0131 kopyalay\u0131p her makineye uygulamak, a\u011f sorununu \u00e7\u00f6zmek yerine yeni bir tane \u00fcretebilir.<\/p>\n
      Hosting m\u00fc\u015fterileri i\u00e7in kontrol s\u0131ras\u0131<\/h2>\n
      Payla\u015f\u0131ml\u0131 hosting veya VPS kullan\u0131yorsan\u0131z her katmana eri\u015fiminiz olmayabilir. Destek talebine yaln\u0131zca “site a\u00e7\u0131lm\u0131yor” yazmak yerine a\u015fa\u011f\u0131daki bilgileri eklemek \u00e7\u00f6z\u00fcm\u00fc h\u0131zland\u0131r\u0131r:<\/p>\n