{"id":8992,"date":"2026-08-04T11:18:26","date_gmt":"2026-08-04T08:18:26","guid":{"rendered":"https:\/\/www.turkticaret.net\/blog\/?p=8992"},"modified":"2026-09-09T17:12:12","modified_gmt":"2026-09-09T14:12:12","slug":"err-bad-ssl-client-auth-cert-hatasi","status":"publish","type":"post","link":"https:\/\/www.turkticaret.net\/blog\/err-bad-ssl-client-auth-cert-hatasi\/","title":{"rendered":"ERR_BAD_SSL_CLIENT_AUTH_CERT Hatas\u0131 ve \u00c7\u00f6z\u00fcm\u00fc"},"content":{"rendered":"

Sertifika kaynakl\u0131 taray\u0131c\u0131 hatalar\u0131n\u0131n \u00e7o\u011fu ziyaret edilen sitenin sertifikas\u0131yla ilgilidir. ERR_BAD_SSL_CLIENT_AUTH_CERT hatas\u0131 ise ters y\u00f6nde \u00e7al\u0131\u015f\u0131r: sorun genellikle sunucunun de\u011fil, sizin bilgisayar\u0131n\u0131z\u0131n sundu\u011fu sertifikadad\u0131r. A\u015fa\u011f\u0131da hatan\u0131n nedenlerini, taray\u0131c\u0131lara g\u00f6re nas\u0131l g\u00f6r\u00fcnd\u00fc\u011f\u00fcn\u00fc ve hem kullan\u0131c\u0131 hem sistem y\u00f6neticisi taraf\u0131nda uygulanabilecek ad\u0131mlar\u0131 bulacaks\u0131n\u0131z.<\/span><\/p>\n

\"ERR_BAD_SSL_CLIENT_AUTH_CERT<\/p>\n

ERR_BAD_SSL_CLIENT_AUTH_CERT Hatas\u0131 Nedir?<\/b><\/h2>\n

ERR_BAD_SSL_CLIENT_AUTH_CERT, TLS el s\u0131k\u0131\u015fmas\u0131n\u0131n istemci sertifikas\u0131n\u0131n hatal\u0131 olmas\u0131 ya da hi\u00e7 sunulmamas\u0131 nedeniyle tamamlanamad\u0131\u011f\u0131n\u0131 bildiren Chromium hata kodudur. Sunucu ba\u011flant\u0131 i\u00e7in sizden bir kimlik sertifikas\u0131 ister, taray\u0131c\u0131 bunu sunamad\u0131\u011f\u0131nda veya sundu\u011fu sertifika kabul edilmedi\u011finde ba\u011flant\u0131 kesilir. Chrome bu durumda sayfay\u0131 y\u00fcklemeden a\u015fa\u011f\u0131daki ekran\u0131 g\u00f6sterir:<\/span><\/p>\n

This site can’t provide a secure connection<\/span><\/p>\n

alanadi.com didn’t accept your login certificate, or one may not have been provided.<\/span><\/p>\n

Try contacting the system admin.<\/span><\/p>\n

ERR_BAD_SSL_CLIENT_AUTH_CERT<\/span><\/p>\n

Normal HTTPS ba\u011flant\u0131lar\u0131nda yaln\u0131zca sunucu, kurulu olan <\/span>SSL sertifikas\u0131<\/span><\/a> ile kimli\u011fini kan\u0131tlar; ziyaret\u00e7inin sertifika sunmas\u0131 gerekmez. Ancak baz\u0131 sunucular kar\u015f\u0131l\u0131kl\u0131 kimlik do\u011frulama (mutual TLS) kullanacak \u015fekilde yap\u0131land\u0131r\u0131l\u0131r. Bu senaryoda sunucu, el s\u0131k\u0131\u015fma s\u0131ras\u0131nda taray\u0131c\u0131dan ge\u00e7erli bir istemci sertifikas\u0131 talep eder. Kurumsal portallar, kamu uygulamalar\u0131 ve bankac\u0131l\u0131k sistemleri bu yap\u0131y\u0131 s\u0131k kullan\u0131r.<\/span><\/p>\n

Sunucu istemci sertifikas\u0131 istedi\u011finde taray\u0131c\u0131, sistemde bulunan uygun sertifikalar\u0131 listeleyen bir se\u00e7im penceresi a\u00e7ar. Listede e\u015fle\u015fen sertifika yoksa pencere bo\u015f gelir; pencereyi kapatman\u0131z veya iptal etmeniz durumunda ise taray\u0131c\u0131 sunucuya bo\u015f bir sertifika yan\u0131t\u0131 g\u00f6nderir. \u00d6zel kaynaklar\u0131 koruyan sunucular bu yan\u0131tta el s\u0131k\u0131\u015fmay\u0131 sonland\u0131r\u0131r ve hata ekran\u0131 ortaya \u00e7\u0131kar. Yani mesaj sunucuya ula\u015f\u0131lamad\u0131\u011f\u0131 anlam\u0131na gelmez; sunucuya ula\u015f\u0131lm\u0131\u015f, ileti\u015fim ba\u015flam\u0131\u015f, ancak kimlik do\u011frulama a\u015famas\u0131nda kar\u015f\u0131l\u0131kl\u0131 g\u00fcven kurulamam\u0131\u015ft\u0131r.<\/span><\/p>\n

Chromium bu hatay\u0131 a\u011f hata listesinde -117 numaras\u0131yla tan\u0131mlar. Bu nedenle baz\u0131 eski s\u00fcr\u00fcmlerde ve sistem kay\u0131tlar\u0131nda ayn\u0131 sorun Error 117 bi\u00e7iminde de g\u00f6r\u00fcnebilir.<\/span><\/p>\n

ERR_BAD_SSL_CLIENT_AUTH_CERT Hatas\u0131 Neden Olu\u015fur?<\/b><\/h2>\n

Hatan\u0131n kayna\u011f\u0131 kullan\u0131c\u0131 taraf\u0131ndaki sertifika deposunda, taray\u0131c\u0131 yap\u0131land\u0131rmas\u0131nda, a\u011f \u00fczerindeki bir g\u00fcvenlik cihaz\u0131nda veya do\u011frudan sunucu ayarlar\u0131nda olabilir. En s\u0131k kar\u015f\u0131la\u015f\u0131lan nedenler \u015funlard\u0131r:<\/span><\/p>\n

    \n
  • Bilgisayarda kurulu istemci sertifikas\u0131n\u0131n s\u00fcresinin dolmas\u0131 veya iptal listesine girmesi<\/span><\/li>\n
  • Sertifika se\u00e7im penceresinin bo\u015f gelmesi ya da pencerenin iptal edilmesi<\/span><\/li>\n
  • Sertifikan\u0131n \u00f6zel anahtar\u0131n\u0131n bozulmas\u0131, silinmesi veya ak\u0131ll\u0131 kart ile token ba\u011flant\u0131s\u0131n\u0131n kesilmesi<\/span><\/li>\n
  • Sunucunun kabul etti\u011fi otorite d\u0131\u015f\u0131nda bir CA taraf\u0131ndan imzalanm\u0131\u015f sertifika sunulmas\u0131<\/span><\/li>\n
  • Sistemde birden fazla sertifika bulunmas\u0131 ve yanl\u0131\u015f olan\u0131n se\u00e7ilmesi<\/span><\/li>\n
  • G\u00fcvenlik duvar\u0131, antivir\u00fcs veya proxy \u00e7\u00f6z\u00fcmlerinin el s\u0131k\u0131\u015fmaya m\u00fcdahale etmesi<\/span><\/li>\n
  • Sistem saat ve tarih ayar\u0131n\u0131n hatal\u0131 olmas\u0131 nedeniyle sertifikan\u0131n ge\u00e7ersiz g\u00f6r\u00fcnmesi<\/span><\/li>\n
  • Sunucu taraf\u0131nda istemci do\u011frulamas\u0131n\u0131n hatal\u0131 yap\u0131land\u0131r\u0131lmas\u0131 veya g\u00fcvenilen CA zincirinin eksik tan\u0131mlanmas\u0131<\/span><\/li>\n<\/ul>\n

    S\u00fcresi dolmu\u015f bir sertifika depoda durmaya ve se\u00e7im penceresinde g\u00f6r\u00fcnmeye devam etti\u011fi i\u00e7in yerelde her \u015fey yolunda g\u00f6r\u00fcnebilir; bu nedenle sertifikan\u0131n ge\u00e7erlilik tarihini ayr\u0131ca kontrol etmek gerekir. Bu nedenlerin bir k\u0131sm\u0131 yaln\u0131zca tek kullan\u0131c\u0131y\u0131, bir k\u0131sm\u0131 t\u00fcm ziyaret\u00e7ileri etkiler. Ayn\u0131 siteye ba\u015fka bir cihazdan veya a\u011fdan ba\u011flanmay\u0131 denemek, sorunun yerel mi yoksa sunucu kaynakl\u0131 m\u0131 oldu\u011funu anlaman\u0131n en h\u0131zl\u0131 yoludur.<\/span><\/p>\n

    Hatan\u0131n Taray\u0131c\u0131lara G\u00f6re G\u00f6r\u00fcn\u00fcm\u00fc<\/b><\/h2>\n

    Hata kodu Chromium altyap\u0131s\u0131na \u00f6zg\u00fcd\u00fcr. Chrome, Edge, Brave ve Opera ayn\u0131 tan\u0131m\u0131 payla\u015ft\u0131\u011f\u0131 i\u00e7in kod bu taray\u0131c\u0131larda birebir ayn\u0131 \u015fekilde g\u00f6r\u00fcn\u00fcr; Firefox ise farkl\u0131 bir sertifika uyar\u0131s\u0131 g\u00f6sterir.<\/span><\/p>\n\n\n\n\n\n\n
    Taray\u0131c\u0131<\/b><\/td>\nTipik g\u00f6r\u00fcn\u00fcm<\/b><\/td>\nSertifika y\u00f6netimi<\/b><\/td>\n<\/tr>\n
    Google Chrome<\/span><\/td>\nBa\u011flant\u0131 kesilir, hata kodu do\u011frudan sayfada g\u00f6r\u00fcn\u00fcr<\/span><\/td>\nWindows’ta sistem sertifika deposu<\/span><\/td>\n<\/tr>\n
    Microsoft Edge<\/span><\/td>\nAyn\u0131 kod g\u00f6r\u00fcn\u00fcr, kurumsal politikalar ek k\u0131s\u0131t getirebilir<\/span><\/td>\nWindows’ta sistem sertifika deposu<\/span><\/td>\n<\/tr>\n
    Mozilla Firefox<\/span><\/td>\nBu kod yerine farkl\u0131 bir sertifika uyar\u0131s\u0131 g\u00f6sterir<\/span><\/td>\nKendi ba\u011f\u0131ms\u0131z sertifika deposu<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Bu farkl\u0131l\u0131k pratik bir te\u015fhis imk\u00e2n\u0131 sunar. Hata Edge taray\u0131c\u0131da da g\u00f6r\u00fcl\u00fcyorsa, iki taray\u0131c\u0131 ayn\u0131 sistem deposunu kulland\u0131\u011f\u0131 i\u00e7in sorunun i\u015fletim sistemi seviyesinde oldu\u011fu d\u00fc\u015f\u00fcn\u00fclebilir. Firefox’ta sorun ya\u015fanm\u0131yorsa, kendi deposunu kulland\u0131\u011f\u0131 i\u00e7in sistem taraf\u0131ndaki sertifikan\u0131n hatal\u0131 oldu\u011fu ihtimali g\u00fc\u00e7lenir.<\/span><\/p>\n

    ERR_BAD_SSL_CLIENT_AUTH_CERT Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr?<\/b><\/h2>\n

    Sorunun b\u00fcy\u00fck k\u0131sm\u0131 teknik bilgi gerektirmeyen kontrollerle \u00e7\u00f6z\u00fclebilir. A\u015fa\u011f\u0131daki ad\u0131mlar\u0131 s\u0131rayla uygulamak hem gereksiz sistem de\u011fi\u015fikliklerini \u00f6nler hem de kayna\u011f\u0131 daralt\u0131r.<\/span><\/p>\n

      \n
    1. Bilgisayar\u0131n\u0131z\u0131n tarih, saat ve saat dilimi ayarlar\u0131n\u0131n do\u011fru oldu\u011funu kontrol edin; hatal\u0131 saat, ge\u00e7erli sertifikalar\u0131n bile s\u00fcresi dolmu\u015f g\u00f6r\u00fcnmesine yol a\u00e7abilir.<\/span><\/li>\n
    2. Taray\u0131c\u0131y\u0131 tamamen kapat\u0131p yeniden a\u00e7\u0131n; b\u00f6ylece \u00f6nbelle\u011fe al\u0131nm\u0131\u015f TLS oturumlar\u0131 temizlenir ve el s\u0131k\u0131\u015fma yeniden kurulur.<\/span><\/li>\n
    3. Ge\u00e7mi\u015f temizleme b\u00f6l\u00fcm\u00fcnden \u00e7erezleri ve \u00f6nbelle\u011fi silin, m\u00fcmk\u00fcnse SSL durumunu da s\u0131f\u0131rlay\u0131n.<\/span><\/li>\n
    4. Gizli pencerede ayn\u0131 adresi a\u00e7\u0131n. Sorun burada g\u00f6r\u00fclm\u00fcyorsa eklentileri tek tek devre d\u0131\u015f\u0131 b\u0131rakarak test edin.<\/span><\/li>\n
    5. Sertifika se\u00e7im penceresi a\u00e7\u0131l\u0131yorsa do\u011fru sertifikay\u0131 se\u00e7ti\u011finizden ve pencereyi kapatmad\u0131\u011f\u0131n\u0131zdan emin olun.<\/span><\/li>\n
    6. Ayn\u0131 adrese farkl\u0131 bir cihazdan ve farkl\u0131 bir a\u011fdan ba\u011flanmay\u0131 deneyin; b\u00f6ylece sorunun cihaza m\u0131 a\u011fa m\u0131 ait oldu\u011fu netle\u015fir.<\/span><\/li>\n
    7. Antivir\u00fcs veya g\u00fcvenlik yaz\u0131l\u0131m\u0131n\u0131z\u0131n HTTPS tarama \u00f6zelli\u011fini ge\u00e7ici olarak kapat\u0131p tekrar deneyin, test sonras\u0131 mutlaka geri a\u00e7\u0131n.<\/span><\/li>\n
    8. VPN veya proxy kullan\u0131yorsan\u0131z ba\u011flant\u0131y\u0131 kesip do\u011frudan eri\u015fim deneyin.<\/span><\/li>\n<\/ol>\n

      Bu ad\u0131mlar sonu\u00e7 vermiyorsa sorun b\u00fcy\u00fck olas\u0131l\u0131kla sistem sertifika deposundaki bir istemci sertifikas\u0131yla ilgilidir. E-imza, banka, kamu portal\u0131 veya kurumsal uygulama eri\u015fimlerinde sertifika ilgili kurumdan temin edildi\u011fi i\u00e7in yenileme s\u00fcrecinin de o kurum \u00fczerinden y\u00fcr\u00fct\u00fclmesi gerekir.<\/span><\/p>\n

      Windows \u00dczerinde \u0130stemci Sertifikas\u0131 Kontrol\u00fc<\/b><\/h2>\n

      Chrome ve Edge, Windows \u00fczerinde istemci sertifikalar\u0131n\u0131 i\u015fletim sisteminin sertifika deposundan okur. Bu nedenle hata \u00e7o\u011fu zaman depodaki hatal\u0131, s\u00fcresi ge\u00e7mi\u015f ya da \u00f6zel anahtar\u0131 bulunmayan bir kay\u0131ttan kaynaklan\u0131r. macOS’ta Anahtar Zinciri, Linux’ta ise taray\u0131c\u0131n\u0131n kendi sertifika veritaban\u0131 kullan\u0131l\u0131r; a\u015fa\u011f\u0131daki ad\u0131mlar Windows i\u00e7indir.<\/span><\/p>\n

      Sertifikalar\u0131 g\u00f6r\u00fcnt\u00fclemek i\u00e7in \u00c7al\u0131\u015ft\u0131r penceresine <\/span>certmgr.msc<\/span> yazarak kullan\u0131c\u0131 sertifika y\u00f6neticisini a\u00e7abilirsiniz. Ki\u015fisel klas\u00f6r\u00fc alt\u0131ndaki Sertifikalar b\u00f6l\u00fcm\u00fcnde, taray\u0131c\u0131n\u0131n sunucuya sunabilece\u011fi istemci sertifikalar\u0131 listelenir. Her sertifikaya \u00e7ift t\u0131klayarak ge\u00e7erlilik tarihini, kimin taraf\u0131ndan verildi\u011fini ve \u00f6zel anahtar\u0131n mevcut olup olmad\u0131\u011f\u0131n\u0131 g\u00f6rebilirsiniz. \u00d6zel anahtar\u0131n bulunmad\u0131\u011f\u0131 bir sertifika kimlik do\u011frulama i\u00e7in kullan\u0131lamaz.<\/span><\/p>\n

      S\u00fcresi dolmu\u015f veya art\u0131k kullan\u0131lmayan sertifikalar\u0131 depodan kald\u0131rmak, taray\u0131c\u0131n\u0131n yanl\u0131\u015f sertifikay\u0131 sunmas\u0131n\u0131 engeller. Silme i\u015fleminden \u00f6nce sertifikan\u0131n hangi hizmet i\u00e7in kullan\u0131ld\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n; e-imza ya da kurumsal eri\u015fim sertifikalar\u0131n\u0131n yanl\u0131\u015fl\u0131kla silinmesi ba\u015fka hizmetlere eri\u015fimi de engelleyebilir. Ak\u0131ll\u0131 kart veya USB token kullan\u0131yorsan\u0131z s\u00fcr\u00fcc\u00fclerin g\u00fcncel oldu\u011fundan ve cihaz\u0131n sistem taraf\u0131ndan tan\u0131nd\u0131\u011f\u0131ndan emin olun.<\/span><\/p>\n

      Sunucu Taraf\u0131nda Yap\u0131land\u0131rma Kontrolleri<\/b><\/h2>\n

      Hata t\u00fcm kullan\u0131c\u0131larda g\u00f6r\u00fcl\u00fcyorsa sorun tek bir bilgisayarda de\u011fil sunucu yap\u0131land\u0131rmas\u0131ndad\u0131r. Bu durumda istemci do\u011frulama ayarlar\u0131n\u0131n ve sertifika zincirinin g\u00f6zden ge\u00e7irilmesi gerekir.<\/span><\/p>\n

      \u0130lk kontrol noktas\u0131, sunucunun ger\u00e7ekten istemci sertifikas\u0131 isteyip istemedi\u011fidir. Nginx ve Apache gibi sunucularda istemci do\u011frulamas\u0131 ayr\u0131 direktiflerle etkinle\u015ftirilir. Bu do\u011frulama iste\u011fe ba\u011fl\u0131 yerine zorunlu bi\u00e7imde yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131nda, uygun sertifika sunamayan her ziyaret\u00e7i ba\u011flant\u0131 kuramaz. Kar\u015f\u0131l\u0131kl\u0131 kimlik do\u011frulama yaln\u0131zca bir y\u00f6netim paneli veya API u\u00e7 noktas\u0131 i\u00e7in gerekiyorsa, k\u0131s\u0131t\u0131n t\u00fcm siteye de\u011fil ilgili konuma uygulanmas\u0131 daha do\u011fru bir yakla\u015f\u0131md\u0131r.<\/span><\/p>\n

      \u0130kinci kontrol noktas\u0131 g\u00fcven zinciridir. Sunucu, istemci sertifikas\u0131n\u0131 do\u011frulayabilmek i\u00e7in o sertifikay\u0131 imzalayan otoritenin k\u00f6k ve ara sertifikalar\u0131n\u0131 tan\u0131mal\u0131d\u0131r. CA dosyas\u0131 eksik, g\u00fcncellenmemi\u015f veya yanl\u0131\u015f yola i\u015faret ediyorsa ge\u00e7erli bir istemci sertifikas\u0131 bile reddedilir. \u0130ptal listesi kontrol\u00fc yap\u0131land\u0131r\u0131lm\u0131\u015fsa CRL dosyas\u0131n\u0131n g\u00fcncel olmas\u0131 ve zincirdeki her sertifika i\u00e7in kar\u015f\u0131l\u0131\u011f\u0131n\u0131 i\u00e7ermesi gerekir; eksik ya da s\u00fcresi dolmu\u015f bir CRL, ge\u00e7erli istemci sertifikalar\u0131n\u0131n da reddedilmesine yol a\u00e7ar. Sunucu g\u00fcnl\u00fcklerindeki TLS el s\u0131k\u0131\u015fma kay\u0131tlar\u0131, do\u011frulaman\u0131n hangi a\u015famada kesildi\u011fini g\u00f6rmenin en g\u00fcvenilir yoludur.<\/span><\/p>\n

      ERR_BAD_SSL_CLIENT_AUTH_CERT \u00c7\u00f6z\u00fcm\u00fcnde Dikkat Edilmesi Gerekenler<\/b><\/h2>\n

      Sertifika hatalar\u0131n\u0131 \u00e7\u00f6zerken at\u0131lan aceleci ad\u0131mlar, g\u00fcvenli\u011fi taray\u0131c\u0131 hatas\u0131ndan daha ciddi bi\u00e7imde zay\u0131flatabilir. \u0130nternette dola\u015fan baz\u0131 \u00f6neriler bu a\u00e7\u0131dan risklidir: taray\u0131c\u0131da sertifika hatalar\u0131n\u0131 g\u00f6rmezden gelen komut sat\u0131r\u0131 parametreleri kullanmak, g\u00fcvenlik yaz\u0131l\u0131m\u0131n\u0131n SSL denetimini kal\u0131c\u0131 olarak kapatmak veya kayna\u011f\u0131 belirsiz k\u00f6k sertifikalar\u0131 sisteme eklemek, sahte sertifikalar\u0131n da kabul edilmesine zemin haz\u0131rlar. Tan\u0131mad\u0131\u011f\u0131n\u0131z bir kaynaktan indirilen istemci sertifikas\u0131n\u0131 y\u00fcklemek ise kimlik bilgilerinizin k\u00f6t\u00fcye kullan\u0131lmas\u0131na yol a\u00e7abilir.<\/span><\/p>\n

      G\u00fcvenli bir yakla\u015f\u0131m i\u00e7in \u015fu ilkeleri g\u00f6zetin:<\/span><\/p>\n