{"id":219,"date":"2026-09-10T12:41:44","date_gmt":"2026-09-10T09:41:44","guid":{"rendered":"https:\/\/licensepow.com\/blog\/?p=219"},"modified":"2026-09-10T12:41:44","modified_gmt":"2026-09-10T09:41:44","slug":"pleskte-firewall","status":"publish","type":"post","link":"https:\/\/licensepow.com\/blog\/pleskte-firewall","title":{"rendered":"Plesk&#8217;te Firewall Nas\u0131l Yap\u0131land\u0131r\u0131l\u0131r? G\u00fcvenlik Rehberi"},"content":{"rendered":"<h1>Plesk&#8217;te Firewall Nas\u0131l Yap\u0131land\u0131r\u0131l\u0131r? Plesk G\u00fcvenlik Duvar\u0131 Rehberi<\/h1>\n<p><strong>Plesk&#8217;te Firewall yap\u0131land\u0131rmak<\/strong>, sunucumuzdaki a\u011f ba\u011flant\u0131lar\u0131n\u0131 kontrol etmek ve yaln\u0131zca gerekli servislerin eri\u015filebilir olmas\u0131n\u0131 sa\u011flamak i\u00e7in \u00f6nemli bir g\u00fcvenlik ad\u0131m\u0131d\u0131r. Web, SSH, FTP, mail ve veritaban\u0131 gibi servislerin kulland\u0131\u011f\u0131 portlar do\u011fru \u015fekilde y\u00f6netilmedi\u011finde hem ba\u011flant\u0131 sorunlar\u0131 hem de g\u00fcvenlik a\u00e7\u0131klar\u0131 ortaya \u00e7\u0131kabilir.<\/p>\n<p>Plesk for Linux \u00fczerinde Firewall extension kullanarak gelen ve giden ba\u011flant\u0131lar i\u00e7in kurallar olu\u015fturabilir, belirli portlar\u0131 a\u00e7\u0131p kapatabilir ve sunucuya \u00f6zel g\u00fcvenlik politikalar\u0131 uygulayabiliriz.<\/p>\n<p>Bu rehberde Plesk Firewall kurulumunu, port y\u00f6netimini, \u00f6zel firewall kural\u0131 olu\u015fturmay\u0131, SSH ve web servislerini korumay\u0131 ve firewall yap\u0131land\u0131r\u0131rken dikkat edilmesi gereken noktalar\u0131 anlat\u0131yoruz.<\/p>\n<h2>Plesk Firewall Nedir?<\/h2>\n<p>Plesk Firewall, Plesk sunucusuna gelen veya sunucudan \u00e7\u0131kan a\u011f ba\u011flant\u0131lar\u0131n\u0131 kurallarla kontrol etmemizi sa\u011flayan g\u00fcvenlik bile\u015fenidir.<\/p>\n<p>Plesk&#8217;in resmi dok\u00fcmantasyonuna g\u00f6re Firewall extension \u00fczerinden a\u011f ba\u011flant\u0131lar\u0131n\u0131 k\u0131s\u0131tlayabilir, firewall kurallar\u0131 olu\u015fturabilir ve mevcut yap\u0131land\u0131rmay\u0131 y\u00f6netebiliriz.<\/p>\n<p><a href=\"https:\/\/docs.plesk.com\/en-US\/obsidian\/administrator-guide\/plesk-administration\/plesk-for-linux-the-plesk-firewall.72046\/\" target=\"_blank\" rel=\"noopener\">Plesk Firewall resmi dok\u00fcmantasyonunu<\/a> inceleyebilirsiniz.<\/p>\n<h2>Plesk Firewall Nerede Bulunur?<\/h2>\n<p>Firewall extension kuruluysa Plesk panelinden g\u00fcvenlik ayarlar\u0131na ula\u015fabiliriz.<\/p>\n<pre><code>Tools &amp; Settings\r\n\u2192 Security\r\n\u2192 Firewall<\/code><\/pre>\n<p>Buradan mevcut firewall kurallar\u0131n\u0131 inceleyebilir ve yeni kurallar ekleyebiliriz.<\/p>\n<h2>Plesk&#8217;te Firewall Extension Nas\u0131l Kurulur?<\/h2>\n<p>Plesk sunucusunda Firewall b\u00f6l\u00fcm\u00fc g\u00f6r\u00fcnm\u00fcyorsa Firewall extension kurulu olmayabilir.<\/p>\n<p>Plesk&#8217;in Extensions Catalog sistemi \u00fczerinden eklentileri do\u011frudan panelden y\u00f6netebiliriz.<\/p>\n<ol>\n<li>Plesk paneline giri\u015f yap\u0131yoruz.<\/li>\n<li><strong>Extensions<\/strong> b\u00f6l\u00fcm\u00fcn\u00fc a\u00e7\u0131yoruz.<\/li>\n<li><strong>Firewall<\/strong> eklentisini ar\u0131yoruz.<\/li>\n<li>Eklentiyi kuruyoruz.<\/li>\n<li>Kurulum tamamland\u0131ktan sonra Firewall b\u00f6l\u00fcm\u00fcn\u00fc a\u00e7\u0131yoruz.<\/li>\n<\/ol>\n<p>Plesk Extensions Catalog hakk\u0131nda <a href=\"https:\/\/docs.plesk.com\/en-US\/obsidian\/administrator-guide\/plesk-extensions\/extensions-catalog.78328\/\" target=\"_blank\" rel=\"noopener\">resmi dok\u00fcmantasyona<\/a> g\u00f6z atabilirsiniz.<\/p>\n<h2>Plesk Firewall ile Hangi Portlar Y\u00f6netilir?<\/h2>\n<p>Firewall yap\u0131land\u0131r\u0131rken sunucudaki servislerin hangi portlar\u0131 kulland\u0131\u011f\u0131n\u0131 bilmemiz gerekir.<\/p>\n<p>Plesk dok\u00fcmantasyonunda yayg\u0131n servisler i\u00e7in a\u015fa\u011f\u0131daki portlar listelenmektedir:<\/p>\n<table>\n<thead>\n<tr>\n<th>Servis<\/th>\n<th>Port<\/th>\n<th>Protokol<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>HTTP<\/td>\n<td>80<\/td>\n<td>TCP<\/td>\n<\/tr>\n<tr>\n<td>HTTPS<\/td>\n<td>443<\/td>\n<td>TCP<\/td>\n<\/tr>\n<tr>\n<td>Plesk Panel<\/td>\n<td>8443<\/td>\n<td>TCP<\/td>\n<\/tr>\n<tr>\n<td>SSH<\/td>\n<td>22<\/td>\n<td>TCP<\/td>\n<\/tr>\n<tr>\n<td>FTP<\/td>\n<td>20, 21<\/td>\n<td>TCP<\/td>\n<\/tr>\n<tr>\n<td>FTPS<\/td>\n<td>990<\/td>\n<td>TCP<\/td>\n<\/tr>\n<tr>\n<td>SMTP<\/td>\n<td>25, 465<\/td>\n<td>TCP<\/td>\n<\/tr>\n<tr>\n<td>IMAP<\/td>\n<td>143, 993<\/td>\n<td>TCP<\/td>\n<\/tr>\n<tr>\n<td>POP3<\/td>\n<td>110, 995<\/td>\n<td>TCP<\/td>\n<\/tr>\n<tr>\n<td>MySQL \/ MariaDB<\/td>\n<td>3306<\/td>\n<td>TCP<\/td>\n<\/tr>\n<tr>\n<td>DNS<\/td>\n<td>53<\/td>\n<td>TCP \/ UDP<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><a href=\"https:\/\/docs.plesk.com\/en-US\/obsidian\/advanced-administration-guide-win\/introduction-to-plesk\/ports-used-by-plesk.68753\/\" target=\"_blank\" rel=\"noopener\">Plesk taraf\u0131ndan kullan\u0131lan portlar\u0131n g\u00fcncel listesini<\/a> kontrol edebilirsiniz.<\/p>\n<h2>Plesk Firewall Kural\u0131 Nas\u0131l Eklenir?<\/h2>\n<p>Yeni bir portu veya servisi eri\u015fime a\u00e7mak i\u00e7in firewall kural\u0131 olu\u015fturabiliriz.<\/p>\n<ol>\n<li><strong>Tools &amp; Settings \u2192 Firewall<\/strong> b\u00f6l\u00fcm\u00fcn\u00fc a\u00e7\u0131yoruz.<\/li>\n<li>Firewall rules b\u00f6l\u00fcm\u00fcne giriyoruz.<\/li>\n<li><strong>Add Firewall Rule<\/strong> se\u00e7ene\u011fini kullan\u0131yoruz.<\/li>\n<li>Kural i\u00e7in bir isim belirliyoruz.<\/li>\n<li>Port numaras\u0131n\u0131 giriyoruz.<\/li>\n<li>TCP veya UDP protokol\u00fcn\u00fc se\u00e7iyoruz.<\/li>\n<li>Kural\u0131 kaydediyoruz.<\/li>\n<li>De\u011fi\u015fiklikleri uyguluyoruz.<\/li>\n<\/ol>\n<p>\u00d6rne\u011fin 8080 portundaki \u00f6zel bir uygulamaya eri\u015fim vermek istiyorsak:<\/p>\n<pre><code>Name: Custom Application\r\nPort: 8080\r\nProtocol: TCP\r\nAction: Allow<\/code><\/pre>\n<p>\u015feklinde bir kural olu\u015fturabiliriz.<\/p>\n<h2>Plesk&#8217;te SSH Portunu A\u00e7ma<\/h2>\n<p>Sunucuya SSH \u00fczerinden ba\u011flan\u0131yorsak kullan\u0131lan SSH portunun firewall taraf\u0131ndan engellenmemesi gerekir.<\/p>\n<p>Standart SSH portu:<\/p>\n<pre><code>22\/TCP<\/code><\/pre>\n<p>olabilir.<\/p>\n<p>SSH farkl\u0131 bir port \u00fczerinden yap\u0131land\u0131r\u0131lm\u0131\u015fsa firewall \u00fczerinde de ger\u00e7ek port numaras\u0131n\u0131 kullanmam\u0131z gerekir.<\/p>\n<p>\u00d6rne\u011fin:<\/p>\n<pre><code>2222\/TCP<\/code><\/pre>\n<p>kullan\u0131l\u0131yorsa bu portun eri\u015filebilir olmas\u0131 gerekir.<\/p>\n<p>Firewall \u00fczerinde SSH ba\u011flant\u0131s\u0131n\u0131 kapatmadan \u00f6nce aktif y\u00f6netici ba\u011flant\u0131m\u0131z\u0131n devam etti\u011finden emin olman\u0131z\u0131 \u00f6neriyoruz.<\/p>\n<h2>Plesk&#8217;te HTTP ve HTTPS Portlar\u0131n\u0131 A\u00e7ma<\/h2>\n<p>Web sitelerimizin internet \u00fczerinden eri\u015filebilir olmas\u0131 i\u00e7in en az\u0131ndan HTTP veya HTTPS trafi\u011finin uygun \u015fekilde y\u00f6nlendirilmi\u015f olmas\u0131 gerekir.<\/p>\n<pre><code>80\/TCP\r\n443\/TCP<\/code><\/pre>\n<p>Web sitelerinde m\u00fcmk\u00fcn oldu\u011funca HTTPS kullan\u0131lmas\u0131 ve HTTP&#8217;den HTTPS&#8217;e y\u00f6nlendirme yap\u0131lmas\u0131 daha g\u00fcvenli bir yap\u0131 olu\u015fturabilir.<\/p>\n<h2>Plesk Panel Portu 8443 Nedir?<\/h2>\n<p>Plesk y\u00f6netim paneline HTTPS \u00fczerinden eri\u015fim i\u00e7in standart olarak:<\/p>\n<pre><code>8443\/TCP<\/code><\/pre>\n<p>portu kullan\u0131l\u0131r.<\/p>\n<p>\u00d6rne\u011fin:<\/p>\n<pre><code>https:\/\/server.example.com:8443<\/code><\/pre>\n<p>adresinden Plesk paneline eri\u015fim sa\u011flanabilir.<\/p>\n<p>Panel eri\u015fimini yaln\u0131zca belirli IP adreslerinden kabul edecek \u015fekilde k\u0131s\u0131tlamak da g\u00fcvenlik a\u00e7\u0131s\u0131ndan de\u011ferlendirilebilir.<\/p>\n<h2>Plesk Firewall ile Sadece Belirli IP Adresine \u0130zin Verme<\/h2>\n<p>Baz\u0131 servisleri t\u00fcm internete a\u00e7mak yerine yaln\u0131zca belirli IP adreslerinden eri\u015filebilir hale getirmek daha kontroll\u00fc olabilir.<\/p>\n<p>\u00d6rne\u011fin SSH i\u00e7in:<\/p>\n<pre><code>Source IP:\r\n203.0.113.10\r\n\r\nDestination Port:\r\n22\r\n\r\nProtocol:\r\nTCP\r\n\r\nAction:\r\nAllow<\/code><\/pre>\n<p>gibi bir kural uygulanabilir.<\/p>\n<p>Bu yap\u0131 \u00f6zellikle y\u00f6netim servislerini yaln\u0131zca g\u00fcvenilir ofis veya VPN IP adreslerinden eri\u015filebilir tutmak istedi\u011fimiz durumlarda kullan\u0131\u015fl\u0131d\u0131r.<\/p>\n<h2>Plesk Firewall&#8217;da Port Kapatma<\/h2>\n<p>Kullan\u0131lmayan bir servis d\u0131\u015far\u0131dan eri\u015filebilir durumdaysa ilgili portu firewall \u00fczerinden kapatmay\u0131 de\u011ferlendirebiliriz.<\/p>\n<p>\u00d6rne\u011fin sunucuda FTP kullan\u0131lm\u0131yorsa FTP servisinin ger\u00e7ekten kapal\u0131 olup olmad\u0131\u011f\u0131n\u0131 kontrol etmeli ve ard\u0131ndan ilgili portlar\u0131n d\u0131\u015f eri\u015fimini s\u0131n\u0131rland\u0131rmal\u0131y\u0131z.<\/p>\n<p>Ancak yaln\u0131zca firewall kural\u0131 eklemek yerine art\u0131k kullan\u0131lmayan servisi tamamen devre d\u0131\u015f\u0131 b\u0131rakmak daha do\u011fru bir g\u00fcvenlik yakla\u015f\u0131m\u0131 olabilir.<\/p>\n<h2>Plesk Firewall ile MySQL Portu A\u00e7\u0131lmal\u0131 m\u0131?<\/h2>\n<p>MySQL veya MariaDB&#8217;nin standart portu:<\/p>\n<pre><code>3306\/TCP<\/code><\/pre>\n<p>olsa da bu portu public internet&#8217;e a\u00e7mak \u00e7o\u011fu hosting senaryosunda gerekli de\u011fildir.<\/p>\n<p>Web uygulamas\u0131 ve veritaban\u0131 ayn\u0131 sunucuda bulunuyorsa genellikle:<\/p>\n<pre><code>Application\r\n    \u2193\r\n127.0.0.1:3306\r\n    \u2193\r\nMySQL \/ MariaDB<\/code><\/pre>\n<p>\u015feklinde yerel ba\u011flant\u0131 yeterlidir.<\/p>\n<p>Uzak veritaban\u0131 eri\u015fimi gerekiyorsa yaln\u0131zca g\u00fcvenilir kaynak IP adreslerine izin veren k\u0131s\u0131tl\u0131 bir firewall kural\u0131 de\u011ferlendirilmelidir.<\/p>\n<h2>Plesk Firewall ve Docker<\/h2>\n<p>Docker kullan\u0131lan Plesk sunucular\u0131nda port yay\u0131nlama i\u015flemlerine ayr\u0131ca dikkat etmek gerekir.<\/p>\n<p>\u00d6rne\u011fin:<\/p>\n<pre><code>Host Port 8080\r\n      \u2193\r\nDocker Container Port 80<\/code><\/pre>\n<p>\u015feklinde bir y\u00f6nlendirme yap\u0131ld\u0131\u011f\u0131nda yaln\u0131zca container ayar\u0131n\u0131 de\u011fil, sunucudaki a\u011f ve firewall yap\u0131land\u0131rmas\u0131n\u0131 da kontrol etmemiz gerekir.<\/p>\n<p>Docker ve Plesk firewall yap\u0131land\u0131rmalar\u0131n\u0131n birlikte kullan\u0131ld\u0131\u011f\u0131 ortamlarda hangi katman\u0131n portu y\u00f6netti\u011fini anlamadan kural eklemek beklenmeyen sonu\u00e7lara yol a\u00e7abilir.<\/p>\n<h2>Plesk Firewall ve firewalld Ayn\u0131 Anda Kullan\u0131l\u0131r m\u0131?<\/h2>\n<p>Bu konu \u00f6zellikle Plesk for Linux kullan\u0131c\u0131lar\u0131 i\u00e7in \u00f6nemlidir.<\/p>\n<p>Plesk&#8217;in resmi dok\u00fcmantasyonunda <strong>Plesk Firewall<\/strong> ile <strong>firewalld<\/strong> ara\u00e7lar\u0131n\u0131n ayn\u0131 anda y\u00f6netim amac\u0131yla kullan\u0131lmas\u0131n\u0131n \u00e7ak\u0131\u015fmalara yol a\u00e7abilece\u011fi ve Plesk&#8217;in \u00e7al\u0131\u015fmas\u0131 i\u00e7in gerekli portlar\u0131n yanl\u0131\u015fl\u0131kla kapat\u0131labilece\u011fi belirtilmektedir.<\/p>\n<p>Bu nedenle firewall y\u00f6netiminde hangi arac\u0131n aktif olarak kullan\u0131laca\u011f\u0131 netle\u015ftirilmelidir.<\/p>\n<p><a href=\"https:\/\/docs.plesk.com\/en-US\/obsidian\/administrator-guide\/plesk-administration\/plesk-for-linux-the-plesk-firewall.72046\/\" target=\"_blank\" rel=\"noopener\">Plesk&#8217;in firewall kullan\u0131m uyar\u0131s\u0131n\u0131<\/a> inceleyebilirsiniz.<\/p>\n<h2>Plesk Firewall Kural\u0131 Uygulanm\u0131yor<\/h2>\n<p>Firewall kural\u0131 ekledi\u011fimiz halde ba\u011flant\u0131 sa\u011flanam\u0131yorsa a\u015fa\u011f\u0131daki noktalar\u0131 kontrol etmeliyiz:<\/p>\n<ul>\n<li>Do\u011fru port numaras\u0131<\/li>\n<li>TCP veya UDP se\u00e7imi<\/li>\n<li>Kaynak IP adresi<\/li>\n<li>Sunucudaki servis durumu<\/li>\n<li>Uygulaman\u0131n ger\u00e7ekten ilgili portu dinleyip dinlemedi\u011fi<\/li>\n<li>Ba\u015fka bir firewall katman\u0131<\/li>\n<li>Cloudflare veya ba\u015fka bir proxy kullan\u0131m\u0131<\/li>\n<\/ul>\n<p>\u00d6rne\u011fin bir servis portu firewall&#8217;da a\u00e7\u0131k olsa bile servis ger\u00e7ekten \u00e7al\u0131\u015fm\u0131yorsa ba\u011flant\u0131 kurulamaz.<\/p>\n<h2>Plesk Firewall ve Cloudflare<\/h2>\n<p>Cloudflare kullan\u0131lan web sitelerinde HTTP ve HTTPS trafi\u011fi i\u00e7in trafik ak\u0131\u015f\u0131n\u0131n nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 bilmek \u00f6nemlidir.<\/p>\n<pre><code>Visitor\r\n   \u2193\r\nCloudflare\r\n   \u2193\r\nOrigin Server\r\n   \u2193\r\nPlesk<\/code><\/pre>\n<p>Web trafi\u011finin Cloudflare \u00fczerinden ge\u00e7ti\u011fi bir yap\u0131da origin sunucuya do\u011frudan internet eri\u015fimini ayr\u0131ca s\u0131n\u0131rland\u0131rma stratejileri uygulanabilir.<\/p>\n<p>Ancak burada yaln\u0131zca web trafi\u011fini de\u011fil, Plesk paneli, SSH, mail ve di\u011fer servisleri de ayr\u0131 de\u011ferlendirmemiz gerekir.<\/p>\n<h2>Plesk Firewall ve Fail2Ban Birlikte Kullan\u0131l\u0131r m\u0131?<\/h2>\n<p>Evet. Plesk for Linux&#8217;ta Fail2Ban, \u015f\u00fcpheli ba\u011flant\u0131lar\u0131 veya ba\u015far\u0131s\u0131z kimlik do\u011frulama giri\u015fimlerini tespit ederek sald\u0131rgan IP adreslerinin engellenmesine yard\u0131mc\u0131 olabilir.<\/p>\n<p>Firewall ba\u011flant\u0131 d\u00fczeyinde kurallar uygularken Fail2Ban log tabanl\u0131 otomatik IP engelleme mekanizmas\u0131 olarak kullan\u0131labilir.<\/p>\n<p>Plesk&#8217;in dok\u00fcmantasyonuna g\u00f6re Fail2Ban Linux sistemlerde SSH, web sunucusu veya Plesk login gibi farkl\u0131 servisler i\u00e7in jail yap\u0131lar\u0131 kullanabilir.<\/p>\n<p><a href=\"https:\/\/docs.plesk.com\/en-US\/obsidian\/administrator-guide\/server-administration\/protection-against-brute-force-attacks.73381\/\" target=\"_blank\" rel=\"noopener\">Plesk Fail2Ban ve brute-force korumas\u0131 rehberini<\/a> inceleyebilirsiniz.<\/p>\n<h2>Plesk Firewall ile ModSecurity Ayn\u0131 \u015eey mi?<\/h2>\n<p>Hay\u0131r. Bu iki g\u00fcvenlik katman\u0131 farkl\u0131 ama\u00e7lara hizmet eder.<\/p>\n<h3>Firewall<\/h3>\n<p>A\u011f ba\u011flant\u0131lar\u0131n\u0131 ve port eri\u015fimini kontrol eder.<\/p>\n<h3>ModSecurity<\/h3>\n<p>Web uygulamalar\u0131na gelen HTTP isteklerini inceleyerek web tabanl\u0131 sald\u0131r\u0131lara kar\u015f\u0131 koruma sa\u011flar.<\/p>\n<p>Plesk&#8217;te ModSecurity, Web Application Firewall olarak kullan\u0131labilir.<\/p>\n<p><a href=\"https:\/\/docs.plesk.com\/en-US\/obsidian\/administrator-guide\/server-administration\/web-application-firewall-modsecurity.73383\/\" target=\"_blank\" rel=\"noopener\">Plesk ModSecurity resmi dok\u00fcmantasyonunu<\/a> inceleyebilirsiniz.<\/p>\n<h2>Plesk Sunucusunda Temel Firewall Yakla\u015f\u0131m\u0131<\/h2>\n<p>Yeni bir Plesk sunucusu yap\u0131land\u0131r\u0131rken m\u00fcmk\u00fcn oldu\u011funca yaln\u0131zca ger\u00e7ekten gerekli servisleri eri\u015filebilir tutmak iyi bir ba\u015flang\u0131\u00e7 noktas\u0131d\u0131r.<\/p>\n<p>\u00d6rne\u011fin tipik bir web hosting sunucusunda:<\/p>\n<pre><code>80   TCP  \u2192 HTTP\r\n443  TCP  \u2192 HTTPS\r\n8443 TCP  \u2192 Plesk\r\n22   TCP  \u2192 SSH\r\n25   TCP  \u2192 SMTP\r\n465  TCP  \u2192 SMTPS\r\n993  TCP  \u2192 IMAPS\r\n<\/code><\/pre>\n<p>gibi servisler kullan\u0131m amac\u0131na g\u00f6re gerekli olabilir.<\/p>\n<p>Her sunucuda ayn\u0131 portlar\u0131n a\u00e7\u0131k olmas\u0131 gerekmez. \u00d6nemli olan kullan\u0131lan servislerle g\u00fcvenlik politikas\u0131n\u0131 e\u015fle\u015ftirmektir.<\/p>\n<h2>Firewall De\u011fi\u015fikli\u011fi Yapmadan \u00d6nce Dikkat Edilmesi Gerekenler<\/h2>\n<p>Firewall \u00fczerinde yanl\u0131\u015f bir kural \u00f6zellikle uzaktan y\u00f6netti\u011fimiz VPS veya dedicated sunucularda eri\u015fim kayb\u0131na neden olabilir.<\/p>\n<ul>\n<li>Aktif SSH ba\u011flant\u0131n\u0131z\u0131 kapatmadan de\u011fi\u015fiklik yap\u0131n.<\/li>\n<li>SSH portunu de\u011fi\u015ftirdiyseniz yeni portu kontrol edin.<\/li>\n<li>Plesk&#8217;in kulland\u0131\u011f\u0131 portlar\u0131 kapatmay\u0131n.<\/li>\n<li>Web, mail ve DNS servislerinin portlar\u0131n\u0131 kullan\u0131m durumuna g\u00f6re de\u011ferlendirin.<\/li>\n<li>De\u011fi\u015fiklikleri k\u00fc\u00e7\u00fck ad\u0131mlarla uygulay\u0131n.<\/li>\n<li>Firewall kurallar\u0131n\u0131 d\u00fczenli olarak g\u00f6zden ge\u00e7irin.<\/li>\n<\/ul>\n<h2>Plesk&#8217;te G\u00fcvenli\u011fi Art\u0131rmak \u0130\u00e7in Ek \u00d6nlemler<\/h2>\n<p>Firewall tek ba\u015f\u0131na tam bir sunucu g\u00fcvenlik \u00e7\u00f6z\u00fcm\u00fc de\u011fildir.<\/p>\n<p>G\u00fcvenli\u011fi art\u0131rmak i\u00e7in firewall ile birlikte:<\/p>\n<ul>\n<li>G\u00fc\u00e7l\u00fc parolalar<\/li>\n<li>SSH key<\/li>\n<li>Fail2Ban<\/li>\n<li>ModSecurity<\/li>\n<li>SSL\/TLS<\/li>\n<li>D\u00fczenli g\u00fcncellemeler<\/li>\n<li>Yedekleme<\/li>\n<\/ul>\n<p>gibi katmanlar\u0131 da birlikte de\u011ferlendirmek gerekir.<\/p>\n<h2>Plesk Sunucusu \u0130\u00e7in Lisans Se\u00e7imi<\/h2>\n<p>Plesk \u00fczerinde web sitelerimizi, DNS kay\u0131tlar\u0131m\u0131z\u0131, e-posta hesaplar\u0131m\u0131z\u0131, veritabanlar\u0131n\u0131 ve g\u00fcvenlik ayarlar\u0131n\u0131 tek panel \u00fczerinden y\u00f6netebiliriz.<\/p>\n<p>VPS veya dedicated sunucunuzda Plesk kullanmak ve lisans maliyetini optimize etmek istiyorsan\u0131z <a href=\"https:\/\/licensepow.com\/plesk-license.php\"><strong>uygun fiyatl\u0131 Plesk Lisans\u0131<\/strong><\/a> se\u00e7eneklerimizi inceleyebilirsiniz.<\/p>\n<p>\u00d6zellikle birden fazla domain bar\u0131nd\u0131ran sunucularda lisans maliyetinin yan\u0131nda backup, firewall ve sunucu kaynaklar\u0131n\u0131 da birlikte planlaman\u0131z\u0131 \u00f6neriyoruz.<\/p>\n<h2>Sonu\u00e7<\/h2>\n<p><strong>Plesk&#8217;te Firewall yap\u0131land\u0131rmak<\/strong>, sunucu g\u00fcvenli\u011finin temel katmanlar\u0131ndan biridir. Plesk Firewall sayesinde gerekli portlar\u0131 eri\u015fime a\u00e7abilir, kullan\u0131lmayan ba\u011flant\u0131lar\u0131 s\u0131n\u0131rland\u0131rabilir ve belirli IP adreslerine \u00f6zel eri\u015fim kurallar\u0131 olu\u015fturabiliriz.<\/p>\n<p>Ancak firewall ayarlar\u0131nda en \u00f6nemli nokta, yaln\u0131zca gerekli servisleri a\u00e7\u0131k tutmak ve kullan\u0131lan servislerin ger\u00e7ek ihtiya\u00e7lar\u0131na g\u00f6re kural olu\u015fturmakt\u0131r. \u00d6zellikle SSH, Plesk paneli, MySQL ve Docker gibi servislerde yanl\u0131\u015f bir port kural\u0131 hem g\u00fcvenlik hem de eri\u015fim sorunlar\u0131na neden olabilir.<\/p>\n<p>Firewall&#8217;u Fail2Ban, ModSecurity, SSL\/TLS ve d\u00fczenli yedekleme gibi di\u011fer g\u00fcvenlik katmanlar\u0131yla birlikte de\u011ferlendirdi\u011fimizde \u00e7ok daha sa\u011flam bir Plesk sunucusu olu\u015fturabiliriz.<\/p>\n<h2>S\u0131k Sorulan Sorular<\/h2>\n<h3>Plesk&#8217;te Firewall nas\u0131l a\u00e7\u0131l\u0131r?<\/h3>\n<p>Plesk for Linux \u00fczerinde Firewall extension kurulduktan sonra Tools &amp; Settings \u2192 Security \u2192 Firewall b\u00f6l\u00fcm\u00fcnden firewall kurallar\u0131 ve politikalar\u0131 y\u00f6netilebilir.<\/p>\n<h3>Plesk Firewall hangi portu kullan\u0131r?<\/h3>\n<p>Plesk y\u00f6netim paneli HTTPS \u00fczerinden standart olarak 8443\/TCP portunu kullan\u0131r. Web, SSH, mail ve di\u011fer servislerin farkl\u0131 portlar\u0131 vard\u0131r.<\/p>\n<h3>Plesk&#8217;te SSH portu nas\u0131l a\u00e7\u0131l\u0131r?<\/h3>\n<p>Firewall kurallar\u0131 b\u00f6l\u00fcm\u00fcnden kullan\u0131lan SSH portuna TCP eri\u015fimi verilmelidir. Varsay\u0131lan SSH portu \u00e7o\u011fu Linux sisteminde 22\/TCP&#8217;dir.<\/p>\n<h3>Plesk Firewall ile firewalld birlikte kullan\u0131labilir mi?<\/h3>\n<p>Plesk&#8217;in resmi dok\u00fcmantasyonuna g\u00f6re iki firewall y\u00f6netim arac\u0131n\u0131n ayn\u0131 anda kullan\u0131lmas\u0131 \u00e7ak\u0131\u015fmalara neden olabilir. Bu nedenle tek bir firewall y\u00f6netim mekanizmas\u0131 tercih edilmelidir.<\/p>\n<h3>Plesk&#8217;te 3306 portu internete a\u00e7\u0131lmal\u0131 m\u0131?<\/h3>\n<p>\u00c7o\u011fu web hosting senaryosunda MySQL veya MariaDB&#8217;nin 3306 portunu public internete a\u00e7mak gerekli de\u011fildir. Uzak eri\u015fim gerekiyorsa yaln\u0131zca gerekli kaynak IP adreslerine izin verilmesi daha g\u00fcvenli olabilir.<\/p>\n<h3>Plesk Firewall g\u00fcvenli\u011fi tek ba\u015f\u0131na yeterli midir?<\/h3>\n<p>Hay\u0131r. Firewall \u00f6nemli bir g\u00fcvenlik katman\u0131d\u0131r ancak Fail2Ban, ModSecurity, SSL\/TLS, g\u00fcncellemeler, g\u00fc\u00e7l\u00fc kimlik do\u011frulama ve yedekleme gibi ek \u00f6nlemlerle birlikte kullan\u0131lmal\u0131d\u0131r.<\/p>\n<p><script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Plesk'te Firewall nas\u0131l a\u00e7\u0131l\u0131r?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Plesk for Linux \u00fczerinde Firewall extension kurulduktan sonra Tools & Settings \u2192 Security \u2192 Firewall b\u00f6l\u00fcm\u00fcnden firewall kurallar\u0131 ve politikalar\u0131 y\u00f6netilebilir.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Plesk Firewall hangi portu kullan\u0131r?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Plesk y\u00f6netim paneli HTTPS \u00fczerinden standart olarak 8443\/TCP portunu kullan\u0131r. Web, SSH, mail ve di\u011fer servislerin farkl\u0131 portlar\u0131 vard\u0131r.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Plesk'te SSH portu nas\u0131l a\u00e7\u0131l\u0131r?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Firewall kurallar\u0131 b\u00f6l\u00fcm\u00fcnden kullan\u0131lan SSH portuna TCP eri\u015fimi verilmelidir. Varsay\u0131lan SSH portu \u00e7o\u011fu Linux sisteminde 22\/TCP'dir.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Plesk Firewall ile firewalld birlikte kullan\u0131labilir mi?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Plesk'in resmi dok\u00fcmantasyonuna g\u00f6re iki firewall y\u00f6netim arac\u0131n\u0131n ayn\u0131 anda kullan\u0131lmas\u0131 \u00e7ak\u0131\u015fmalara neden olabilir. Bu nedenle tek bir firewall y\u00f6netim mekanizmas\u0131 tercih edilmelidir.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Plesk'te 3306 portu internete a\u00e7\u0131lmal\u0131 m\u0131?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"\u00c7o\u011fu web hosting senaryosunda MySQL veya MariaDB'nin 3306 portunu public internete a\u00e7mak gerekli de\u011fildir. Uzak eri\u015fim gerekiyorsa yaln\u0131zca gerekli kaynak IP adreslerine izin verilmesi daha g\u00fcvenli olabilir.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Plesk Firewall g\u00fcvenli\u011fi tek ba\u015f\u0131na yeterli midir?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Hay\u0131r. Firewall \u00f6nemli bir g\u00fcvenlik katman\u0131d\u0131r ancak Fail2Ban, ModSecurity, SSL\/TLS, g\u00fcncellemeler, g\u00fc\u00e7l\u00fc kimlik do\u011frulama ve yedekleme gibi ek \u00f6nlemlerle birlikte kullan\u0131lmal\u0131d\u0131r.\"\n      }\n    }\n  ]\n}\n<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Plesk&#8217;te Firewall nas\u0131l yap\u0131land\u0131r\u0131l\u0131r? Port a\u00e7ma, SSH, 8443, 3306, IP k\u0131s\u0131tlama, Fail2Ban ve g\u00fcvenlik ayarlar\u0131n\u0131 \u00f6\u011frenin.<\/p>\n","protected":false},"author":1,"featured_media":216,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[793,791,789,351,787,349,109,503,399,773,359,107,135],"class_list":["post-219","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-plesk","tag-3306-portu","tag-8443-portu","tag-fail2ban","tag-firewall","tag-guvenlik-duvari","tag-modsecurity","tag-plesk-tr","tag-plesk-firewall","tag-plesk-vps","tag-ssh","tag-sunucu-guvenligi","tag-sunucu-yonetimi","tag-vps"],"_links":{"self":[{"href":"https:\/\/licensepow.com\/blog\/wp-json\/wp\/v2\/posts\/219","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/licensepow.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/licensepow.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/licensepow.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/licensepow.com\/blog\/wp-json\/wp\/v2\/comments?post=219"}],"version-history":[{"count":1,"href":"https:\/\/licensepow.com\/blog\/wp-json\/wp\/v2\/posts\/219\/revisions"}],"predecessor-version":[{"id":220,"href":"https:\/\/licensepow.com\/blog\/wp-json\/wp\/v2\/posts\/219\/revisions\/220"}],"wp:attachment":[{"href":"https:\/\/licensepow.com\/blog\/wp-json\/wp\/v2\/media?parent=219"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/licensepow.com\/blog\/wp-json\/wp\/v2\/categories?post=219"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/licensepow.com\/blog\/wp-json\/wp\/v2\/tags?post=219"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}