{"id":1975,"date":"2026-08-19T13:30:56","date_gmt":"2026-08-19T10:30:56","guid":{"rendered":"https:\/\/allinonewpsettings.com\/blog\/?p=1975"},"modified":"2026-08-04T11:29:00","modified_gmt":"2026-08-04T11:29:00","slug":"wordpress-yonetim-ve-giris-sayfasinda-ssl-nasil-zorlanir","status":"publish","type":"post","link":"https:\/\/allinonewpsettings.com\/blog\/tr\/wordpress-yonetim-ve-giris-sayfasinda-ssl-nasil-zorlanir\/","title":{"rendered":"WordPress Giri\u015f ve Y\u00f6netim Sayfalar\u0131nda SSL Nas\u0131l Zorlan\u0131r?"},"content":{"rendered":"

WordPress giri\u015f sayfas\u0131 HTTP’ye d\u00f6n\u00fcyor veya proxy arkas\u0131nda y\u00f6nlendirme d\u00f6ng\u00fcs\u00fcne giriyorsa yaln\u0131zca FORCE_SSL_ADMIN<\/code> eklemek yeterli olmayabilir. WordPress’in iste\u011fi ger\u00e7ekten HTTPS olarak alg\u0131lamas\u0131 ve kullan\u0131lan hostta ge\u00e7erli sertifika bulunmas\u0131 gerekir.<\/p>\n

Ayar\u0131 a\u00e7madan \u00f6nce \u00e7al\u0131\u015fan bir HTTPS y\u00f6netim yolu ve dosya d\u00fczeyinde geri d\u00f6n\u00fc\u015f eri\u015fimi haz\u0131rlay\u0131n. B\u00f6ylece yanl\u0131\u015f proxy ya da URL yap\u0131land\u0131rmas\u0131 y\u00f6netici hesab\u0131n\u0131 kilitlemez.<\/p>\n

\u0130\u00e7indekiler<\/strong><\/p>\n
    \n
  1. FORCE_SSL_ADMIN ne yapar?<\/a><\/li>\n
  2. Ger\u00e7ek\u00e7i bir WordPress \u00f6rne\u011fi<\/a><\/li>\n
  3. Neden \u00f6nemlidir?<\/a><\/li>\n
  4. G\u00fcvenli uygulama ad\u0131mlar\u0131<\/a><\/li>\n
  5. \u0130leri teknik kontroller<\/a><\/li>\n
  6. Riskler ve geri alma<\/a><\/li>\n
  7. AIOWS nas\u0131l yard\u0131mc\u0131 olur?<\/a><\/li>\n
  8. \u0130lgili AIOWS yaz\u0131lar\u0131<\/a><\/li>\n
  9. Sonu\u00e7 ve \u00f6nerilen yol<\/a><\/li>\n
  10. Resm\u00ee kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n

    FORCE_SSL_ADMIN ne yapar?<\/h2>\n

    FORCE_SSL_ADMIN<\/code>, WordPress’in giri\u015f ve y\u00f6netim alanlar\u0131nda HTTPS kullanmas\u0131n\u0131 sa\u011flar. Sertifika kurmaz, WordPress adreslerini otomatik d\u00fczeltmez ve reverse proxy’nin istemcinin kulland\u0131\u011f\u0131 protokol\u00fc yanl\u0131\u015f iletmesini gidermez.<\/p>\n

    Ger\u00e7ek\u00e7i bir WordPress \u00f6rne\u011fi<\/h2>\n

    Ziyaret\u00e7i CDN \u00fczerinden HTTPS kullan\u0131r, fakat CDN origin’e HTTP ile ba\u011flan\u0131r. WordPress g\u00fcvenilir proxy ba\u015fl\u0131\u011f\u0131n\u0131 do\u011fru yorumlamad\u0131\u011f\u0131 i\u00e7in iste\u011fi HTTP san\u0131r ve giri\u015f sayfas\u0131n\u0131 tekrar HTTPS’ye y\u00f6nlendirir. Taray\u0131c\u0131 d\u00f6ng\u00fcye girer; Secure \u00e7erez de beklenen \u015fekilde olu\u015fmaz.<\/p>\n

    \u00c7\u00f6z\u00fcm, her X-Forwarded-Proto<\/code> ba\u015fl\u0131\u011f\u0131na g\u00fcvenmek de\u011fildir. WordPress, d\u0131\u015f iste\u011fin HTTPS kulland\u0131\u011f\u0131n\u0131 yaln\u0131zca g\u00fcvenilir proxy bu bilgiyi do\u011fru bi\u00e7imde iletti\u011finde kabul etmelidir.<\/p>\n

    Neden \u00f6nemlidir?<\/h2>\n

    Giri\u015f bilgileri ve y\u00f6netici oturumlar\u0131 HTTPS \u00fczerinden ta\u015f\u0131nmal\u0131d\u0131r. Yanl\u0131\u015f uygulama ise giri\u015f d\u00f6ng\u00fcs\u00fc, s\u00fcrekli oturum kayb\u0131, hatal\u0131 parola s\u0131f\u0131rlama ba\u011flant\u0131s\u0131 veya wp-admin<\/code> eri\u015fiminin tamamen kesilmesine yol a\u00e7abilir.<\/p>\n

    G\u00fcvenli uygulama ad\u0131mlar\u0131<\/h2>\n
      \n
    1. https:\/\/alanadi\/wp-login.php<\/code> ve \/wp-admin\/<\/code> yollar\u0131n\u0131 elle do\u011frulay\u0131n.<\/li>\n
    2. WordPress home<\/code> ve siteurl<\/code> de\u011ferlerinin do\u011fru hostu kulland\u0131\u011f\u0131n\u0131 kontrol edin.<\/li>\n
    3. Proxy varsa HTTPS bilgisinin yaln\u0131z g\u00fcvenilir kaynaktan geldi\u011fini do\u011frulay\u0131n.<\/li>\n
    4. wp-config.php<\/code> yede\u011fini al\u0131p FORCE_SSL_ADMIN<\/code> ayar\u0131n\u0131 bir kez ekleyin.<\/li>\n
    5. Giri\u015f, \u00e7\u0131k\u0131\u015f, parola s\u0131f\u0131rlama ve ikinci y\u00f6netici oturumunu s\u0131nay\u0131n.<\/li>\n
    6. Secure \u00e7erezleri ve HTTP iste\u011finin tek y\u00f6nlendirmeyle HTTPS’ye ula\u015ft\u0131\u011f\u0131n\u0131 kontrol edin.<\/li>\n<\/ol>\n

      \u0130leri teknik kontroller<\/h2>\n

      Load balancer ba\u011fl\u0131l\u0131\u011f\u0131, \u00e7erez domaini, multisite host e\u015fle\u015fmesi, REST nonce istekleri ve y\u00f6netim i\u00e7indeki medya\/eklenti sayfalar\u0131n\u0131 inceleyin. Do\u011frudan istemci taraf\u0131ndan eklenebilen forwarded ba\u015fl\u0131klara g\u00fcvenilmedi\u011fini s\u0131nay\u0131n.<\/p>\n

      CDN, web sunucusu ve WordPress y\u00f6nlendirmelerini tek zincirde \u00e7\u0131kar\u0131n. Y\u00f6netim yolunun HTTPS oldu\u011funu WordPress’e do\u011fru bildirmek ile genel HTTP\u2192HTTPS y\u00f6nlendirmesini y\u00f6netmek ayr\u0131 sorumluluklard\u0131r.<\/p>\n

      Riskler ve geri alma<\/h2>\n

      HTTPS \u00e7al\u0131\u015fmadan sabiti a\u00e7mak veya URL, proxy ve y\u00f6nlendirme ayarlar\u0131n\u0131 ayn\u0131 anda de\u011fi\u015ftirmek geri d\u00f6n\u00fc\u015f\u00fc zorla\u015ft\u0131r\u0131r. A\u00e7\u0131k bir y\u00f6netici oturumu ve sunucu eri\u015fimi tutun. Giri\u015f d\u00f6ng\u00fcs\u00fc ya da Secure \u00e7erez sorunu olu\u015fursa son de\u011fi\u015fikli\u011fi geri al\u0131n ve \u00f6nce WordPress’in iste\u011fi HTTP veya HTTPS olarak alg\u0131lama bi\u00e7imini d\u00fczeltin.<\/p>\n

      \n

      AIOWS nas\u0131l yard\u0131mc\u0131 olur?<\/p>\n

      AIOWS SSL Y\u00f6neticisi<\/h2>\n

      Y\u00f6netim alan\u0131nda SSL zorlamadan \u00f6nce AIOWS SSL Y\u00f6neticisi, WordPress adreslerinin ve uygulaman\u0131n HTTPS davran\u0131\u015f\u0131n\u0131n tutarl\u0131 oldu\u011funu denetlemeye yard\u0131mc\u0131 olur.<\/p>\n

      Mod\u00fcl, reverse proxy’nin g\u00fcven ili\u015fkisini veya web sunucusundaki sertifikay\u0131 kendi ba\u015f\u0131na d\u00fczeltemez. Proxy, d\u0131\u015f iste\u011fin HTTPS bilgisini yanl\u0131\u015f iletiyorsa \u00f6nce altyap\u0131 katman\u0131n\u0131 g\u00fcvenli bi\u00e7imde yap\u0131land\u0131r\u0131n. Sonras\u0131nda giri\u015f, parola s\u0131f\u0131rlama, REST ve y\u00f6netim i\u00e7i sayfalar ger\u00e7ek oturumlarla s\u0131nanmal\u0131d\u0131r.<\/p>\n

      Y\u00f6nlendirme d\u00f6ng\u00fcs\u00fc veya oturum kayb\u0131 s\u00fcr\u00fcyorsa ek SSL kurallar\u0131 a\u00e7may\u0131n. Son \u00e7al\u0131\u015fan yap\u0131land\u0131rmaya d\u00f6n\u00fcn ve sorunun URL, proxy alg\u0131s\u0131 ya da \u00e7erez katman\u0131nda oldu\u011funu ayr\u0131 ayr\u0131 kan\u0131tlay\u0131n.<\/p>\n

      AIOWS SSL Y\u00f6neticisi’ni inceleyin<\/a>AIOWS planlar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n<\/a><\/p>\n<\/section>\n

      \u0130lgili AIOWS yaz\u0131lar\u0131<\/h2>\n