{"id":32071,"date":"2025-10-17T10:41:10","date_gmt":"2025-10-17T07:41:10","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=32071"},"modified":"2025-10-17T10:41:10","modified_gmt":"2025-10-17T07:41:10","slug":"nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/","title":{"rendered":"Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu"},"content":{"rendered":"<p><body><\/p>\n<h2>Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu<\/h2>\n<h2>Giri\u015f<\/h2>\n<p>G\u00fcn\u00fcm\u00fcz internet d\u00fcnyas\u0131nda g\u00fcvenlik, kullan\u0131c\u0131 g\u00fcveni ve arama motoru s\u0131ralamalar\u0131 i\u00e7in vazge\u00e7ilmez bir unsurdur. Web sitelerinin HTTPS protokol\u00fc \u00fczerinden yay\u0131n yapmas\u0131, yani SSL\/TLS (Secure Sockets Layer\/Transport Layer Security) sertifikalar\u0131 ile \u015fifrelenmesi, art\u0131k bir standart haline gelmi\u015ftir. HTTPS, kullan\u0131c\u0131 ile sunucu aras\u0131ndaki t\u00fcm ileti\u015fimi \u015fifreleyerek veri b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc ve gizlili\u011fini sa\u011flar. \u00d6zellikle ki\u015fisel bilgiler, \u00f6deme detaylar\u0131 veya hassas veriler i\u00e7eren web siteleri i\u00e7in bu \u015fifreleme kritik \u00f6neme sahiptir.<\/p>\n<p>Bir\u00e7ok kurulu\u015f ve geli\u015ftirici, tek bir sunucu ve IP adresi \u00fczerinde birden fazla web sitesi bar\u0131nd\u0131rma ihtiyac\u0131 duyar. Geleneksel olarak, her bir SSL sertifikas\u0131 farkl\u0131 bir IP adresi gerektirirdi ki bu da IP adresi k\u0131tl\u0131\u011f\u0131 ve maliyet a\u00e7\u0131s\u0131ndan sorunlara yol a\u00e7\u0131yordu. Ancak Server Name Indication (SNI) teknolojisi sayesinde, tek bir IP adresi \u00fczerinde birden fazla alan ad\u0131 i\u00e7in ayr\u0131 ayr\u0131 SSL sertifikalar\u0131n\u0131 ba\u015far\u0131yla kullanmak m\u00fcmk\u00fcn hale gelmi\u015ftir. Nginx gibi modern web sunucular\u0131, SNI deste\u011fi sayesinde bu karma\u015f\u0131k g\u00f6r\u00fcnen yap\u0131land\u0131rmay\u0131 olduk\u00e7a basit ve verimli bir \u015fekilde y\u00f6netebilir.<\/p>\n<p>Bu makalede, pop\u00fcler bir web sunucusu olan Nginx&#8217;i ve yayg\u0131n olarak kullan\u0131lan i\u015fletim sistemi Ubuntu&#8217;nun 12.04 s\u00fcr\u00fcm\u00fcn\u00fc kullanarak, tek bir IP adresi \u00fczerinde birden fazla SSL sertifikas\u0131n\u0131n nas\u0131l kurulaca\u011f\u0131n\u0131 ve yap\u0131land\u0131r\u0131laca\u011f\u0131n\u0131 ad\u0131m ad\u0131m ele alaca\u011f\u0131z. Ubuntu 12.04&#8217;\u00fcn eski bir s\u00fcr\u00fcm olmas\u0131na ra\u011fmen, bu rehber o d\u00f6nemki Nginx ve OpenSSL versiyonlar\u0131n\u0131n SNI deste\u011fini nas\u0131l kulland\u0131\u011f\u0131n\u0131 detayland\u0131racakt\u0131r. Amac\u0131m\u0131z, hem teorik bilgiyi hem de pratik uygulama ad\u0131mlar\u0131n\u0131 bir araya getirerek, bu konuda eksiksiz bir kaynak sunmakt\u0131r.<\/p>\n<h2>\u00d6n Ko\u015fullar<\/h2>\n<p>Bu rehbere ba\u015flamadan \u00f6nce a\u015fa\u011f\u0131daki \u00f6n ko\u015fullar\u0131n yerine getirildi\u011finden emin olmal\u0131s\u0131n\u0131z:<\/p>\n<p>*   <strong>Ubuntu 12.04 Kurulu Sunucu:<\/strong> SSH eri\u015fimi olan, root veya sudo yetkilerine sahip bir Ubuntu 12.04 sunucunuz olmal\u0131d\u0131r.<br \/>\n*   <strong>Nginx Kurulumu:<\/strong> Nginx web sunucusu sunucunuzda kurulu olmal\u0131d\u0131r. E\u011fer kurulu de\u011filse, sonraki b\u00f6l\u00fcmlerde nas\u0131l kurulaca\u011f\u0131na dair k\u0131sa bir bilgi verilecektir. Ubuntu 12.04 depolar\u0131ndaki Nginx s\u00fcr\u00fcm\u00fcn\u00fcn (genellikle 1.1.x serisi) SNI deste\u011fi bulunmaktad\u0131r.<br \/>\n*   <strong>Alan Adlar\u0131 ve DNS Kay\u0131tlar\u0131:<\/strong> Birden fazla web sitesi bar\u0131nd\u0131raca\u011f\u0131n\u0131z i\u00e7in, en az iki farkl\u0131 alan ad\u0131n\u0131z (\u00f6rne\u011fin, <code>www.domain1.com<\/code> ve <code>www.domain2.com<\/code>) olmal\u0131 ve bu alan adlar\u0131n\u0131n DNS A kay\u0131tlar\u0131 sunucunuzun tek IP adresine i\u015faret etmelidir.<br \/>\n*   <strong>SSL Sertifikalar\u0131:<\/strong> Her bir alan ad\u0131n\u0131z i\u00e7in ayr\u0131 ayr\u0131 SSL sertifikalar\u0131na sahip olman\u0131z gerekmektedir. Bu sertifikalar \u00fccretli bir sertifika sa\u011flay\u0131c\u0131s\u0131ndan (Comodo, DigiCert, GoDaddy vb.) al\u0131nm\u0131\u015f olabilece\u011fi gibi, Let&#8217;s Encrypt gibi \u00fccretsiz sertifika sa\u011flayan kurulu\u015flardan da edinilebilir. Sertifikalar\u0131n\u0131z genellikle <code>domain.crt<\/code> (genel sertifika), <code>domain.key<\/code> (\u00f6zel anahtar) ve <code>ca_bundle.crt<\/code> veya <code>domain_chain.crt<\/code> (ara sertifikalar) dosyalar\u0131n\u0131 i\u00e7erecektir. Baz\u0131 durumlarda, <code>fullchain.crt<\/code> ad\u0131 alt\u0131nda genel sertifika ve ara sertifikalar tek bir dosyada birle\u015ftirilmi\u015f olabilir.<br \/>\n*   <strong>Firewall Ayarlar\u0131:<\/strong> Sunucunuzda bir g\u00fcvenlik duvar\u0131 (\u00f6rne\u011fin UFW) etkinse, HTTP (port 80) ve HTTPS (port 443) trafi\u011fine izin verdi\u011finden emin olun.<\/p>\n<h2>SSL Sertifikalar\u0131n\u0131 Anlamak<\/h2>\n<p>Nginx yap\u0131land\u0131rmas\u0131na ge\u00e7meden \u00f6nce, SSL sertifikalar\u0131n\u0131n temel bile\u015fenlerini ve t\u00fcrlerini anlamak faydal\u0131 olacakt\u0131r.<\/p>\n<h3>Sertifika T\u00fcrleri<\/h3>\n<p>*   <strong>Domain Validated (DV):<\/strong> En temel ve en h\u0131zl\u0131 al\u0131nan sertifika t\u00fcr\u00fcd\u00fcr. Sadece alan ad\u0131n\u0131n sahipli\u011fini do\u011frular. Genellikle ki\u015fisel bloglar, k\u00fc\u00e7\u00fck i\u015fletme siteleri i\u00e7in yeterlidir. Let&#8217;s Encrypt sertifikalar\u0131 DV t\u00fcr\u00fcndedir.<br \/>\n*   <strong>Organization Validated (OV):<\/strong> Alan ad\u0131n\u0131n sahipli\u011finin yan\u0131 s\u0131ra, kurulu\u015fun ger\u00e7ekli\u011fini de do\u011frular. Daha y\u00fcksek g\u00fcven sa\u011flar ve genellikle kurumsal web siteleri i\u00e7in tercih edilir.<br \/>\n*   <strong>Extended Validation (EV):<\/strong> En y\u00fcksek do\u011frulama seviyesine sahip sertifikad\u0131r. Alan ad\u0131 ve kurulu\u015f do\u011frulamas\u0131n\u0131n yan\u0131 s\u0131ra, kapsaml\u0131 bir yasal ve fiziksel do\u011frulama s\u00fcreci gerektirir. Taray\u0131c\u0131lar\u0131n adres \u00e7ubu\u011funda genellikle kurulu\u015fun ad\u0131n\u0131 ye\u015fil renkte g\u00f6sterir.<\/p>\n<h3>Sertifika Dosyalar\u0131<\/h3>\n<p>Bir SSL sertifikas\u0131 sat\u0131n ald\u0131\u011f\u0131n\u0131zda veya olu\u015fturdu\u011funuzda, genellikle a\u015fa\u011f\u0131daki dosya t\u00fcrlerini elde edersiniz:<\/p>\n<p>*   <strong>Public Certificate (<code>.crt<\/code> veya <code>.pem<\/code>):<\/strong> Bu dosya, web sitenizin genel sertifikas\u0131n\u0131 i\u00e7erir. Taray\u0131c\u0131lar bu sertifikay\u0131 kullanarak sunucunuzun kimli\u011fini do\u011frular. \u00d6rnek: <code>domain.com.crt<\/code>.<br \/>\n*   <strong>Private Key (<code>.key<\/code> veya <code>.pem<\/code>):<\/strong> Bu dosya, sertifikan\u0131zla e\u015fle\u015fen \u00f6zel anahtar\u0131 i\u00e7erir. Bu anahtar, sunucu taraf\u0131ndan gelen trafi\u011fi \u015fifrelemek ve \u015fifresini \u00e7\u00f6zmek i\u00e7in kullan\u0131l\u0131r. \u00d6zel anahtar\u0131n\u0131z\u0131n kesinlikle gizli tutulmas\u0131 ve g\u00fcvenli bir \u015fekilde saklanmas\u0131 gerekmektedir. \u00d6rnek: <code>domain.com.key<\/code>.<br \/>\n*   <strong>Intermediate Certificates \/ CA Bundle (<code>_chain.crt<\/code>, <code>ca_bundle.crt<\/code> veya <code>intermediate.crt<\/code>):<\/strong> Bu dosyalar, sertifikan\u0131z\u0131 veren kurulu\u015fun (Certificate Authority &#8211; CA) ara sertifikalar\u0131n\u0131 i\u00e7erir. Taray\u0131c\u0131lar\u0131n, sizin sertifikan\u0131z\u0131 g\u00fcven zincirindeki k\u00f6k sertifikaya kadar do\u011frulayabilmesi i\u00e7in bu ara sertifikalara ihtiyac\u0131 vard\u0131r. \u00d6rnek: <code>domain.com_chain.crt<\/code>.<br \/>\n*   <strong>Fullchain Certificate (<code>fullchain.crt<\/code>):<\/strong> Baz\u0131 sertifika sa\u011flay\u0131c\u0131lar\u0131 veya ara\u00e7lar (\u00f6zellikle Let&#8217;s Encrypt), genel sertifikay\u0131 ve ara sertifikalar\u0131 tek bir dosyada birle\u015ftirerek <code>fullchain.crt<\/code> ad\u0131nda bir dosya sunar. Bu dosya, Nginx yap\u0131land\u0131rmas\u0131n\u0131 basitle\u015ftirebilir.<\/p>\n<p>Her alan ad\u0131n\u0131z i\u00e7in bu dosyalar\u0131n do\u011fru ve g\u00fcvenli bir \u015fekilde elde edildi\u011finden ve sunucunuzda uygun bir dizine kopyaland\u0131\u011f\u0131ndan emin olun.<\/p>\n<h2>Nginx Kurulumu ve Temel Yap\u0131land\u0131rma (Ubuntu 12.04)<\/h2>\n<p>E\u011fer Nginx sunucunuzda kurulu de\u011filse, a\u015fa\u011f\u0131daki ad\u0131mlar\u0131 izleyerek kurabilirsiniz.<\/p>\n<h3>Nginx Kurulumu<\/h3>\n<p>Ubuntu 12.04&#8217;te Nginx&#8217;i y\u00fcklemek i\u00e7in apt paket y\u00f6neticisini kullanaca\u011f\u0131z:<\/p>\n<pre><code class=\"language-bash\">sudo apt-get update           # Paket listelerini g\u00fcnceller\nsudo apt-get install nginx    # Nginx'i kurar<\/code><\/pre>\n<p>Kurulum tamamland\u0131ktan sonra Nginx servisi otomatik olarak ba\u015flayabilir. Taray\u0131c\u0131n\u0131zdan sunucunuzun IP adresini ziyaret ederek Nginx&#8217;in varsay\u0131lan &#8220;Welcome to Nginx!&#8221; sayfas\u0131n\u0131 g\u00f6r\u00fcp g\u00f6rmedi\u011finizi kontrol edebilirsiniz.<\/p>\n<h3>Nginx Hizmet Y\u00f6netimi<\/h3>\n<p>Nginx servisini y\u00f6netmek i\u00e7in a\u015fa\u011f\u0131daki komutlar\u0131 kullanabilirsiniz:<\/p>\n<pre><code class=\"language-bash\">sudo service nginx start      # Nginx servisini ba\u015flat\u0131r\nsudo service nginx stop       # Nginx servisini durdurur\nsudo service nginx restart    # Nginx servisini yeniden ba\u015flat\u0131r (yap\u0131land\u0131rma de\u011fi\u015fikliklerinden sonra s\u0131k kullan\u0131l\u0131r)\nsudo service nginx reload     # Nginx yap\u0131land\u0131rmas\u0131n\u0131 yeniden y\u00fckler (servisi tamamen durdurup ba\u015flatmadan)\nsudo service nginx status     # Nginx servisinin durumunu g\u00f6sterir<\/code><\/pre>\n<h3>Varsay\u0131lan Yap\u0131land\u0131rma Dosyalar\u0131<\/h3>\n<p>Nginx&#8217;in ana yap\u0131land\u0131rma dosyalar\u0131 Ubuntu&#8217;da <code>\/etc\/nginx\/<\/code> dizini alt\u0131nda bulunur:<\/p>\n<p>*   <code>\/etc\/nginx\/nginx.conf<\/code>: Nginx&#8217;in ana yap\u0131land\u0131rma dosyas\u0131d\u0131r. Genel ayarlar, mod\u00fcl y\u00fcklemeleri ve di\u011fer yap\u0131land\u0131rma dosyalar\u0131n\u0131n dahil edildi\u011fi yerdir.<br \/>\n*   <code>\/etc\/nginx\/sites-available\/<\/code>: Bu dizin, farkl\u0131 web siteleri (sanal hostlar) i\u00e7in yap\u0131land\u0131rma dosyalar\u0131n\u0131 i\u00e7erir. Bu dosyalardaki yap\u0131land\u0131rmalar varsay\u0131lan olarak etkin de\u011fildir.<br \/>\n*   <code>\/etc\/nginx\/sites-enabled\/<\/code>: Bu dizin, <code>\/etc\/nginx\/sites-available\/<\/code> dizinindeki dosyalar\u0131n sembolik ba\u011flant\u0131lar\u0131n\u0131 i\u00e7erir. Nginx, yaln\u0131zca bu dizindeki yap\u0131land\u0131rma dosyalar\u0131n\u0131 okuyarak siteleri etkinle\u015ftirir.<\/p>\n<h3>UFW Firewall Ayarlar\u0131<\/h3>\n<p>E\u011fer Ubuntu sunucunuzda UFW (Uncomplicated Firewall) etkinse, Nginx&#8217;in gelen HTTP ve HTTPS isteklerini alabilmesi i\u00e7in ilgili portlar\u0131 a\u00e7man\u0131z gerekir:<\/p>\n<pre><code class=\"language-bash\">sudo ufw allow 'Nginx HTTP'   # HTTP (port 80) trafi\u011fine izin verir\nsudo ufw allow 'Nginx HTTPS'  # HTTPS (port 443) trafi\u011fine izin verir\nsudo ufw enable               # G\u00fcvenlik duvar\u0131n\u0131 etkinle\u015ftirir (e\u011fer etkin de\u011filse)\nsudo ufw status               # G\u00fcvenlik duvar\u0131 durumunu ve kurallar\u0131n\u0131 g\u00f6sterir<\/code><\/pre>\n<p>Bu komutlar\u0131 \u00e7al\u0131\u015ft\u0131rd\u0131ktan sonra, hem HTTP hem de HTTPS trafi\u011fi Nginx&#8217;e ula\u015fabilecektir.<\/p>\n<h2>SSL Sertifikalar\u0131n\u0131 Sunucuya Kopyalama<\/h2>\n<p>Her bir alan ad\u0131n\u0131z i\u00e7in edindi\u011finiz SSL sertifikas\u0131 dosyalar\u0131n\u0131 (CRT, KEY, CHAIN\/Bundle) sunucunuzdaki g\u00fcvenli bir konuma kopyalaman\u0131z gerekmektedir. Nginx&#8217;in kolayca eri\u015febilece\u011fi ve g\u00fcvenli bir dizin yap\u0131s\u0131 olu\u015fturmak iyi bir uygulamad\u0131r.<\/p>\n<p>\u00d6nerilen dizin yap\u0131s\u0131:<\/p>\n<pre><code class=\"language-\">\/etc\/nginx\/ssl\/\n\u251c\u2500\u2500 domain1.com\/\n\u2502   \u251c\u2500\u2500 domain1.com.crt\n\u2502   \u251c\u2500\u2500 domain1.com.key\n\u2502   \u2514\u2500\u2500 domain1.com_chain.crt (veya fullchain.crt)\n\u2514\u2500\u2500 domain2.com\/\n    \u251c\u2500\u2500 domain2.com.crt\n    \u251c\u2500\u2500 domain2.com.key\n    \u2514\u2500\u2500 domain2.com_chain.crt (veya fullchain.crt)<\/code><\/pre>\n<p>Sertifika dosyalar\u0131n\u0131 sunucuya kopyalamak i\u00e7in <code>scp<\/code> veya <code>sftp<\/code> gibi g\u00fcvenli dosya transfer protokollerini kullanabilirsiniz:<\/p>\n<pre><code class=\"language-bash\"># \u00d6rnek: Sertifikalar\u0131 yerel bilgisayar\u0131n\u0131zdan sunucuya kopyalama\n<h2>scp \/path\/to\/local\/domain1.com.crt user@your_server_ip:\/tmp\/<\/h2>\n<h2>scp \/path\/to\/local\/domain1.com.key user@your_server_ip:\/tmp\/<\/h2>\n<h2>scp \/path\/to\/local\/domain1.com_chain.crt user@your_server_ip:\/tmp\/<\/code><\/pre>\n<\/h2>\n<p>Sunucuya kopyalad\u0131ktan sonra, bunlar\u0131 uygun dizinlere ta\u015f\u0131y\u0131n ve izinlerini ayarlay\u0131n:<\/p>\n<pre><code class=\"language-bash\"># domain1.com i\u00e7in dizin olu\u015fturma ve dosyalar\u0131 ta\u015f\u0131ma\nsudo mkdir -p \/etc\/nginx\/ssl\/domain1.com\nsudo mv \/tmp\/domain1.com.crt \/etc\/nginx\/ssl\/domain1.com\/\nsudo mv \/tmp\/domain1.com.key \/etc\/nginx\/ssl\/domain1.com\/\nsudo mv \/tmp\/domain1.com_chain.crt \/etc\/nginx\/ssl\/domain1.com\/\n\n<h2>domain2.com i\u00e7in dizin olu\u015fturma ve dosyalar\u0131 ta\u015f\u0131ma<\/h2>\nsudo mkdir -p \/etc\/nginx\/ssl\/domain2.com\nsudo mv \/tmp\/domain2.com.crt \/etc\/nginx\/ssl\/domain2.com\/\nsudo mv \/tmp\/domain2.com.key \/etc\/nginx\/ssl\/domain2.com\/\nsudo mv \/tmp\/domain2.com_chain.crt \/etc\/nginx\/ssl\/domain2.com\/<\/code><\/pre>\n<p><strong>Dosya \u0130zinleri:<\/strong> \u00d6zel anahtar dosyas\u0131 (<code>.key<\/code>) kesinlikle sadece <code>root<\/code> kullan\u0131c\u0131s\u0131 taraf\u0131ndan okunabilir olmal\u0131d\u0131r. Di\u011fer kullan\u0131c\u0131lar\u0131n bu dosyaya eri\u015fimi olmamal\u0131d\u0131r. Genel sertifika ve zincir dosyalar\u0131 ise Nginx kullan\u0131c\u0131s\u0131 taraf\u0131ndan okunabilir olmal\u0131d\u0131r.<\/p>\n<pre><code class=\"language-bash\"># \u00d6zel anahtar dosyalar\u0131na sadece root kullan\u0131c\u0131s\u0131n\u0131n okuma izni ver\nsudo chmod 600 \/etc\/nginx\/ssl\/domain1.com\/*.key\nsudo chmod 600 \/etc\/nginx\/ssl\/domain2.com\/*.key\n\n<h2>Sertifika dosyalar\u0131na Nginx'in okuma izni ver (genellikle 644 yeterlidir)<\/h2>\nsudo chmod 644 \/etc\/nginx\/ssl\/domain1.com\/*.crt\nsudo chmod 644 \/etc\/nginx\/ssl\/domain2.com\/*.crt<\/code><\/pre>\n<p>Bu ad\u0131mlar, sertifika dosyalar\u0131n\u0131z\u0131n sunucunuzda g\u00fcvenli ve d\u00fczenli bir \u015fekilde saklanmas\u0131n\u0131 sa\u011flar.<\/p>\n<h2>Nginx Sanal Host Yap\u0131land\u0131rmas\u0131 (Server Blocks)<\/h2>\n<p>Nginx&#8217;te her bir web sitesi veya alan ad\u0131, bir &#8220;server block&#8221; (sanal host) ile yap\u0131land\u0131r\u0131l\u0131r. Tek bir IP adresinde birden fazla SSL sertifikas\u0131 kullanabilmek i\u00e7in SNI (Server Name Indication) mekanizmas\u0131 kritik \u00f6neme sahiptir.<\/p>\n<h3>SNI (Server Name Indication) Mekanizmas\u0131<\/h3>\n<p>SNI, TLS protokol\u00fcn\u00fcn bir uzant\u0131s\u0131d\u0131r ve istemcinin (taray\u0131c\u0131n\u0131n), TLS el s\u0131k\u0131\u015fmas\u0131 s\u0131ras\u0131nda hangi alan ad\u0131na eri\u015fmek istedi\u011fini sunucuya bildirmesini sa\u011flar. Sunucu, bu bilgiye dayanarak do\u011fru SSL sertifikas\u0131n\u0131 se\u00e7er ve istemciye g\u00f6nderir. B\u00f6ylece, ayn\u0131 IP adresini ve portu (443) kullanan birden fazla web sitesi, her biri kendi SSL sertifikas\u0131na sahip olarak hizmet verebilir. Ubuntu 12.04&#8217;teki Nginx ve OpenSSL s\u00fcr\u00fcmleri genellikle SNI&#8217;yi destekler.<\/p>\n<h3>Domain 1 \u0130\u00e7in Yap\u0131land\u0131rma<\/h3>\n<p>\u0130lk alan ad\u0131n\u0131z (<code>domain1.com<\/code>) i\u00e7in bir Nginx sanal host yap\u0131land\u0131rma dosyas\u0131 olu\u015ftural\u0131m.<\/p>\n<pre><code class=\"language-bash\">sudo nano \/etc\/nginx\/sites-available\/domain1.com<\/code><\/pre>\n<p>Dosyan\u0131n i\u00e7eri\u011fi a\u015fa\u011f\u0131daki gibi olmal\u0131d\u0131r:<\/p>\n<pre><code class=\"language-nginx\"># HTTP'den HTTPS'e y\u00f6nlendirme\nserver {\n    listen 80;\n    server_name domain1.com www.domain1.com;\n    return 301 https:\/\/$host$request_uri;\n}\n\n<h2>HTTPS yap\u0131land\u0131rmas\u0131<\/h2>\nserver {\n    listen 443 ssl;\n    server_name domain1.com www.domain1.com;\n\n    # SSL sertifika dosyalar\u0131\n    ssl_certificate \/etc\/nginx\/ssl\/domain1.com\/domain1.com_fullchain.crt; # Veya domain1.com.crt; ve ssl_trusted_certificate domain1.com_chain.crt;\n    ssl_certificate_key \/etc\/nginx\/ssl\/domain1.com\/domain1.com.key;\n\n    # SSL ayarlar\u0131 (g\u00fcvenlik i\u00e7in \u00f6nerilen ayarlar)\n    ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Ubuntu 12.04'teki OpenSSL s\u00fcr\u00fcm\u00fcne g\u00f6re ayarla. TLSv1.3 desteklenmez.\n    ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA384';\n    ssl_prefer_server_ciphers on;\n    ssl_session_cache shared:SSL:10m;\n    ssl_session_timeout 10m;\n    ssl_stapling on; # OCSP Stapling'i etkinle\u015ftirir\n    ssl_stapling_verify on;\n    resolver 8.8.8.8 8.8.4.4 valid=300s; # DNS \u00e7\u00f6z\u00fcmleyici (Google DNS)\n    resolver_timeout 5s;\n\n    # HSTS (HTTP Strict Transport Security) - \u0130ste\u011fe ba\u011fl\u0131, ancak g\u00fcvenlik i\u00e7in \u00f6nerilir\n    add_header Strict-Transport-Security \"max-age=31536000; includeSubDomains; preload\" always;\n\n    # Web sitenizin k\u00f6k dizini\n    root \/var\/www\/domain1.com;\n    index index.html index.htm index.nginx-debian.html;\n\n    location \/ {\n        try_files $uri $uri\/ =404;\n    }\n\n    # Hata sayfalar\u0131\n    error_page 404 \/404.html;\n    location = \/404.html {\n        internal;\n    }\n\n    error_page 500 502 503 504 \/50x.html;\n    location = \/50x.html {\n        internal;\n    }\n}<\/code><\/pre>\n<p><strong>\u00d6nemli Not:<\/strong> E\u011fer <code>fullchain.crt<\/code> dosyan\u0131z yoksa ve sertifika ile ara sertifika ayr\u0131 dosyalardaysa:<br \/>\n<code>ssl_certificate \/etc\/nginx\/ssl\/domain1.com\/domain1.com.crt;<\/code><br \/>\n<code>ssl_certificate_key \/etc\/nginx\/ssl\/domain1.com\/domain1.com.key;<\/code><br \/>\n<code>ssl_trusted_certificate \/etc\/nginx\/ssl\/domain1.com\/domain1.com_chain.crt;<\/code> (Bu direktif, ara sertifikalar\u0131 belirtmek i\u00e7in kullan\u0131l\u0131r, \u00f6zellikle OCSP stapling ile birlikte.)<\/p>\n<h3>Domain 2 \u0130\u00e7in Yap\u0131land\u0131rma<\/h3>\n<p>\u0130kinci alan ad\u0131n\u0131z (<code>domain2.com<\/code>) i\u00e7in de benzer \u015fekilde bir yap\u0131land\u0131rma dosyas\u0131 olu\u015fturun:<\/p>\n<pre><code class=\"language-bash\">sudo nano \/etc\/nginx\/sites-available\/domain2.com<\/code><\/pre>\n<p>Dosyan\u0131n i\u00e7eri\u011fi, <code>domain1.com<\/code> yap\u0131land\u0131rmas\u0131na benzer olacak, ancak <code>server_name<\/code>, <code>root<\/code> dizini ve <code>ssl_certificate<\/code> ile <code>ssl_certificate_key<\/code> yollar\u0131 <code>domain2.com<\/code>&#8216;a \u00f6zg\u00fc olacakt\u0131r:<\/p>\n<pre><code class=\"language-nginx\"># HTTP'den HTTPS'e y\u00f6nlendirme\nserver {\n    listen 80;\n    server_name domain2.com www.domain2.com;\n    return 301 https:\/\/$host$request_uri;\n}\n\n<h2>HTTPS yap\u0131land\u0131rmas\u0131<\/h2>\nserver {\n    listen 443 ssl;\n    server_name domain2.com www.domain2.com;\n\n    # SSL sertifika dosyalar\u0131\n    ssl_certificate \/etc\/nginx\/ssl\/domain2.com\/domain2.com_fullchain.crt; # Veya domain2.com.crt; ve ssl_trusted_certificate domain2.com_chain.crt;\n    ssl_certificate_key \/etc\/nginx\/ssl\/domain2.com\/domain2.com.key;\n\n    # SSL ayarlar\u0131 (g\u00fcvenlik i\u00e7in \u00f6nerilen ayarlar) - Domain 1 ile ayn\u0131 olabilir\n    ssl_protocols TLSv1 TLSv1.1 TLSv1.2;\n    ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA384';\n    ssl_prefer_server_ciphers on;\n    ssl_session_cache shared:SSL:10m;\n    ssl_session_timeout 10m;\n    ssl_stapling on;\n    ssl_stapling_verify on;\n    resolver 8.8.8.8 8.8.4.4 valid=300s;\n    resolver_timeout 5s;\n\n    # HSTS\n    add_header Strict-Transport-Security \"max-age=31536000; includeSubDomains; preload\" always;\n\n    # Web sitenizin k\u00f6k dizini\n    root \/var\/www\/domain2.com;\n    index index.html index.htm index.nginx-debian.html;\n\n    location \/ {\n        try_files $uri $uri\/ =404;\n    }\n\n    # Hata sayfalar\u0131\n    error_page 404 \/404.html;\n    location = \/404.html {\n        internal;\n    }\n\n    error_page 500 502 503 504 \/50x.html;\n    location = \/50x.html {\n        internal;\n    }\n}<\/code><\/pre>\n<p>Her bir alan ad\u0131n\u0131z i\u00e7in <code>\/var\/www\/<\/code> dizini alt\u0131nda ilgili k\u00f6k dizinleri olu\u015fturmay\u0131 unutmay\u0131n. \u00d6rne\u011fin:<\/p>\n<pre><code class=\"language-bash\">sudo mkdir -p \/var\/www\/domain1.com\nsudo mkdir -p \/var\/www\/domain2.com\n<h2>Test i\u00e7in basit bir index.html dosyas\u0131 olu\u015fturabilirsiniz<\/h2>\necho \"Hello from Domain 1!\" | sudo tee \/var\/www\/domain1.com\/index.html\necho \"Hello from Domain 2!\" | sudo tee \/var\/www\/domain2.com\/index.html<\/code><\/pre>\n<h3>Varsay\u0131lan SSL Hostu (Opsiyonel ama \u00d6nemli)<\/h3>\n<p>SNI deste\u011fi olmayan \u00e7ok eski taray\u0131c\u0131lar veya istemciler, HTTPS \u00fczerinden sunucunuza eri\u015fmeye \u00e7al\u0131\u015ft\u0131\u011f\u0131nda, sunucu hangi sertifikay\u0131 g\u00f6nderece\u011fini bilemez. Bu durumda Nginx, <code>listen 443 ssl default_server;<\/code> y\u00f6nergesine sahip ilk <code>server<\/code> blo\u011funu kullan\u0131r. Bu blo\u011fu genellikle birincil alan ad\u0131n\u0131z i\u00e7in kullanabilir veya SNI deste\u011fi olmayan istemciler i\u00e7in \u00f6zel bir hata sayfas\u0131 sunan bir varsay\u0131lan blok tan\u0131mlayabilirsiniz.<\/p>\n<p>\u00d6rne\u011fin, <code>domain1.com<\/code> yap\u0131land\u0131rman\u0131zda <code>listen 443 ssl default_server;<\/code> kullan\u0131rsan\u0131z, SNI deste\u011fi olmayan istemciler <code>domain1.com<\/code>&#8216;un sertifikas\u0131n\u0131 alacakt\u0131r. Bu, genellikle kabul edilebilir bir davran\u0131\u015ft\u0131r.<\/p>\n<h2>Nginx Yap\u0131land\u0131rmas\u0131n\u0131 Etkinle\u015ftirme ve Test Etme<\/h2>\n<p>Yap\u0131land\u0131rma dosyalar\u0131n\u0131 olu\u015fturduktan sonra, Nginx&#8217;in bunlar\u0131 okuyup etkinle\u015ftirmesi i\u00e7in baz\u0131 ad\u0131mlar gereklidir.<\/p>\n<h3>Sembolik Ba\u011flant\u0131lar Olu\u015fturma<\/h3>\n<p>Olu\u015fturdu\u011funuz yap\u0131land\u0131rma dosyalar\u0131n\u0131 <code>\/etc\/nginx\/sites-available\/<\/code> dizininden <code>\/etc\/nginx\/sites-enabled\/<\/code> dizinine sembolik ba\u011flant\u0131lar olu\u015fturarak etkinle\u015ftirin:<\/p>\n<pre><code class=\"language-bash\">sudo ln -s \/etc\/nginx\/sites-available\/domain1.com \/etc\/nginx\/sites-enabled\/\nsudo ln -s \/etc\/nginx\/sites-available\/domain2.com \/etc\/nginx\/sites-enabled\/<\/code><\/pre>\n<p>Varsay\u0131lan Nginx yap\u0131land\u0131rma dosyas\u0131 olan <code>\/etc\/nginx\/sites-enabled\/default<\/code> dosyas\u0131n\u0131 devre d\u0131\u015f\u0131 b\u0131rakmak isteyebilirsiniz, aksi takdirde \u00e7ak\u0131\u015fmalara neden olabilir:<\/p>\n<pre><code class=\"language-bash\">sudo rm \/etc\/nginx\/sites-enabled\/default<\/code><\/pre>\n<h3>Nginx Yap\u0131land\u0131rma S\u00f6zdizimini Kontrol Etme<\/h3>\n<p>Nginx&#8217;i yeniden ba\u015flatmadan \u00f6nce, yap\u0131land\u0131rma dosyalar\u0131n\u0131zda herhangi bir s\u00f6zdizimi hatas\u0131 olup olmad\u0131\u011f\u0131n\u0131 kontrol etmek \u00e7ok \u00f6nemlidir. Bu, olas\u0131 servis kesintilerini \u00f6nler:<\/p>\n<pre><code class=\"language-bash\">sudo nginx -t<\/code><\/pre>\n<p>E\u011fer her \u015fey yolundaysa, a\u015fa\u011f\u0131daki gibi bir \u00e7\u0131kt\u0131 almal\u0131s\u0131n\u0131z:<\/p>\n<pre><code class=\"language-\">nginx: the configuration file \/etc\/nginx\/nginx.conf syntax is ok\nnginx: configuration file \/etc\/nginx\/nginx.conf test is successful<\/code><\/pre>\n<p>Herhangi bir hata mesaj\u0131 al\u0131rsan\u0131z, belirtilen sat\u0131rlardaki hatalar\u0131 d\u00fczeltin ve tekrar kontrol edin.<\/p>\n<h3>Nginx&#8217;i Yeniden Ba\u015flatma<\/h3>\n<p>Yap\u0131land\u0131rma testi ba\u015far\u0131l\u0131 olduktan sonra, Nginx servisini yeniden ba\u015flatarak yeni yap\u0131land\u0131rmalar\u0131n etkinle\u015fmesini sa\u011flay\u0131n:<\/p>\n<pre><code class=\"language-bash\">sudo service nginx restart<\/code><\/pre>\n<h3>Test Etme<\/h3>\n<p>Kurulumun ba\u015far\u0131l\u0131 olup olmad\u0131\u011f\u0131n\u0131 kontrol etmek i\u00e7in a\u015fa\u011f\u0131daki ad\u0131mlar\u0131 izleyin:<\/p>\n<p>1.  <strong>Taray\u0131c\u0131 Testi:<\/strong><br \/>\n    *   Taray\u0131c\u0131n\u0131z\u0131 a\u00e7\u0131n ve <code>https:\/\/www.domain1.com<\/code> adresine gidin.<br \/>\n    *   Taray\u0131c\u0131n\u0131z\u0131n adres \u00e7ubu\u011funda kilit simgesini kontrol edin. Kilit simgesine t\u0131klayarak sertifika bilgilerini (kimin i\u00e7in verildi\u011fi, ge\u00e7erlilik s\u00fcresi vb.) kontrol edin. <code>domain1.com<\/code> i\u00e7in do\u011fru sertifikay\u0131 g\u00f6rmelisiniz.<br \/>\n    *   Ayn\u0131 i\u015flemi <code>https:\/\/www.domain2.com<\/code> i\u00e7in de tekrarlay\u0131n. <code>domain2.com<\/code> i\u00e7in do\u011fru sertifikay\u0131 g\u00f6rmelisiniz.<br \/>\n    *   HTTP&#8217;den HTTPS&#8217;e y\u00f6nlendirmelerin do\u011fru \u00e7al\u0131\u015f\u0131p \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131 kontrol etmek i\u00e7in <code>http:\/\/www.domain1.com<\/code> ve <code>http:\/\/www.domain2.com<\/code> adreslerine de eri\u015fmeyi deneyin. Otomatik olarak HTTPS&#8217;e y\u00f6nlendirilmelisiniz.<\/p>\n<p>2.  <strong>SSL Labs Testi:<\/strong><br \/>\n    *   SSL Labs&#8217;\u0131n [SSL Server Test](https:\/\/www.ssllabs.com\/ssltest\/) arac\u0131n\u0131 kullanarak her bir alan ad\u0131n\u0131z i\u00e7in sertifika yap\u0131land\u0131rman\u0131z\u0131n ve g\u00fcvenlik ayarlar\u0131n\u0131z\u0131n ne kadar g\u00fc\u00e7l\u00fc oldu\u011funu kontrol edin. Bu ara\u00e7, potansiyel zay\u0131fl\u0131klar\u0131 ve iyile\u015ftirme \u00f6nerilerini g\u00f6sterir.<\/p>\n<h2>S\u0131k Kar\u015f\u0131la\u015f\u0131lan Sorunlar ve \u00c7\u00f6z\u00fcmleri<\/h2>\n<p>Kurulum s\u00fcrecinde kar\u015f\u0131la\u015fabilece\u011finiz baz\u0131 yayg\u0131n sorunlar ve \u00e7\u00f6z\u00fcmleri:<\/p>\n<p>*   <strong>Sertifika Yolu Hatalar\u0131:<\/strong> Nginx loglar\u0131nda (genellikle <code>\/var\/log\/nginx\/error.log<\/code>) &#8220;no such file or directory&#8221; veya &#8220;permission denied&#8221; gibi hatalar g\u00f6r\u00fcyorsan\u0131z, <code>ssl_certificate<\/code> ve <code>ssl_certificate_key<\/code> y\u00f6nergelerindeki dosya yollar\u0131n\u0131n do\u011fru oldu\u011fundan ve Nginx&#8217;in bu dosyalara eri\u015fim izinlerinin bulundu\u011fundan emin olun.<br \/>\n*   <strong>\u0130zin Hatalar\u0131:<\/strong> \u00d6zel anahtar dosyalar\u0131n\u0131n (<code>.key<\/code>) izinleri genellikle <code>600<\/code> olmal\u0131d\u0131r. Di\u011fer sertifika dosyalar\u0131 i\u00e7in <code>644<\/code> yeterlidir. Nginx kullan\u0131c\u0131s\u0131n\u0131n bu dosyalara okuma izni olmal\u0131d\u0131r.<br \/>\n*   <strong>SNI Deste\u011fi Olmayan \u0130stemciler:<\/strong> \u00c7ok eski taray\u0131c\u0131lar veya i\u015fletim sistemleri SNI&#8217;yi desteklemez. Bu durumda, sunucu varsay\u0131lan SSL hostunun sertifikas\u0131n\u0131 g\u00f6nderir. Bu, genellikle <code>listen 443 ssl default_server;<\/code> y\u00f6nergesini i\u00e7eren ilk <code>server<\/code> blo\u011funun sertifikas\u0131d\u0131r. Bu durum, bu istemciler i\u00e7in bir sertifika uyar\u0131s\u0131na neden olabilir. Bu t\u00fcr istemcilerin say\u0131s\u0131 g\u00fcn\u00fcm\u00fczde \u00e7ok azd\u0131r.<br \/>\n*   <strong>Firewall Engellemeleri:<\/strong> E\u011fer web sitelerinize taray\u0131c\u0131dan eri\u015femiyorsan\u0131z, sunucunuzdaki g\u00fcvenlik duvar\u0131n\u0131n (UFW veya ba\u015fka bir firewall) 80 (HTTP) ve 443 (HTTPS) portlar\u0131n\u0131 engellemedi\u011finden emin olun. <code>sudo ufw status<\/code> komutuyla kontrol edebilirsiniz.<br \/>\n*   <strong>DNS Hatalar\u0131:<\/strong> Alan adlar\u0131n\u0131z\u0131n (\u00f6rn. <code>domain1.com<\/code>, <code>www.domain1.com<\/code>) DNS A kay\u0131tlar\u0131n\u0131n sunucunuzun do\u011fru IP adresine i\u015faret etti\u011finden emin olun. DNS de\u011fi\u015fikliklerinin yay\u0131lmas\u0131 biraz zaman alabilir.<br \/>\n*   <strong>Nginx Syntax Hatalar\u0131:<\/strong> <code>sudo nginx -t<\/code> komutunun \u00e7\u0131kt\u0131s\u0131n\u0131 dikkatlice inceleyin. Genellikle hatan\u0131n hangi dosyada ve hangi sat\u0131rda oldu\u011funu belirtir.<br \/>\n*   <strong>Sertifika S\u00fcreleri:<\/strong> Sertifikalar\u0131n belirli bir ge\u00e7erlilik s\u00fcresi vard\u0131r. \u00d6zellikle Let&#8217;s Encrypt sertifikalar\u0131 90 g\u00fcn ge\u00e7erlidir. Sertifikalar\u0131n\u0131z\u0131n s\u00fcresi dolmadan \u00f6nce yenilendi\u011finden emin olun. Otomatik yenileme ara\u00e7lar\u0131 (Certbot gibi) kullanmak bu s\u00fcreci kolayla\u015ft\u0131r\u0131r.<\/p>\n<h2>G\u00fcvenlik \u0130pu\u00e7lar\u0131<\/h2>\n<p>Nginx ve SSL yap\u0131land\u0131rman\u0131z\u0131 daha g\u00fcvenli hale getirmek i\u00e7in baz\u0131 ek ipu\u00e7lar\u0131:<\/p>\n<p>*   <strong>G\u00fc\u00e7l\u00fc \u015eifreleme Algoritmalar\u0131 Kullanma:<\/strong> <code>ssl_protocols<\/code> ve <code>ssl_ciphers<\/code> y\u00f6nergelerini kullanarak zay\u0131f \u015fifreleme algoritmalar\u0131n\u0131 devre d\u0131\u015f\u0131 b\u0131rak\u0131n ve yaln\u0131zca g\u00fc\u00e7l\u00fc olanlar\u0131 kullan\u0131n. Yukar\u0131daki \u00f6rnek yap\u0131land\u0131rmada modern ve g\u00fcvenli bir \u015fifreleme listesi bulunmaktad\u0131r. Ancak Ubuntu 12.04&#8217;teki OpenSSL s\u00fcr\u00fcm\u00fcn\u00fcn TLSv1.3&#8217;\u00fc desteklemedi\u011fini unutmay\u0131n.<br \/>\n*   <strong>HSTS (HTTP Strict Transport Security):<\/strong> HSTS, taray\u0131c\u0131lara web sitenize her zaman HTTPS \u00fczerinden eri\u015fmeleri gerekti\u011fini bildirir. Bu, bir kullan\u0131c\u0131n\u0131n yanl\u0131\u015fl\u0131kla HTTP \u00fczerinden eri\u015fmeye \u00e7al\u0131\u015fmas\u0131n\u0131 veya bir araya girme sald\u0131r\u0131s\u0131yla HTTP&#8217;ye d\u00fc\u015f\u00fcr\u00fclmesini engeller. Yukar\u0131daki \u00f6rnek yap\u0131land\u0131rmada HSTS ba\u015fl\u0131\u011f\u0131 eklenmi\u015ftir.<br \/>\n*   <strong>OCSP Stapling:<\/strong> OCSP Stapling, sunucunun sertifika iptal durumu bilgisini do\u011frudan CA&#8217;dan al\u0131p istemciye TLS el s\u0131k\u0131\u015fmas\u0131 s\u0131ras\u0131nda g\u00f6ndermesini sa\u011flar. Bu, istemcinin CA&#8217;ya ayr\u0131 bir istek g\u00f6ndermesini engelleyerek hem performans\u0131 art\u0131r\u0131r hem de gizlili\u011fi korur. Yukar\u0131daki \u00f6rnek yap\u0131land\u0131rmada etkinle\u015ftirilmi\u015ftir.<br \/>\n*   <strong>Sertifika Dosyalar\u0131n\u0131n G\u00fcvenli\u011fi:<\/strong> \u00d6zel anahtar dosyalar\u0131n\u0131z\u0131n (<code>.key<\/code>) sunucunuzda en g\u00fcvenli \u015fekilde sakland\u0131\u011f\u0131ndan ve sadece gerekli kullan\u0131c\u0131lar\u0131n eri\u015febildi\u011finden emin olun (<code>chmod 600<\/code>).<br \/>\n*   <strong>Nginx S\u00fcr\u00fcm\u00fcn\u00fc G\u00fcncel Tutma:<\/strong> Ubuntu 12.04&#8217;te bu m\u00fcmk\u00fcn olmasa da, genel bir g\u00fcvenlik \u00f6nerisi olarak, Nginx ve OpenSSL gibi yaz\u0131l\u0131mlar\u0131n g\u00fcncel tutulmas\u0131, bilinen g\u00fcvenlik a\u00e7\u0131klar\u0131ndan korunmak i\u00e7in \u00f6nemlidir. Eski sistemlerde g\u00fcvenlik yamalar\u0131n\u0131n eksikli\u011fi risk olu\u015fturabilir.<\/p>\n<h2>Sonu\u00e7<\/h2>\n<p>Bu makalede, Nginx ve Ubuntu 12.04 \u00fczerinde tek bir IP adresinde birden fazla SSL sertifikas\u0131n\u0131 SNI teknolojisi sayesinde nas\u0131l yap\u0131land\u0131raca\u011f\u0131m\u0131z\u0131 detayl\u0131 bir \u015fekilde inceledik. Modern web ortam\u0131nda HTTPS&#8217;in \u00f6nemi g\u00f6z \u00f6n\u00fcne al\u0131nd\u0131\u011f\u0131nda, bu yetenek, sunucu kaynaklar\u0131n\u0131 verimli kullanmak ve ayn\u0131 zamanda t\u00fcm web siteleri i\u00e7in y\u00fcksek g\u00fcvenlik standartlar\u0131n\u0131 sa\u011flamak a\u00e7\u0131s\u0131ndan kritik bir rol oynamaktad\u0131r.<\/p>\n<p>Her bir alan ad\u0131 i\u00e7in ayr\u0131 ayr\u0131 SSL sertifikalar\u0131n\u0131 edinme, bunlar\u0131 sunucuya g\u00fcvenli bir \u015fekilde kopyalama, Nginx sanal hostlar\u0131n\u0131 (server blocks) do\u011fru bir \u015fekilde yap\u0131land\u0131rma ve son olarak yap\u0131land\u0131rmay\u0131 test etme ad\u0131mlar\u0131n\u0131 titizlikle uygulayarak, web sitelerinizi g\u00fcvenli bir \u015fekilde HTTPS \u00fczerinden yay\u0131nlayabilirsiniz. Unutulmamal\u0131d\u0131r ki, g\u00fcvenli bir yap\u0131land\u0131rma sadece kurulumla bitmez; sertifikalar\u0131n d\u00fczenli olarak yenilenmesi, g\u00fcvenlik duvar\u0131 ayarlar\u0131n\u0131n do\u011fru olmas\u0131 ve sunucu yaz\u0131l\u0131mlar\u0131n\u0131n (m\u00fcmk\u00fcnse) g\u00fcncel tutulmas\u0131 da s\u00fcrekli bir g\u00fcvenlik i\u00e7in elzemdir. Bu rehberin, Nginx \u00fczerinde birden fazla SSL sertifikas\u0131 kurma s\u00fcrecini anlaman\u0131za ve ba\u015far\u0131l\u0131 bir \u015fekilde uygulaman\u0131za yard\u0131mc\u0131 olmas\u0131n\u0131 umuyoruz.<\/p>\n","protected":false},"excerpt":{"rendered":"Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu\nGiri\u015f\nG\u00fcn\u00fcm\u00fcz internet d\u00fcnyas\u0131nda g\u00fcvenlik, kulla","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1468],"tags":[],"class_list":{"0":"post-32071","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-ubuntu","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v20.5 (Yoast SEO v25.3.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu\" \/>\n<meta property=\"og:description\" content=\"Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu Giri\u015f G\u00fcn\u00fcm\u00fcz internet d\u00fcnyas\u0131nda g\u00fcvenlik, kulla\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-10-17T07:41:10+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"19 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu\",\"datePublished\":\"2025-10-17T07:41:10+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/\"},\"wordCount\":2830,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"Ubuntu\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/\",\"name\":\"Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-10-17T07:41:10+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/","og_locale":"tr_TR","og_type":"article","og_title":"Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu","og_description":"Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu Giri\u015f G\u00fcn\u00fcm\u00fcz internet d\u00fcnyas\u0131nda g\u00fcvenlik, kulla","og_url":"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-10-17T07:41:10+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"19 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu","datePublished":"2025-10-17T07:41:10+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/"},"wordCount":2830,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["Ubuntu"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/","url":"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/","name":"Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-10-17T07:41:10+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/nginx-ve-ubuntu-12-04-uzerinde-tek-bir-ip-adresinde-birden-fazla-ssl-sertifikasi-kurulumu\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Nginx ve Ubuntu 12.04 \u00dczerinde Tek Bir IP Adresinde Birden Fazla SSL Sertifikas\u0131 Kurulumu"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/32071","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=32071"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/32071\/revisions"}],"predecessor-version":[{"id":32072,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/32071\/revisions\/32072"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=32071"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=32071"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=32071"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}