G\u00fcn\u00fcm\u00fcz web d\u00fcnyas\u0131nda, bir web sitesinin istemci (taray\u0131c\u0131) ile sunucu aras\u0131ndaki ileti\u015fimini \u015fifrelemek yaln\u0131zca bir tercih de\u011fil, temel bir zorunluluktur. HTTPS protokolu, aktar\u0131lan verilerin \u00fc\u00e7\u00fcnc\u00fc \u015fah\u0131slar taraf\u0131ndan dinlenmesini (eavesdropping), de\u011fi\u015ftirilmesini (tampering) veya taklit edilmesini (man-in-the-middle sald\u0131r\u0131lar\u0131) engeller. Arama motorlar\u0131n\u0131n HTTPS kullanan sitelere \u00f6ncelik tan\u0131mas\u0131 ve modern taray\u0131c\u0131lar\u0131n HTTP ba\u011flant\u0131lar\u0131n\u0131 “G\u00fcvenli De\u011fil” olarak i\u015faretlemesi, SSL\/TLS sertifikalar\u0131n\u0131n kullan\u0131m\u0131n\u0131 zorunlu k\u0131lm\u0131\u015ft\u0131r.<\/p>\n
Bu kapsaml\u0131 teknik rehberde, Debian 10 (Buster) i\u015fletim sistemi \u00fczerinde \u00e7al\u0131\u015fan bir Nginx web sunucusunun, Let’s Encrypt taraf\u0131ndan sa\u011flanan \u00fccretsiz, otomatikle\u015ftirilmi\u015f ve g\u00fcvenilir bir SSL\/TLS sertifikas\u0131 ile nas\u0131l yap\u0131land\u0131r\u0131laca\u011f\u0131n\u0131 ad\u0131m ad\u0131m inceleyece\u011fiz. Ayr\u0131ca, sertifikasyon s\u00fcrecinin yan\u0131 s\u0131ra TLS protokol\u00fc s\u0131k\u0131la\u015ft\u0131rma, HSTS entegrasyonu, OCSP Stapling ve otomatik yenileme mekanizmalar\u0131n\u0131 da detayland\u0131raca\u011f\u0131z.<\/p>\n
SSL (Secure Sockets Layer) ve onun modern, daha g\u00fcvenli halefi olan TLS (Transport Layer Security), a\u011f \u00fczerindeki ileti\u015fimi \u015fifreleyen kriptografik protokollerdir. SSL\/TLS sertifikalar\u0131, asimetrik \u015fifreleme (a\u00e7\u0131k ve \u00f6zel anahtar \u00e7iftleri) kullanarak istemci ile sunucu aras\u0131nda g\u00fcvenli bir el s\u0131k\u0131\u015fma (handshake) ger\u00e7ekle\u015ftirir.<\/p>\n
Let me Encrypt, \u0130nternet G\u00fcvenli\u011fi Ara\u015ft\u0131rma Grubu (ISRG) taraf\u0131ndan sunulan \u00fccretsiz, otomatik ve a\u00e7\u0131k bir Sertifika Yetkilisidir (CA – Certificate Authority). Let’s Encrypt, manuel sertifika talep, do\u011frulama ve kurulum s\u00fcre\u00e7lerini ortadan kald\u0131rmak i\u00e7in Otomatik Sertifika Y\u00f6netim Ortam\u0131 (ACME – Automated Certificate Management Environment) protokol\u00fcn\u00fc kullan\u0131r. Certbot ise bu ACME protokol\u00fcn\u00fc uygulayan ve istemci taraf\u0131nda sertifika alma\/yenileme i\u015flemlerini otomatikle\u015ftiren a\u00e7\u0131k kaynakl\u0131 bir ara\u00e7t\u0131r.<\/p>\n
Certbot, sunucunuz ad\u0131na bir sertifika isteminde bulundu\u011funda, Let’s Encrypt CA sunucuya bir “meydan okuma” (challenge) g\u00f6nderir. HTTP-01 do\u011frulama t\u00fcr\u00fcnde, Certbot web sunucunuzun belirli bir dizinine ( Kuruluma ba\u015flamadan \u00f6nce, sisteminizde a\u015fa\u011f\u0131daki gereksinimlerin kar\u015f\u0131land\u0131\u011f\u0131ndan emin olman\u0131z gerekmektedir:<\/p>\n DNS de\u011fi\u015fikliklerinin k\u00fcresel olarak yay\u0131lmas\u0131 zaman alabilir. Sertifika alma i\u015flemine ge\u00e7meden \u00f6nce alan ad\u0131n\u0131z\u0131n do\u011fru IP adresine y\u00f6nlendi\u011fini komut sat\u0131r\u0131ndan do\u011frulaman\u0131z \u00f6nerilir:<\/p>\n D\u00f6nen \u00e7\u0131kt\u0131lar\u0131n sunucunuzun public IP adresi ile birebir e\u015fle\u015fti\u011finden emin olun.<\/p>\n Debian 10 (Buster) depolar\u0131nda Certbot ve Nginx entegrasyonunu sa\u011flayan resmi eklentiler mevcuttur. Kuruluma ba\u015flamadan \u00f6nce sistem paket listesini g\u00fcncelleyelim.<\/p>\n Paket veritaban\u0131 g\u00fcncellendikten sonra, Certbot ve Python tabanl\u0131 Nginx eklentisi olan Kurulum tamamland\u0131ktan sonra Certbot’un sistemde do\u011fru \u015fekilde y\u00fcklendi\u011fini kontrol etmek i\u00e7in versiyon bilgisini sorgulayabilirsiniz:<\/p>\n Certbot’un Nginx i\u00e7in otomatik SSL yap\u0131land\u0131rmas\u0131 yapabilmesi i\u00e7in, Nginx yap\u0131land\u0131rma dosyalar\u0131n\u0131zda \u00d6rnek bir Nginx konfig\u00fcrasyon dosyas\u0131n\u0131 (genellikle Dosya i\u00e7eri\u011finin a\u015fa\u011f\u0131daki gibi temel bir HTTP konfig\u00fcrasyonuna sahip oldu\u011fundan emin olun:<\/p>\n E\u011fer dosya yeni olu\u015fturulduysa, bu konfig\u00fcrasyonu aktifle\u015ftirmek i\u00e7in Nginx yap\u0131land\u0131rman\u0131zda herhangi bir s\u00f6zdizimi (syntax) hatas\u0131 olup olmad\u0131\u011f\u0131n\u0131 test edin:<\/p>\n E\u011fer \u00e7\u0131kt\u0131 E\u011fer Debian sunucunuzda varsay\u0131lan g\u00fcvenlik duvar\u0131 olarak UFW (Uncomplicated Firewall) aktif durumda ise, varsay\u0131lan HTTP (Port 80) ve HTTPS (Port 443) trafi\u011fine izin vermeniz gerekmektedir.<\/p>\n Mevcut UFW durumunu ve profillerini inceleyin:<\/p>\n Nginx, UFW i\u00e7in haz\u0131r profiller sunar. Bu profilleri listelemek i\u00e7in:<\/p>\n \u00c7\u0131kt\u0131da ‘Nginx Full’, ‘Nginx HTTP’ ve ‘Nginx HTTPS’ profillerini g\u00f6receksiniz. HTTPS trafi\u011fine izin vermek i\u00e7in ‘Nginx Full’ profilini etkinle\u015ftirmemiz gerekir:<\/p>\n Yap\u0131land\u0131rma sonras\u0131nda durum tekrar kontrol edildi\u011finde Port 80 ve Port 443 ge\u00e7i\u015flerine izin verildi\u011fi do\u011frulanmal\u0131d\u0131r.<\/p>\n Certbot, Nginx eklentisi sayesinde sertifika alma ve konfig\u00fcrasyon dosyas\u0131n\u0131 g\u00fcncelleme s\u00fcrecini tek bir komutla halledebilir. Sertifikay\u0131 almak i\u00e7in a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n Bu komut \u00e7al\u0131\u015ft\u0131r\u0131ld\u0131\u011f\u0131nda Certbot etkile\u015fimli bir kurulum ba\u015flat\u0131r. S\u0131ras\u0131yla \u015fu ad\u0131mlar ger\u00e7ekle\u015fir:<\/p>\n Se\u00e7iminizi yap\u0131p Sertifikalar\u0131n\u0131z sunucunuzda Let’s Encrypt taraf\u0131ndan verilen SSL\/TLS sertifikalar\u0131 90 g\u00fcn s\u00fcreyle ge\u00e7erlidir. Bu k\u0131sa s\u00fcre, \u00e7al\u0131nan anahtarlar\u0131n etki alan\u0131n\u0131 daraltmak ve g\u00fcvenli\u011fi art\u0131rmak amac\u0131yla uygulan\u0131r. Certbot, Debian 10 \u00fczerinde sistem arka plan\u0131nda \u00e7al\u0131\u015fan bir Sisteminizdeki otomasyon zamanlay\u0131c\u0131s\u0131n\u0131n aktif olup olmad\u0131\u011f\u0131n\u0131 kontrol etmek i\u00e7in a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n Bu zamanlay\u0131c\u0131, g\u00fcnde iki kez \u00e7al\u0131\u015farak s\u00fcresi bitmesine 30 g\u00fcnden az kalm\u0131\u015f sertifikalar\u0131 tespit eder ve otomatik olarak yeniler.<\/p>\n Yenileme s\u00fcrecinde herhangi bir yap\u0131land\u0131rma hatas\u0131 veya a\u011f engeli ya\u015fan\u0131p ya\u015fanmayaca\u011f\u0131n\u0131 anlamak i\u00e7in ger\u00e7ek bir sertifika isteminde bulunmadan sim\u00fclasyon (dry-run) yapabilirsiniz:<\/p>\n E\u011fer \u00e7\u0131kt\u0131n\u0131n sonunda Certbot varsay\u0131lan olarak g\u00fcvenli bir yap\u0131land\u0131rma sunsa da, sunucunuzun SSL Labs veya benzeri g\u00fcvenlik testlerinden A+ alabilmesi i\u00e7in ek kryptografik s\u0131k\u0131la\u015ft\u0131rmalar yap\u0131lmas\u0131 tavsiye edilir.<\/p>\n Diffie-Hellman (DH) anahtar de\u011fi\u015fimi, istemci ve sunucunun g\u00fcvensiz bir kanal \u00fczerinden g\u00fcvenli bir \u015fekilde gizli anahtar olu\u015fturmas\u0131n\u0131 sa\u011flar. Varsay\u0131lan 1024-bit DH parametreleri yerine 2048-bit g\u00fc\u00e7l\u00fc bir parametre grubu olu\u015fturmak g\u00fcvenli\u011fi \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131r\u0131r:<\/p>\n Not: Bu i\u015flem sunucu i\u015flemci g\u00fcc\u00fcne ba\u011fl\u0131 olarak birka\u00e7 dakika s\u00fcrebilir.<\/em><\/p>\n Nginx SSL ayarlar\u0131n\u0131 global olarak optimize etmek i\u00e7in ortak bir yap\u0131land\u0131rma par\u00e7as\u0131 (snippet) olu\u015ftural\u0131m:<\/p>\n A\u015fa\u011f\u0131daki parametreleri dosya i\u00e7erisine ekleyin. Bu yap\u0131land\u0131rma eski ve zay\u0131f kabul edilen SSLv2, SSLv3, TLSv1.0 ve TLSv1.1 protokollerini devre d\u0131\u015f\u0131 b\u0131rak\u0131r, yaln\u0131zca TLSv1.2 ve TLSv1.3 kullan\u0131lmas\u0131na izin verir.<\/p>\n \u015eimdi Nginx sanal konak dosyam\u0131z\u0131 g\u00fcncelleyerek Certbot’un olu\u015fturdu\u011fu ayarlar\u0131 ve yeni ekledi\u011fimiz g\u00fcvenlik parametrelerini birle\u015ftirelim:<\/p>\n Yap\u0131land\u0131rman\u0131z nihai olarak a\u015fa\u011f\u0131daki yap\u0131ya benzer olmal\u0131d\u0131r:<\/p>\n De\u011fi\u015fikliklerin ge\u00e7erli olabilmesi i\u00e7in konfig\u00fcrasyon testini yap\u0131n ve Nginx’i yeniden ba\u015flat\u0131n:<\/p>\n Sertifika al\u0131rken veya Nginx SSL yap\u0131land\u0131rmas\u0131nda kar\u015f\u0131la\u015f\u0131labilecek olas\u0131 problemler ve \u00e7\u00f6z\u00fcm y\u00f6ntemleri \u015funlard\u0131r:<\/p>\n Bu hata, Let’s Encrypt sunucular\u0131n\u0131n alan ad\u0131n\u0131za HTTP (Port 80) \u00fczerinden eri\u015femedi\u011fi anlam\u0131na gelir.<\/p>\n Let’s Encrypt, k\u00f6t\u00fcye kullan\u0131m\u0131 engellemek i\u00e7in belirli bir alan ad\u0131 i\u00e7in haftal\u0131k sertifika alma s\u0131n\u0131r\u0131 (rate limit) uygular.<\/p>\n Siteniz HTTPS \u00fczerinden y\u00fcklense de HTML kodlar\u0131 i\u00e7indeki g\u00f6rseller, CSS veya JavaScript dosyalar\u0131 .well-known\/acme-challenge\/<\/code>) ge\u00e7ici bir token dosyas\u0131 yerle\u015ftirir. Let’s Encrypt CA sunucusu, belirtilen alan ad\u0131 \u00fczerinden bu dosyaya HTTP iste\u011fi atarak eri\u015fmeye \u00e7al\u0131\u015f\u0131r. Eri\u015fim ba\u015far\u0131l\u0131 olursa, alan ad\u0131n\u0131n kontrol\u00fcn\u00fcn ger\u00e7ekten sizde oldu\u011fu do\u011frulan\u0131r ve dijital olarak imzalanm\u0131\u015f SSL\/TLS sertifikas\u0131 sunucunuza iletilir.<\/p>\n2. \u00d6n Gereksinimler ve Sistem Haz\u0131rl\u0131\u011f\u0131<\/h2>\n
\n
sudo<\/code> yetkilerine sahip root d\u0131\u015f\u0131 bir kullan\u0131c\u0131 hesab\u0131.<\/li>\nornekdomain.com<\/code> ve www.ornekdomain.com<\/code> ifadeleri kullan\u0131lacakt\u0131r.<\/li>\nDNS Kay\u0131tlar\u0131n\u0131n Kontrol Edilmesi<\/h3>\n
dig A ornekdomain.com +short\ndig A www.ornekdomain.com +short<\/code><\/pre>\n3. Ad\u0131m 1: Certbot ve Nginx Eklentisinin Debian 10 \u00dczerine Kurulmas\u0131<\/h2>\n
sudo apt update\nsudo apt upgrade -y<\/code><\/pre>\npython3-certbot-nginx<\/code> paketini y\u00fckleyebiliriz. Bu eklenti, Nginx konfig\u00fcrasyon dosyalar\u0131n\u0131 otomatik olarak okuma, SSL bloklar\u0131n\u0131 yazma ve web sunucusunu yeniden ba\u015flatma yetene\u011fine sahiptir.<\/p>\nsudo apt install certbot python3-certbot-nginx -y<\/code><\/pre>\ncertbot --version<\/code><\/pre>\n4. Ad\u0131m 2: Nginx Konfig\u00fcrasyonunun Do\u011frulanmas\u0131<\/h2>\n
server_name<\/code> y\u00f6nergesinin do\u011fru tan\u0131mlanm\u0131\u015f olmas\u0131 \u015fartt\u0131r. Certbot, mevcut bloklar\u0131 tarayarak alan ad\u0131n\u0131zla e\u015fle\u015fen sanal konak (Virtual Host \/ Server Block) yap\u0131s\u0131n\u0131 tespit eder.<\/p>\n\/etc\/nginx\/sites-available\/ornekdomain.com<\/code>) kontrol edelim veya olu\u015ftural\u0131m:<\/p>\nsudo nano \/etc\/nginx\/sites-available\/ornekdomain.com<\/code><\/pre>\nserver {\n listen 80;\n listen [::]:80;\n\n server_name ornekdomain.com www.ornekdomain.com;\n\n root \/var\/www\/ornekdomain.com\/html;\n index index.html index.htm;\n\n location \/ {\n try_files $uri $uri\/ =404;\n }\n}<\/code><\/pre>\nsites-enabled<\/code> dizinine bir sembolik ba\u011f (symlink) olu\u015fturman\u0131z gerekir:<\/p>\nsudo ln -s \/etc\/nginx\/sites-available\/ornekdomain.com \/etc\/nginx\/sites-enabled\/<\/code><\/pre>\nsudo nginx -t<\/code><\/pre>\nsyntax is ok<\/code> ve test is successful<\/code> mesajlar\u0131n\u0131 d\u00f6n\u00fcyorsa, Nginx servisini yeniden y\u00fckleyin:<\/p>\nsudo systemctl reload nginx<\/code><\/pre>\n5. Ad\u0131m 3: G\u00fcvenlik Duvar\u0131 (UFW) Ayarlar\u0131n\u0131n G\u00fcncellenmesi<\/h2>\n
sudo ufw status<\/code><\/pre>\nsudo ufw app list<\/code><\/pre>\nsudo ufw allow 'Nginx Full'\nsudo ufw delete allow 'Nginx HTTP'<\/code><\/pre>\n6. Ad\u0131m 4: Let’s Encrypt SSL\/TLS Sertifikas\u0131n\u0131n Al\u0131nmas\u0131<\/h2>\n
sudo certbot --nginx -d ornekdomain.com -d www.ornekdomain.com<\/code><\/pre>\n\n
A<\/code> (Agree) tu\u015funa basman\u0131z gerekir.<\/li>\nY<\/code> veya N<\/code>).<\/li>\n\n
1: No redirect<\/code> – Nginx konfig\u00fcrasyonu de\u011fi\u015ftirilmez. HTTP ve HTTPS ayr\u0131 \u00e7al\u0131\u015f\u0131r.<\/li>\n2: Redirect<\/code> – T\u00fcm HTTP istekleri otomatik olarak 301 (Permanent Redirect) ile HTTPS’e y\u00f6nlendirilir. (\u00d6nerilen Se\u00e7enek: 2<\/strong>)<\/li>\n<\/ul>\n<\/li>\n<\/ol>\nEnter<\/code> tu\u015funa bast\u0131\u011f\u0131n\u0131zda Certbot, Nginx konfig\u00fcrasyon dosyan\u0131z\u0131 g\u00fcncelleyecek ve Nginx servisini otomatik olarak yeniden y\u00fckleyecektir.<\/p>\n\u00dcretilen Sertifika Dosyalar\u0131n\u0131n \u0130ncelemesi<\/h3>\n
\/etc\/letsencrypt\/live\/ornekdomain.com\/<\/code> dizini alt\u0131nda saklan\u0131r. Bu dizinde bulunan kritik dosyalar \u015funlard\u0131r:<\/p>\n\n\n
\n \nDosya Ad\u0131<\/th>\n A\u00e7\u0131klama<\/th>\n<\/tr>\n<\/thead>\n \n privkey.pem<\/code><\/td>\nSertifikan\u0131n \u00d6zel Anahtar\u0131 (Private Key). Kesinlikle gizli tutulmal\u0131d\u0131r.<\/strong><\/td>\n<\/tr>\n \n fullchain.pem<\/code><\/td>\nSunucu sertifikan\u0131z ile Let’s Encrypt ara sertifikalar\u0131n\u0131n (intermediate certificates) birle\u015fimi olan ana sertifika dosyas\u0131.<\/td>\n<\/tr>\n \n cert.pem<\/code><\/td>\nSadece alan ad\u0131n\u0131za ait yal\u0131n sunucu sertifikas\u0131.<\/td>\n<\/tr>\n \n chain.pem<\/code><\/td>\nLet’s Encrypt zincir\/ara sertifikalar\u0131.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n 7. Ad\u0131m 5: Otomatik Sertifika Yenilemesinin (Auto-Renewal) Test Edilmesi<\/h2>\n
systemd timer<\/code> veya cron job<\/code> mekanizmas\u0131 ile birlikte gelir.<\/p>\nsudo systemctl status certbot.timer<\/code><\/pre>\nKuru \u00c7al\u0131\u015fma (Dry-Run) Testi<\/h3>\n
sudo certbot renew --dry-run<\/code><\/pre>\nCongratulations, all simulated renewals succeeded<\/code> mesaj\u0131n\u0131 g\u00f6r\u00fcyorsan\u0131z, otomatik yenileme mekanizman\u0131z sorunsuz bir \u015fekilde yap\u0131land\u0131r\u0131lm\u0131\u015f demektir.<\/p>\n8. Ad\u0131m 6: Nginx SSL\/TLS G\u00fcvenli\u011fini S\u0131k\u0131la\u015ft\u0131rma (Hardening)<\/h2>\n
A. Diffie-Hellman Parametrelerinin Olu\u015fturulmas\u0131<\/h3>\n
sudo openssl dhparam -out \/etc\/ssl\/certs\/dhparam.pem 2048<\/code><\/pre>\nB. Nginx SSL Konfig\u00fcrasyonunun \u0130yile\u015ftirilmesi<\/h3>\n
sudo nano \/etc\/nginx\/conf.d\/ssl-params.conf<\/code><\/pre>\n# TLS Protokol Seviyeleri\nssl_protocols TLSv1.2 TLSv1.3;\n\nG\u00fc\u00e7l\u00fc \u015eifreleme Algoritmalar\u0131 (Cipher Suites)<\/h2>\nssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;\nssl_prefer_server_ciphers off;\n\n
Diffie-Hellman Parametresi<\/h2>\nssl_dhparam \/etc\/ssl\/certs\/dhparam.pem;\n\n
SSL Session Ayarlar\u0131<\/h2>\nssl_session_timeout 1d;\nssl_session_cache shared:SSL:10m;\nssl_session_tickets off;\n\n
OCSP Stapling (Sunucu Taraf\u0131nda Sertifika Durum Do\u011frulamas\u0131)<\/h2>\nssl_stapling on;\nssl_stapling_verify on;\nresolver 8.8.8.8 8.8.4.4 valid=300s;\nresolver_timeout 5s;\n\n
HSTS (HTTP Strict Transport Security) - 1 Y\u0131l S\u00fcreyle zorunlu HTTPS<\/h2>\nadd_header Strict-Transport-Security \"max-age=63072000; includeSubDomains; preload\" always;\n\n
G\u00fcvenlik Ba\u015fl\u0131klar\u0131 (Security Headers)<\/h2>\nadd_header X-Frame-Options DENY;\nadd_header X-Content-Type-Options nosniff;\nadd_header X-XSS-Protection \"1; mode=block\";<\/code><\/pre>\n
C. Nginx Server Blo\u011funun G\u00fcncellenmesi<\/h3>\n
sudo nano \/etc\/nginx\/sites-available\/ornekdomain.com<\/code><\/pre>\nserver {\n listen 80;\n listen [::]:80;\n server_name ornekdomain.com www.ornekdomain.com;\n\n # HTTP isteklerini HTTPS'e 301 y\u00f6nlendirmesi\n return 301 https:\/\/$host$request_uri;\n}\n\nserver {\n listen 443 ssl http2;\n listen [::]:443 ssl http2;\n server_name ornekdomain.com www.ornekdomain.com;\n\n root \/var\/www\/ornekdomain.com\/html;\n index index.html index.htm;\n\n # Let's Encrypt Sertifika Yollar\u0131\n ssl_certificate \/etc\/letsencrypt\/live\/ornekdomain.com\/fullchain.pem;\n ssl_certificate_key \/etc\/letsencrypt\/live\/ornekdomain.com\/privkey.pem;\n\n # \u00d6zel SSL Parametrelerinin Dahil Edilmesi\n include \/etc\/nginx\/conf.d\/ssl-params.conf;\n\n location \/ {\n try_files $uri $uri\/ =404;\n }\n}<\/code><\/pre>\nsudo nginx -t\nsudo systemctl restart nginx<\/code><\/pre>\n9. S\u0131k Kar\u015f\u0131la\u015f\u0131lan Sorunlar ve \u00c7\u00f6z\u00fcm Yollar\u0131 (Troubleshooting)<\/h2>\n
1. “Failed authorization procedure” \/ HTTP-01 Challenge Ba\u015far\u0131s\u0131zl\u0131\u011f\u0131<\/h3>\n
\n
2. “Too Many Requests” (Rate Limit) Hatas\u0131<\/h3>\n
\n
--dry-run<\/code> parametresini ekleyerek Let’s Encrypt Staging ortam\u0131n\u0131 kullan\u0131n. Limit tak\u0131lmas\u0131 durumunda \u00fcretim ortam\u0131nda bir s\u00fcre beklemeniz gerekecektir.<\/li>\n<\/ul>\n3. Mixed Content (Karma \u0130\u00e7erik) Uyar\u0131lar\u0131<\/h3>\n
http:\/\/<\/code> protokol\u00fc ile \u00e7a\u011fr\u0131l\u0131yorsa taray\u0131c\u0131lar uyar\u0131 verecektir.<\/p>\n