{"id":13548,"date":"2017-10-11T10:36:15","date_gmt":"2017-10-11T07:36:15","guid":{"rendered":"https:\/\/blog.natro.com\/?p=13548"},"modified":"2023-02-22T18:28:18","modified_gmt":"2023-02-22T15:28:18","slug":"500-internal-server-hatasi-nedir","status":"publish","type":"post","link":"https:\/\/www.natro.com\/blog\/500-internal-server-hatasi-nedir\/","title":{"rendered":"500 Internal Server Hatas\u0131 Nedir?"},"content":{"rendered":"

\u201c500 Internal Server Hatas\u0131\u201d veya<\/strong> \u201chttp 500 hatas\u0131\u201d<\/strong> web sitenizin sunucusunda bir \u015feylerin yanl\u0131\u015f gitti\u011finin g\u00f6stergesidir. Bu yanl\u0131\u015fl\u0131k, genelde .htaccess<\/strong> dosyas\u0131n\u0131n yanl\u0131\u015f yap\u0131land\u0131r\u0131lmas\u0131ndan kaynaklanmaktad\u0131r. Bu durum, hatal\u0131 bir sayfan\u0131n veya sitenin programlanmas\u0131yla ilgilidir. Bunun d\u0131\u015f\u0131nda, di\u011fer nedenler uyumsuz PHP s\u00fcr\u00fcm\u00fc veya WordPress g\u00fcncellemeleri olabilir. Bir web sayfas\u0131n\u0131 a\u00e7maya \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131zda, web taray\u0131c\u0131n\u0131zda bu hatayla kar\u015f\u0131la\u015f\u0131rs\u0131n\u0131z.<\/p>\n

Bu hatan\u0131n detay\u0131n\u0131 dilerseniz, sunucu \u00fczerinden kontrol edebilirsiniz. Linux ve Windows i\u015fletim sistemine g\u00f6re de\u011fi\u015fkenlik g\u00f6steren 500 Internal Server hatas\u0131n\u0131n a\u00e7\u0131lma d\u00fczeni ise; a\u015fa\u011f\u0131daki gibidir:<\/p>\n

Linux Tabanl\u0131 Paneller:\u00a0<\/strong><\/h4>\n
\"http
http 500 hatas\u0131<\/figcaption><\/figure>\n

Linux i\u015fletim sisteminde, \u201c500 Internal Server\u201d<\/strong> veya \u201chttp 500 hatas\u0131\u201d<\/strong>\u00a0hatas\u0131 al\u0131yorsan\u0131z, sitenin ana dizininde olu\u015facak olan \u201cerror_log\u201d<\/strong> dosyas\u0131n\u0131n son sat\u0131r\u0131n\u0131 kontrol edebilirsiniz.<\/p>\n

Hata sat\u0131r\u0131n\u0131 a\u00e7mak i\u00e7in ise; a\u015fa\u011f\u0131daki ad\u0131mlar\u0131 takip edebilirsiniz:<\/p>\n

\u201ccPanel ana ekran > select php versiyon > php 5,X s\u00fcr\u00fcm\u00fc > set as current > PHP S\u00fcr\u00fcm\u00fc > Switch To PHP Options<\/em> > display_errors > ON\u00a0 > Kaydet\u201d<\/em><\/strong><\/p>\n

Windows Tabanl\u0131 Paneller:\u00a0<\/strong><\/h4>\n

\"\"<\/p>\n

Bu panellerde ise; \u00a0\u201c500 Internal Server Error\u201d hatas\u0131 sunucu \u00fczerinde a\u00e7\u0131lan bir taray\u0131c\u0131 \u00fczerinde lokal bazl\u0131 g\u00f6r\u00fclmektedir.<\/p>\n

Hata sat\u0131r\u0131n\u0131 a\u00e7mak i\u00e7in a\u015fa\u011f\u0131daki ad\u0131mlar\u0131 takip edebilirsiniz.<\/p>\n

Start\u00a0 > Run > inetmgr > site > error pages > 500 \u2018\u00fc se\u00e7ip > Edit Feature settings > detailed error > OK\u00a0<\/em><\/strong><\/p>\n

Bu ad\u0131mlardan sonra son kullan\u0131c\u0131 ekran\u0131 \u00fczerinde art\u0131k hatan\u0131n detay\u0131na eri\u015febileceksiniz.<\/p>\n

Hatan\u0131n D\u00fczeltilmesi \u0130\u00e7in \u0130zleyebilece\u011finiz Di\u011fer Yollar: <\/strong><\/h4>\n

Sitenizi yedekleyin<\/strong>. <\/strong><\/p>\n

Site yedekleme i\u015flemini, sadece bu hatayla kar\u015f\u0131la\u015ft\u0131\u011f\u0131n\u0131z i\u00e7in de\u011fil, genel olarak g\u00fcvenli\u011finizi sa\u011flamak i\u00e7in d\u00fczenli olarak ger\u00e7ekle\u015ftirmeniz, sizin yarar\u0131n\u0131za olacakt\u0131r. Kar\u015f\u0131la\u015fabilece\u011finiz olas\u0131 durumlarda, sitenizin yede\u011fi, hayat kurtarabilir. Yedekleme i\u015flemini dilerseniz FTP <\/strong>kullanarak, dilerseniz de WordPress\u2019in eklentilerinden yard\u0131m alarak ger\u00e7ekle\u015ftirebilirsiniz.<\/p>\n

\u201cWordPress\u201dinizde sorun yaratan eklentiyi bulun. <\/strong><\/p>\n

Kimi zaman bu hata, bir eklentinin y\u00fcklenmesinden veya g\u00fcncellenmesinden kaynakl\u0131 olu\u015fabilir. E\u011fer yukar\u0131daki ad\u0131mlar sorunu \u00e7\u00f6zmenizde yard\u0131mc\u0131 olmazsa, t\u00fcm eklentilerinizi devre d\u0131\u015f\u0131 b\u0131rakarak, size problem yaratan eklentiyi bulmaya \u00e7al\u0131\u015fmal\u0131s\u0131n\u0131z.<\/p>\n

PHP bellek limitinizi artt\u0131r\u0131n.\u00a0<\/strong><\/p>\n

PHP bellek limitlerinizi belirleyen etmenler hosting firman\u0131z ve WordPress\u2019tir. Siz limiti a\u015fmaya ba\u015flad\u0131\u011f\u0131n\u0131zda WordPress otomatik olarak limiti artt\u0131rmaya \u00e7al\u0131\u015f\u0131r ancak; hosting firman\u0131z limiti ka\u00e7 olarak belirlediyse, WordPress ancak o s\u0131n\u0131ra kadar y\u00fckseltilebilir. Bu nedenle limitinizi biraz y\u00fckseltip sitenizi test edebilirsiniz. E\u011fer sorun devam ediyorsa, hosting firman\u0131zla g\u00f6r\u00fc\u015fmenizi tavsiye ederiz.<\/p>\n

Yeni bir .htaccess veya web.config dosyas\u0131 olu\u015fturun<\/strong>. <\/strong><\/p>\n

WordPress k\u00f6k dosyan\u0131z\u0131 a\u00e7t\u0131\u011f\u0131n\u0131zda, kar\u015f\u0131n\u0131za \u201cwp-admin\u201d ve \u201cwp-content\u201d klas\u00f6rleri \u00e7\u0131kacakt\u0131r. Burada bulunan \u201c.htaccess\u201d dosyas\u0131n\u0131n ad\u0131n\u0131 \u201c.htaccess.bak\u201d olarak de\u011fi\u015ftirip, ard\u0131ndan silebilirsiniz. Bu i\u015flemden sonra, art\u0131k yeni bir \u201c.htaccess\u201d dosyas\u0131 olu\u015fturman\u0131z gerekecektir. En son ad\u0131m olarak, WordPress ayarlar b\u00f6l\u00fcm\u00fcnde bulunan \u201cpermalinks\u201d k\u0131sm\u0131na giderek de\u011fi\u015fiklikleri kaydedebilirsiniz.<\/p>\n\n\n

\"\"<\/a><\/figure>\n","protected":false},"excerpt":{"rendered":"\u201c500 Internal Server Hatas\u0131\u201d veya \u201chttp 500 hatas\u0131\u201d web sitenizin sunucusunda bir \u015feylerin yanl\u0131\u015f gitti\u011finin g\u00f6stergesidir. Bu yanl\u0131\u015fl\u0131k,…\n","protected":false},"author":7,"featured_media":13554,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":{"0":"post-13548","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-genel"},"_links":{"self":[{"href":"https:\/\/www.natro.com\/blog\/wp-json\/wp\/v2\/posts\/13548","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.natro.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.natro.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.natro.com\/blog\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.natro.com\/blog\/wp-json\/wp\/v2\/comments?post=13548"}],"version-history":[{"count":2,"href":"https:\/\/www.natro.com\/blog\/wp-json\/wp\/v2\/posts\/13548\/revisions"}],"predecessor-version":[{"id":34448,"href":"https:\/\/www.natro.com\/blog\/wp-json\/wp\/v2\/posts\/13548\/revisions\/34448"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.natro.com\/blog\/wp-json\/wp\/v2\/media\/13554"}],"wp:attachment":[{"href":"https:\/\/www.natro.com\/blog\/wp-json\/wp\/v2\/media?parent=13548"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.natro.com\/blog\/wp-json\/wp\/v2\/categories?post=13548"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.natro.com\/blog\/wp-json\/wp\/v2\/tags?post=13548"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}