{"id":775,"date":"2026-09-16T10:51:15","date_gmt":"2026-09-16T10:51:15","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=775"},"modified":"2026-09-16T09:30:04","modified_gmt":"2026-09-16T09:30:04","slug":"vpste-wordpress-kurulumu-adim-adim","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/vpste-wordpress-kurulumu-adim-adim\/","title":{"rendered":"VPS&#8217;te WordPress Kurulumu: Ad\u0131m Ad\u0131m Rehber"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">H\u0131zl\u0131 \u00d6zet &#8211; VPS&#039;te WordPress Kurulumu<\/p>\n<p>WordPress&#039;i VPS&#039;e kurarken DNS, web sunucusu, PHP-FPM, MariaDB, HTTPS ve yedekleme birlikte ele al\u0131nmal\u0131d\u0131r. Ubuntu 24.04, Nginx ve MariaDB tabanl\u0131 ak\u0131\u015f \u015fu s\u0131ray\u0131 izler:<\/p>\n<ul>\n<li><strong>Sunucuyu haz\u0131rlay\u0131n<\/strong> \u2014 G\u00fcncellemeleri uygulay\u0131n, sudo kullan\u0131c\u0131s\u0131 olu\u015fturun ve SSH ile 80\/443 portlar\u0131n\u0131 g\u00fcvenli bi\u00e7imde a\u00e7\u0131n.<\/li>\n<li><strong>DNS&#039;i do\u011frulay\u0131n<\/strong> \u2014 Alan ad\u0131n\u0131n A ve gerekiyorsa AAAA kay\u0131tlar\u0131n\u0131n do\u011fru VPS adresine \u00e7\u00f6z\u00fcld\u00fc\u011f\u00fcn\u00fc kontrol edin.<\/li>\n<li><strong>Yaz\u0131l\u0131m\u0131 kurun<\/strong> \u2014 Nginx, PHP-FPM, gerekli PHP mod\u00fclleri ve MariaDB paketlerini y\u00fckleyip servisleri etkinle\u015ftirin.<\/li>\n<li><strong>Veritaban\u0131 olu\u015fturun<\/strong> \u2014 WordPress i\u00e7in ayr\u0131 bir utf8mb4 veritaban\u0131 ve yaln\u0131zca bu veritaban\u0131nda yetkili kullan\u0131c\u0131 tan\u0131mlay\u0131n.<\/li>\n<li><strong>HTTPS ekleyin<\/strong> \u2014 Nginx sanal host yap\u0131land\u0131rmas\u0131n\u0131 test edin, ard\u0131ndan Certbot ile Let&#039;s Encrypt sertifikas\u0131 al\u0131n.<\/li>\n<li><strong>Yedekleyin ve izleyin<\/strong> \u2014 wp-content ile veritaban\u0131n\u0131 uzak hedefe yedekleyin, geri d\u00f6n\u00fc\u015f provas\u0131 yap\u0131n ve g\u00fcnl\u00fckleri takip edin.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">VPS WordPress kurulumu i\u00e7in Ubuntu 24.04 \u00fczerinde Nginx, PHP-FPM ve MariaDB kurup alan ad\u0131n\u0131 sunucuya y\u00f6nlendirin; ayr\u0131 bir veritaban\u0131 kullan\u0131n, Nginx yap\u0131land\u0131rmas\u0131n\u0131 test edin, Let&#039;s Encrypt ile HTTPS ekleyin ve kurulumdan sonra yedekleme ile g\u00fcncelleme d\u00fczeni olu\u015fturun. B\u00f6ylece yaln\u0131zca \u00e7al\u0131\u015fan de\u011fil, y\u00f6netilebilir bir WordPress sunucusu elde edersiniz.<\/p>\n<div class=\"aiw-toc\" style=\"border:1px solid #dbe3ea;border-radius:8px;padding:16px 20px;margin:0 0 28px\">\n<p class=\"aiw-toc-head\"><strong>\u0130\u00e7indekiler<\/strong><span class=\"aiw-toc-meta\"> \u00b7 12 dk okuma<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#vpste-wordpress-kurmak-icin-hangi-hazirliklar-gerekir\">VPS&#039;te WordPress kurmak i\u00e7in hangi haz\u0131rl\u0131klar gerekir?<\/a><\/li>\n<li><a href=\"#vps-wordpress-kurulumu-oncesi-dns-ve-sunucu-hazirligi\">VPS WordPress kurulumu \u00f6ncesi DNS ve sunucu haz\u0131rl\u0131\u011f\u0131<\/a><\/li>\n<li><a href=\"#nginx-php-fpm-ve-mariadb-nasil-kurulur\">Nginx, PHP-FPM ve MariaDB nas\u0131l kurulur?<\/a><\/li>\n<li><a href=\"#wordpress-veritabani-ve-kullanici-hesabi-nasil-olusturulur\">WordPress veritaban\u0131 ve kullan\u0131c\u0131 hesab\u0131 nas\u0131l olu\u015fturulur?<\/a><\/li>\n<li><a href=\"#wordpress-dosyalari-vpse-nasil-yuklenir\">WordPress dosyalar\u0131 VPS&#039;e nas\u0131l y\u00fcklenir?<\/a><\/li>\n<li><a href=\"#nginx-sanal-host-yapilandirmasi-nasil-yapilir\">Nginx sanal host yap\u0131land\u0131rmas\u0131 nas\u0131l yap\u0131l\u0131r?<\/a><\/li>\n<li><a href=\"#https-ve-wordpress-ilk-kurulum-ekrani-nasil-tamamlanir\">HTTPS ve WordPress ilk kurulum ekran\u0131 nas\u0131l tamamlan\u0131r?<\/a><\/li>\n<li><a href=\"#vps-wordpress-kurulumu-sonrasinda-hangi-guvenlik-ayarlari-yapilmali\">VPS WordPress kurulumu sonras\u0131nda hangi g\u00fcvenlik ayarlar\u0131 yap\u0131lmal\u0131?<\/a><\/li>\n<li><a href=\"#performans-icin-php-onbellek-ve-yedekleme-ayarlari\">Performans i\u00e7in PHP, \u00f6nbellek ve yedekleme ayarlar\u0131<\/a><\/li>\n<li><a href=\"#kurulum-sorunlarini-nasil-teshis-edebilirsiniz\">Kurulum sorunlar\u0131n\u0131 nas\u0131l te\u015fhis edebilirsiniz?<\/a><\/li>\n<li><a href=\"#kuruluma-baslamadan-once-sunlari-kontrol-edin\">Kuruluma Ba\u015flamadan \u00d6nce \u015eunlar\u0131 Kontrol Edin<\/a><\/li>\n<li><a href=\"#sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/a><\/li>\n<li><a href=\"#kaynaklar\">Kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"vpste-wordpress-kurmak-icin-hangi-hazirliklar-gerekir\">VPS&#8217;te WordPress kurmak i\u00e7in hangi haz\u0131rl\u0131klar gerekir?<\/h2>\n<p>WordPress kurulumu, dosyalar\u0131 sunucuya kopyalamaktan ibaret de\u011fildir. Alan ad\u0131 DNS kayd\u0131, web sunucusu, PHP-FPM, veritaban\u0131, dosya izinleri, HTTPS ve g\u00fcncelleme politikas\u0131 birlikte haz\u0131rlanmal\u0131d\u0131r. A\u015fa\u011f\u0131daki \u00f6rnek Ubuntu 24.04 LTS \u00fczerinde Nginx, PHP-FPM ve MariaDB 10.11 kullan\u0131r. Komutlar\u0131 root yerine sudo yetkili ayr\u0131 bir kullan\u0131c\u0131yla \u00e7al\u0131\u015ft\u0131rmak daha g\u00fcvenlidir.<\/p>\n<p>WordPress&#8217;in resmi gereksinimleri PHP 7.4 veya \u00fczeri ile MySQL 8.0 veya \u00fczerini ya da MariaDB 10.6 veya \u00fczerini listeler. Kullan\u0131lan PHP s\u00fcr\u00fcm\u00fcn\u00fcn da\u011f\u0131t\u0131m ve eklenti deste\u011fini ayr\u0131ca kontrol edin. HTTPS ise yaln\u0131zca adres \u00e7ubu\u011fundaki kilit simgesi de\u011fildir; y\u00f6netici parolalar\u0131 ve oturum \u00e7erezleri \u015fifreli ta\u015f\u0131nmal\u0131d\u0131r.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Kuruluma ba\u015flamadan \u00f6nce i\u015fletim sistemi s\u00fcr\u00fcm\u00fcn\u00fc, RAM miktar\u0131n\u0131, disk alan\u0131n\u0131 ve alan ad\u0131n\u0131n do\u011fru VPS IP&#8217;sine y\u00f6nlendi\u011fini do\u011frulay\u0131n.<\/p>\n<h2 id=\"vps-wordpress-kurulumu-oncesi-dns-ve-sunucu-hazirligi\">VPS WordPress kurulumu \u00f6ncesi DNS ve sunucu haz\u0131rl\u0131\u011f\u0131<\/h2>\n<p>\u00d6nce alan ad\u0131n\u0131n A kayd\u0131n\u0131 VPS&#8217;in IPv4 adresine, varsa AAAA kayd\u0131n\u0131 VPS&#8217;in IPv6 adresine y\u00f6nlendirin. IPv6 yap\u0131land\u0131r\u0131lmad\u0131ysa rastgele bir AAAA kayd\u0131 b\u0131rakmak, baz\u0131 ziyaret\u00e7ilerin \u00e7al\u0131\u015fan IPv4 yerine eri\u015filemeyen IPv6 yolunu se\u00e7mesine neden olabilir.<\/p>\n<pre><code>dig +short example.com A\ndig +short example.com AAAA\nhostnamectl\nfree -h\ndf -hT<\/code><\/pre>\n<p><code>dig +short<\/code> \u00e7\u0131kt\u0131s\u0131nda beklenen IP adresini g\u00f6rmelisiniz. <code>df -hT<\/code> ise \u00f6zellikle <code>\/<\/code> ve <code>\/var<\/code> b\u00f6l\u00fcmlerindeki bo\u015f alan\u0131 g\u00f6sterir. K\u00fc\u00e7\u00fck bir blog i\u00e7in 1 GB RAM ve 20 GB SSD teknik olarak yeterli olabilir; eklenti, medya ve trafik artt\u0131k\u00e7a PHP i\u015f\u00e7ileri ile disk alan\u0131 ayr\u0131ca planlanmal\u0131d\u0131r.<\/p>\n<p>SSH eri\u015fimini de kurulumdan \u00f6nce d\u00fczenleyin. Yeni bir y\u00f6netici kullan\u0131c\u0131 olu\u015fturup anahtar tabanl\u0131 giri\u015fe ge\u00e7in, ard\u0131ndan g\u00fcvenlik duvar\u0131nda yaln\u0131zca gerekli portlar\u0131 a\u00e7\u0131n. SSH portunu de\u011fi\u015ftirmek tek ba\u015f\u0131na g\u00fcvenlik sa\u011flamaz; g\u00fc\u00e7l\u00fc kimlik do\u011frulama, g\u00fcncel paketler ve ba\u015far\u0131s\u0131z giri\u015flerin izlenmesi daha de\u011ferlidir.<\/p>\n<pre><code>sudo adduser deploy\nsudo usermod -aG sudo deploy\nsudo apt update &amp;&amp; sudo apt full-upgrade -y\nsudo apt install -y ufw fail2ban curl unzip ca-certificates\nsudo ufw allow OpenSSH\nsudo ufw allow 80\/tcp\nsudo ufw allow 443\/tcp\nsudo ufw enable\nsudo ufw status verbose<\/code><\/pre>\n<p>Sunucuda \u00e7al\u0131\u015fan ba\u015fka bir servis varsa <code>OpenSSH<\/code> kural\u0131n\u0131n ger\u00e7ek SSH portunu kapsad\u0131\u011f\u0131n\u0131 kontrol edin. UFW&#8217;yi etkinle\u015ftirmeden \u00f6nce mevcut SSH oturumunu kapatmay\u0131n; ikinci bir terminalden ba\u011flant\u0131y\u0131 test edin.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; DNS \u00e7\u00f6z\u00fcmlemesini ve ikinci SSH oturumunu do\u011frulamadan g\u00fcvenlik duvar\u0131 ayarlar\u0131n\u0131 tamamlanm\u0131\u015f kabul etmeyin.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">\u0130pucu<\/p>\n<p>Kurulumdan \u00f6nce alan ad\u0131n\u0131z\u0131 ve VPS IP adresinizi ayr\u0131 bir terminalde test edin: dig +short example.com. Beklenmeyen eski bir IP g\u00f6r\u00fcyorsan\u0131z WordPress dosyalar\u0131na ge\u00e7meden DNS \u00f6nbelle\u011fini ve nameserver delegasyonunu \u00e7\u00f6z\u00fcn.<\/p>\n<\/div>\n<h2 id=\"nginx-php-fpm-ve-mariadb-nasil-kurulur\">Nginx, PHP-FPM ve MariaDB nas\u0131l kurulur?<\/h2>\n<p>WordPress isteklerini Nginx kar\u015f\u0131lar, PHP kodunu PHP-FPM \u00e7al\u0131\u015ft\u0131r\u0131r, yaz\u0131 ve ayar verilerini MariaDB saklar. Bu par\u00e7alar\u0131n g\u00f6revleri ayr\u0131d\u0131r. Nginx do\u011frudan PHP yorumlamaz; ilgili iste\u011fi Unix soketi veya TCP \u00fczerinden PHP-FPM havuzuna iletir.<\/p>\n<pre><code>sudo apt install -y nginx mariadb-server mariadb-client \\\n  php-fpm php-mysql php-curl php-gd php-mbstring php-xml \\\n  php-zip php-intl php-imagick\nsudo systemctl enable --now nginx mariadb\nsudo systemctl status nginx mariadb --no-pager<\/code><\/pre>\n<p>Ubuntu 24.04 depolar\u0131nda PHP s\u00fcr\u00fcm\u00fc da\u011f\u0131t\u0131m\u0131n paket politikas\u0131na g\u00f6re gelir. S\u00fcr\u00fcm\u00fc ve PHP-FPM servis ad\u0131n\u0131 kontrol edin:<\/p>\n<pre><code>php -v\nphp -m | sort\nsystemctl list-units 'php*-fpm.service' --no-legend<\/code><\/pre>\n<p>WordPress i\u00e7in gerekli PHP mod\u00fcllerinden biri eksikse y\u00f6netim panelinde eklenti kurulumu, g\u00f6rsel i\u015fleme veya kal\u0131c\u0131 ba\u011flant\u0131 i\u015flemleri hata verebilir. Her eklentinin ayn\u0131 kaynak t\u00fcketmedi\u011fini de hesaba kat\u0131n; PHP-FPM havuzunu tahminle b\u00fcy\u00fctmek yerine RAM ve CPU kullan\u0131m\u0131n\u0131 izleyin.<\/p>\n<p>MariaDB&#8217;nin ilk g\u00fcvenlik ayarlar\u0131 i\u00e7in interaktif komutu \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n<pre><code>sudo mariadb-secure-installation<\/code><\/pre>\n<p>Yerel root hesab\u0131n\u0131n parola davran\u0131\u015f\u0131, anonim kullan\u0131c\u0131lar, test veritaban\u0131 ve uzaktan root eri\u015fimi hakk\u0131nda sorular g\u00f6receksiniz. \u00dcretim VPS&#8217;inde uzaktan root veritaban\u0131 eri\u015fimi gereksizdir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; PHP-FPM servis ad\u0131n\u0131 sistemde ger\u00e7ekten bulunan s\u00fcr\u00fcmle e\u015fle\u015ftirin; dosya yolunu tahmin ederek Nginx yap\u0131land\u0131rmay\u0131n.<\/p>\n<h2 id=\"wordpress-veritabani-ve-kullanici-hesabi-nasil-olusturulur\">WordPress veritaban\u0131 ve kullan\u0131c\u0131 hesab\u0131 nas\u0131l olu\u015fturulur?<\/h2>\n<p>WordPress i\u00e7in ayr\u0131 bir veritaban\u0131 ve yaln\u0131zca o veritaban\u0131nda yetkili ayr\u0131 bir kullan\u0131c\u0131 olu\u015fturun. Uygulamay\u0131 MariaDB root hesab\u0131yla \u00e7al\u0131\u015ft\u0131rmak, bir eklenti a\u00e7\u0131\u011f\u0131n\u0131n etkisini gereksiz yere b\u00fcy\u00fct\u00fcr.<\/p>\n<pre><code>sudo mariadb<\/code><\/pre>\n<pre><code>CREATE DATABASE wp_site CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;\nCREATE USER 'wp_user'@'localhost' IDENTIFIED BY 'Buraya-uzun-ve-rastgele-bir-parola';\nGRANT ALL PRIVILEGES ON wp_site.* TO 'wp_user'@'localhost';\nFLUSH PRIVILEGES;\nEXIT;<\/code><\/pre>\n<p><code>utf8mb4<\/code>, T\u00fcrk\u00e7e karakterler ve d\u00f6rt baytl\u0131k Unicode karakterleri i\u00e7in uygun se\u00e7imdir. Parolay\u0131 sohbet, terminal ge\u00e7mi\u015fi veya d\u00fcz metin notlar\u0131nda saklamay\u0131n; parola y\u00f6neticisi kullan\u0131n. Y\u00fcksek rastgelelikte bir parola \u00fcretmek i\u00e7in <code>openssl rand<\/code> kullan\u0131labilir:<\/p>\n<pre><code>openssl rand -base64 32<\/code><\/pre>\n<p>Veritaban\u0131 hesab\u0131n\u0131n eri\u015fimini test etmek i\u00e7in:<\/p>\n<pre><code>mariadb -u wp_user -p -h localhost wp_site -e 'SELECT VERSION();'<\/code><\/pre>\n<p>Bu komut MariaDB s\u00fcr\u00fcm\u00fcn\u00fc d\u00f6nd\u00fcrmelidir. <code>Access denied<\/code> g\u00f6r\u00fcrseniz \u00f6nce kullan\u0131c\u0131 ad\u0131, veritaban\u0131 ad\u0131, parola ve host de\u011ferlerini kontrol edin; tablo olu\u015fturmaya ge\u00e7meden \u00f6nce kimlik do\u011frulamay\u0131 \u00e7\u00f6z\u00fcn.<\/p>\n<h2 id=\"wordpress-dosyalari-vpse-nasil-yuklenir\">WordPress dosyalar\u0131 VPS&#8217;e nas\u0131l y\u00fcklenir?<\/h2>\n<p>Site dosyalar\u0131n\u0131 \u00f6rnekte <code>\/var\/www\/example.com<\/code> alt\u0131nda tutal\u0131m. Alan ad\u0131n\u0131z\u0131 kendi de\u011ferinizle de\u011fi\u015ftirin. Ar\u015fivi resmi WordPress adresinden indirin; \u00fcretim ortamlar\u0131nda kullan\u0131lan s\u00fcr\u00fcm\u00fcn b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc ve indirme kayna\u011f\u0131n\u0131 kontrol etmek iyi bir al\u0131\u015fkanl\u0131kt\u0131r.<\/p>\n<pre><code>sudo mkdir -p \/var\/www\/example.com\ncd \/tmp\ncurl -O https:\/\/wordpress.org\/latest.tar.gz\nsudo tar -xzf latest.tar.gz -C \/var\/www\/example.com --strip-components=1\nsudo chown -R www-data:www-data \/var\/www\/example.com\nsudo find \/var\/www\/example.com -type d -exec chmod 755 {} \\;\nsudo find \/var\/www\/example.com -type f -exec chmod 644 {} \\;<\/code><\/pre>\n<p>Web sunucusunun dosyalar\u0131 okuyabilmesi gerekir. WordPress&#8217;in y\u00fckleme ve \u00f6nbellek i\u015flemleri i\u00e7in baz\u0131 dizinlere yazma eri\u015fimi gerekebilir; b\u00fct\u00fcn a\u011faca <code>chmod 777<\/code> vermek \u00e7\u00f6z\u00fcm de\u011fildir. B\u00f6yle bir izin, sorunun ad\u0131n\u0131 de\u011fi\u015ftirir, kendisini de\u011fil.<\/p>\n<p>Yap\u0131land\u0131rma dosyas\u0131n\u0131 \u00f6rnek dosyadan \u00fcretin:<\/p>\n<pre><code>cd \/var\/www\/example.com\nsudo -u www-data cp wp-config-sample.php wp-config.php\nsudo -u www-data vim wp-config.php<\/code><\/pre>\n<p><code>DB_NAME<\/code>, <code>DB_USER<\/code>, <code>DB_PASSWORD<\/code> ve <code>DB_HOST<\/code> de\u011ferlerini olu\u015fturdu\u011funuz bilgilerle de\u011fi\u015ftirin. <code>AUTH_KEY<\/code>, <code>SECURE_AUTH_KEY<\/code> ve di\u011fer salt de\u011ferlerini WordPress&#8217;in resmi salt \u00fcretim servisiyle yenileyin; \u00f6rnek de\u011ferleri \u00fcretim sitesinde b\u0131rakmay\u0131n.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; <code>wp-config.php<\/code> i\u00e7indeki veritaban\u0131 bilgilerini girip dosyan\u0131n sahibi ve izinlerini tekrar kontrol edin.<\/p>\n<h2 id=\"nginx-sanal-host-yapilandirmasi-nasil-yapilir\">Nginx sanal host yap\u0131land\u0131rmas\u0131 nas\u0131l yap\u0131l\u0131r?<\/h2>\n<p>Nginx, alan ad\u0131n\u0131 do\u011fru WordPress dizinine y\u00f6nlendiren bir server blo\u011funa ihtiya\u00e7 duyar. A\u015fa\u011f\u0131daki yap\u0131land\u0131rmada PHP istekleri yaln\u0131zca mevcut dosya yoksa PHP-FPM&#8217;e g\u00f6nderilir; statik dosyalar gereksiz yere PHP i\u015f\u00e7isine gitmez.<\/p>\n<pre><code>sudo vim \/etc\/nginx\/sites-available\/example.com<\/code><\/pre>\n<pre><code>server {\n    listen 80;\n    listen [::]:80;\n    server_name example.com www.example.com;\n\n    root \/var\/www\/example.com;\n    index index.php index.html;\n\n    client_max_body_size 64M;\n\n    location \/ {\n        try_files $uri $uri\/ \/index.php?$args;\n    }\n\n    location ~ \\.php$ {\n        include snippets\/fastcgi-php.conf;\n        fastcgi_pass unix:\/run\/php\/php8.3-fpm.sock;\n    }\n\n    location ~* \/\\. {\n        deny all;\n    }\n}<\/code><\/pre>\n<p>PHP-FPM soket yolu sisteminizde farkl\u0131 olabilir. <code>ls \/run\/php\/<\/code> ile ger\u00e7ek dosya ad\u0131n\u0131 g\u00f6r\u00fcn. Ard\u0131ndan siteyi etkinle\u015ftirip varsay\u0131lan siteyi kald\u0131rabilirsiniz; bunu ba\u015fka bir web sitesi \u00e7al\u0131\u015fmad\u0131\u011f\u0131ndan eminseniz yap\u0131n.<\/p>\n<pre><code>sudo ln -s \/etc\/nginx\/sites-available\/example.com \/etc\/nginx\/sites-enabled\/example.com\nsudo rm -f \/etc\/nginx\/sites-enabled\/default\nsudo nginx -t\nsudo systemctl reload nginx<\/code><\/pre>\n<p><code>nginx -t<\/code> sat\u0131r\u0131nda <code>syntax is ok<\/code> ve <code>test is successful<\/code> g\u00f6r\u00fclmeden reload \u00e7al\u0131\u015ft\u0131rmay\u0131n. K\u00fc\u00e7\u00fck bir noktal\u0131 virg\u00fcl eksikli\u011fi bile \u00e7al\u0131\u015fan sitenin eri\u015filemez olmas\u0131na yol a\u00e7abilir.<\/p>\n<p>Kal\u0131c\u0131 ba\u011flant\u0131lar i\u00e7in <code>try_files<\/code> sat\u0131r\u0131 kritiktir. Bu sat\u0131r yoksa ana sayfa a\u00e7\u0131l\u0131p yaz\u0131 URL&#8217;leri 404 d\u00f6nd\u00fcrebilir. 404 sorunlar\u0131 i\u00e7in ayr\u0131ca <a href=\"https:\/\/www.vps.tc\/blog\/tr\/404-hatasi-nedir-sebepleri-ve-cozum-yollari\/\">404 Hatas\u0131 Nedir? Sebepleri ve \u00c7\u00f6z\u00fcm Yollar\u0131<\/a> yaz\u0131s\u0131ndaki te\u015fhis ad\u0131mlar\u0131na bakabilirsiniz.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; PHP-FPM soketini do\u011frulay\u0131n, ard\u0131ndan yaln\u0131zca ba\u015far\u0131l\u0131 <code>nginx -t<\/code> \u00e7\u0131kt\u0131s\u0131ndan sonra reload yap\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>Nginx yap\u0131land\u0131rmas\u0131n\u0131 d\u00fczenledikten sonra do\u011frudan reload \u00e7al\u0131\u015ft\u0131rmay\u0131n. \u00d6nce nginx -t komutunu \u00e7al\u0131\u015ft\u0131r\u0131n; hata varsa servis mevcut yap\u0131land\u0131rmayla \u00e7al\u0131\u015fmaya devam eder ve yanl\u0131\u015f bir reload ile \u00e7al\u0131\u015fan siteyi de riske atmam\u0131\u015f olursunuz.<\/p>\n<\/div>\n<h2 id=\"https-ve-wordpress-ilk-kurulum-ekrani-nasil-tamamlanir\">HTTPS ve WordPress ilk kurulum ekran\u0131 nas\u0131l tamamlan\u0131r?<\/h2>\n<p>HTTP \u00fczerinden alan ad\u0131n\u0131 a\u00e7arak WordPress web kurulumunu test edin. Dil, site ba\u015fl\u0131\u011f\u0131, y\u00f6netici kullan\u0131c\u0131 ad\u0131, parola ve e-posta adresini belirleyin. Y\u00f6netici kullan\u0131c\u0131 ad\u0131n\u0131 <code>admin<\/code> se\u00e7mek zorunda de\u011filsiniz; tahmin edilmesi kolay adlar brute-force denemelerini kolayla\u015ft\u0131r\u0131r.<\/p>\n<p>Site HTTP \u00fczerinden d\u00fczg\u00fcn a\u00e7\u0131ld\u0131ktan sonra Let&#8217;s Encrypt sertifikas\u0131 al\u0131n. Certbot&#8217;un Nginx eklentisi, uygun server blo\u011funu bulup sertifika ve y\u00f6nlendirme ayarlar\u0131n\u0131 d\u00fczenleyebilir.<\/p>\n<pre><code>sudo apt install -y certbot python3-certbot-nginx\nsudo certbot --nginx -d example.com -d www.example.com\nsudo certbot renew --dry-run<\/code><\/pre>\n<p><code>--dry-run<\/code>, yenileme ak\u0131\u015f\u0131n\u0131 ger\u00e7ek sertifikay\u0131 de\u011fi\u015ftirmeden s\u0131nar. Sertifika yenilemesinin otomatik \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 yaln\u0131zca cron dosyas\u0131na bakarak varsaymay\u0131n; g\u00fcnl\u00fckleri ve deneme \u00e7\u0131kt\u0131s\u0131n\u0131 kontrol edin.<\/p>\n<p>HTTPS sonras\u0131nda WordPress adreslerinin <code>https:\/\/<\/code> ile ba\u015flad\u0131\u011f\u0131n\u0131 y\u00f6netim panelindeki Ayarlar, Genel ekran\u0131ndan do\u011frulay\u0131n. HTTP&#8217;den HTTPS&#8217;e y\u00f6nlendirme s\u0131ras\u0131nda d\u00f6ng\u00fc olu\u015fursa ters proxy ba\u015fl\u0131klar\u0131, <code>siteurl<\/code> ve <code>home<\/code> de\u011ferleri birlikte incelenmelidir. HTTPS kullan\u0131m\u0131yla ilgili y\u00f6nlendirme sonras\u0131nda <a href=\"https:\/\/www.vps.tc\/blog\/tr\/301-yonlendirme-nedir-seo-kullanim-rehberi\/\">301 Y\u00f6nlendirme Nedir? SEO \u0130\u00e7in Kullan\u0131m Rehberi<\/a> yaz\u0131s\u0131ndaki durum kodu a\u00e7\u0131klamalar\u0131 yard\u0131mc\u0131 olabilir.<\/p>\n<p>\u0130lk kurulumdan sonra <code>https:\/\/example.com\/wp-admin<\/code> adresine girin. Kal\u0131c\u0131 ba\u011flant\u0131 ayar\u0131n\u0131 se\u00e7ip kaydedin; Nginx&#8217;teki <code>try_files<\/code> sat\u0131r\u0131 do\u011fruysa WordPress rewrite kurallar\u0131 \u00e7al\u0131\u015facakt\u0131r.<\/p>\n<h2 id=\"vps-wordpress-kurulumu-sonrasinda-hangi-guvenlik-ayarlari-yapilmali\">VPS WordPress kurulumu sonras\u0131nda hangi g\u00fcvenlik ayarlar\u0131 yap\u0131lmal\u0131?<\/h2>\n<p>Kurulum tamamlan\u0131nca i\u015f bitmez. WordPress \u00e7ekirde\u011fi, eklentiler, temalar ve i\u015fletim sistemi ayr\u0131 g\u00fcncelleme y\u00fczeyleridir. Kullan\u0131lmayan eklenti ve temalar\u0131 yaln\u0131zca devre d\u0131\u015f\u0131 b\u0131rakmak yerine kald\u0131rmak sald\u0131r\u0131 y\u00fczeyini azalt\u0131r.<\/p>\n<p>Y\u00f6netim hesab\u0131nda g\u00fc\u00e7l\u00fc ve benzersiz parola, iki a\u015famal\u0131 do\u011frulama ve do\u011fru e-posta adresi kullan\u0131n. XML-RPC&#8217;yi gerektiren bir mobil uygulama veya entegrasyon yoksa kapatmay\u0131 de\u011ferlendirin; bunu k\u00f6rlemesine yapmak yerine kulland\u0131\u011f\u0131n\u0131z \u00f6zellikleri test edin.<\/p>\n<p>Dosya d\u00fczenleyicisini kapatmak i\u00e7in <code>wp-config.php<\/code> i\u00e7ine ekleyebilirsiniz:<\/p>\n<pre><code>define('DISALLOW_FILE_EDIT', true);<\/code><\/pre>\n<p>Bu ayar, panel i\u00e7inden tema ve eklenti dosyalar\u0131n\u0131 de\u011fi\u015ftirmeyi engeller; dosya y\u00fcklemeyi veya g\u00fcncellemeyi tamamen kapatmaz. Y\u00f6netim panelini yaln\u0131zca belirli IP&#8217;lere a\u00e7mak m\u00fcmk\u00fcn olsa da mobil ve de\u011fi\u015fken ba\u011flant\u0131lar i\u00e7in operasyonel maliyeti hesaplay\u0131n.<\/p>\n<p>G\u00fcnl\u00fckleri izleyin. <code>journalctl -u nginx<\/code>, Nginx eri\u015fim g\u00fcnl\u00fc\u011f\u00fc ve PHP-FPM g\u00fcnl\u00fc\u011f\u00fc 502, 403 ve yava\u015f isteklerin kayna\u011f\u0131n\u0131 ay\u0131rmaya yard\u0131m eder. <a href=\"https:\/\/www.vps.tc\/blog\/tr\/502-bad-gateway-hatasi-nedir-nasil-cozulur\/\">502 Bad Gateway Hatas\u0131 Nedir ve Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr<\/a> yaz\u0131s\u0131nda da PHP-FPM ba\u011flant\u0131s\u0131 ve upstream hatalar\u0131 i\u00e7in ek kontrol noktalar\u0131 bulunur.<\/p>\n<p>Yedekleri VPS&#8217;in ayn\u0131 diskinde tutmay\u0131n. En az\u0131ndan veritaban\u0131 d\u00f6k\u00fcm\u00fc ve <code>wp-content<\/code> dizini ayr\u0131 bir hedefe kopyalanmal\u0131; geri y\u00fckleme provas\u0131 yap\u0131lmadan yedek tamamlanm\u0131\u015f say\u0131lmamal\u0131d\u0131r.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; G\u00fcncellemeleri uygulamadan \u00f6nce veritaban\u0131 ve dosya yede\u011fi al\u0131n, ard\u0131ndan bo\u015f bir test ortam\u0131nda geri d\u00f6n\u00fc\u015f\u00fc deneyin.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">Sahadan not<\/p>\n<p>Bir gece saat \u00fc\u00e7te disk dolu alarm\u0131 geldi. ncdu ile \/var alt\u0131nda ilerleyince uygulaman\u0131n log dosyas\u0131n\u0131n g\u00fcnlerdir d\u00f6nmedi\u011fini g\u00f6rd\u00fcm; logrotate yap\u0131land\u0131rmas\u0131na eksik rotate sat\u0131r\u0131n\u0131 ekleyip logrotate -f \/etc\/logrotate.conf ile test ettim. O olaydan sonra disk alarm\u0131n\u0131 yaln\u0131zca temizlemek yerine g\u00fcnl\u00fck d\u00f6nd\u00fcrme, saklama ve geri d\u00f6n\u00fc\u015f davran\u0131\u015f\u0131n\u0131 birlikte kontrol ediyorum.<\/p>\n<\/div>\n<h2 id=\"performans-icin-php-onbellek-ve-yedekleme-ayarlari\">Performans i\u00e7in PHP, \u00f6nbellek ve yedekleme ayarlar\u0131<\/h2>\n<p>WordPress performans\u0131nda ilk bak\u0131lacak yer her zaman daha b\u00fcy\u00fck VPS de\u011fildir. Gereksiz eklentiler, a\u011f\u0131r sorgular, b\u00fcy\u00fck g\u00f6rseller ve \u00f6nbelleksiz PHP istekleri kaynak t\u00fcketimini art\u0131r\u0131r. \u00d6nce <code>htop<\/code>, Nginx g\u00fcnl\u00fckleri ve veritaban\u0131 sorgu s\u00fcreleriyle darbo\u011faz\u0131 \u00f6l\u00e7\u00fcn.<\/p>\n<p>PHP-FPM havuzunda <code>pm.max_children<\/code> de\u011feri RAM&#8217;e g\u00f6re belirlenmelidir. Her PHP i\u015f\u00e7isinin t\u00fcketti\u011fi bellek eklenti ve uygulama y\u00fck\u00fcne g\u00f6re de\u011fi\u015fir; rastgele 50 i\u015f\u00e7i a\u00e7mak k\u00fc\u00e7\u00fck bir VPS&#8217;i k\u0131sa s\u00fcrede swap&#8217;e itebilir. Swap alan\u0131 i\u00e7in <a href=\"https:\/\/www.vps.tc\/blog\/tr\/vpste-swap-alani-olusturma-linux-bellek-yonetimi\/\">VPS&#8217;te Swap Alan\u0131 Olu\u015fturma ve Linux Bellek Y\u00f6netimi<\/a> rehberindeki s\u0131n\u0131rlar\u0131 ve izleme ad\u0131mlar\u0131n\u0131 kullanabilirsiniz.<\/p>\n<p>Medya dosyalar\u0131 i\u00e7in WebP veya AVIF d\u00f6n\u00fc\u015f\u00fcm\u00fc, taray\u0131c\u0131 \u00f6nbellek ba\u015fl\u0131klar\u0131 ve sayfa \u00f6nbelle\u011fi de\u011ferlendirilebilir. TTFB&#8217;yi milisaniye milisaniye tart\u0131\u015fmadan \u00f6nce sayfa \u00f6nbelle\u011finin istekleri ger\u00e7ekten \u00f6nbellekten kar\u015f\u0131lay\u0131p kar\u015f\u0131lamad\u0131\u011f\u0131n\u0131 \u00f6l\u00e7\u00fcn.<\/p>\n<p>Basit bir veritaban\u0131 yede\u011fi:<\/p>\n<pre><code>sudo install -d -m 700 \/var\/backups\/wordpress\nsudo mariadb-dump --single-transaction wp_site | \\\n  gzip | sudo tee \/var\/backups\/wordpress\/wp_site-$(date +%F).sql.gz &gt; \/dev\/null\nsudo tar -czf \/var\/backups\/wordpress\/wp-content-$(date +%F).tar.gz \\\n  -C \/var\/www\/example.com wp-content<\/code><\/pre>\n<p>Bu dosyalar\u0131 ayn\u0131 VPS&#8217;te b\u0131rakmak yaln\u0131zca h\u0131zl\u0131 bir geri d\u00f6n\u00fc\u015f noktas\u0131 sa\u011flar; disk ar\u0131zas\u0131na kar\u015f\u0131 koruma sa\u011flamaz. Rsync ile uzak hedefe kopyalama ve Borg ile s\u00fcr\u00fcml\u00fc, \u015fifreli yedekleme daha sa\u011flam bir modeldir. Ayda bir yedek geri d\u00f6n\u00fc\u015f provas\u0131 planlay\u0131n.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Yedek dosyas\u0131n\u0131n olu\u015fturuldu\u011funu de\u011fil, yeni ve bo\u015f bir WordPress kurulumunda a\u00e7\u0131labildi\u011fini do\u011frulay\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">\u00d6rnek<\/p>\n<p>K\u00fc\u00e7\u00fck bir blogda sayfa \u00f6nbelle\u011fi a\u00e7\u0131kken 1 GB RAM yeterli g\u00f6r\u00fcnebilir; WooCommerce, g\u00f6rsel i\u015fleme ve yo\u011fun y\u00f6netici trafi\u011fi eklendi\u011finde PHP-FPM i\u015f\u00e7i say\u0131s\u0131 RAM&#039;i h\u0131zla t\u00fcketebilir. \u00d6nce htop ve g\u00fcnl\u00fcklerle \u00f6l\u00e7\u00fcn, sonra kaynak art\u0131r\u0131n.<\/p>\n<\/div>\n<h2 id=\"kurulum-sorunlarini-nasil-teshis-edebilirsiniz\">Kurulum sorunlar\u0131n\u0131 nas\u0131l te\u015fhis edebilirsiniz?<\/h2>\n<p>Sayfa a\u00e7\u0131lm\u0131yorsa hemen VPS&#8217;i yeniden ba\u015flatmay\u0131n. \u00d6nce sorunun DNS, a\u011f, Nginx, PHP-FPM, veritaban\u0131 veya WordPress katman\u0131nda oldu\u011funu ay\u0131r\u0131n.<\/p>\n<ul>\n<li><code>dig +short example.com<\/code> ile DNS adresini kontrol edin.<\/li>\n<li><code>curl -I https:\/\/example.com<\/code> ile HTTP durum kodunu ve y\u00f6nlendirmeyi g\u00f6r\u00fcn.<\/li>\n<li><code>sudo nginx -t<\/code> ile yap\u0131land\u0131rma s\u00f6zdizimini test edin.<\/li>\n<li><code>systemctl status php8.3-fpm nginx mariadb<\/code> ile servisleri inceleyin.<\/li>\n<li><code>journalctl -u nginx -n 100 --no-pager<\/code> ve PHP-FPM g\u00fcnl\u00fcklerini okuyun.<\/li>\n<li><code>sudo tail -f \/var\/log\/nginx\/error.log<\/code> ile yeni iste\u011fin hata kayd\u0131n\u0131 izleyin.<\/li>\n<\/ul>\n<p>403 hatas\u0131 \u00e7o\u011funlukla izin veya Nginx kural\u0131, 404 hatas\u0131 yanl\u0131\u015f <code>try_files<\/code> ya da kal\u0131c\u0131 ba\u011flant\u0131, 502 hatas\u0131 ise PHP-FPM soketi veya servis sorunudur. Veritaban\u0131 ba\u011flant\u0131 hatas\u0131nda <code>wp-config.php<\/code> de\u011ferlerini ve MariaDB kullan\u0131c\u0131 yetkilerini kontrol edin.<\/p>\n<p>WordPress kurulumu s\u0131ras\u0131nda yaln\u0131zca taray\u0131c\u0131daki hata mesaj\u0131na g\u00fcvenmeyin. Ayn\u0131 iste\u011fi <code>curl<\/code> ile tekrarlamak ve ilgili log sat\u0131r\u0131n\u0131 ayn\u0131 zaman aral\u0131\u011f\u0131nda bulmak, tahminle yap\u0131lan restart&#8217;lardan \u00e7ok daha h\u0131zl\u0131d\u0131r.<\/p>\n<h2 id=\"kuruluma-baslamadan-once-sunlari-kontrol-edin\">Kuruluma Ba\u015flamadan \u00d6nce \u015eunlar\u0131 Kontrol Edin<\/h2>\n<ul class=\"aiw-checklist\">\n<li>VPS i\u015fletim sistemini g\u00fcncelleyin ve ayr\u0131 bir sudo kullan\u0131c\u0131s\u0131 olu\u015fturun.<\/li>\n<li>A ve gerekiyorsa AAAA DNS kay\u0131tlar\u0131n\u0131 ger\u00e7ek sunucu adresine y\u00f6nlendirin.<\/li>\n<li>SSH eri\u015fimini ikinci bir terminalden test edin.<\/li>\n<li>80 ve 443 portlar\u0131n\u0131 a\u00e7\u0131p gereksiz servisleri kapat\u0131n.<\/li>\n<li>PHP-FPM soket yolunu ve gerekli PHP mod\u00fcllerini do\u011frulay\u0131n.<\/li>\n<li>WordPress i\u00e7in ayr\u0131 MariaDB veritaban\u0131 ve kullan\u0131c\u0131 olu\u015fturun.<\/li>\n<li>HTTPS, uzak yedekleme ve geri y\u00fckleme provas\u0131n\u0131 tamamlay\u0131n.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>Kurulumu tamamlad\u0131ktan sonra bir test yaz\u0131s\u0131 yay\u0131mlay\u0131p kal\u0131c\u0131 ba\u011flant\u0131y\u0131, g\u00f6rsel y\u00fcklemeyi, HTTPS y\u00f6nlendirmesini ve yedek geri d\u00f6n\u00fc\u015f\u00fcn\u00fc ayn\u0131 g\u00fcn kontrol edin. Sunucu \u00e7al\u0131\u015f\u0131rken de\u011fil, sorun \u00e7\u0131kmadan \u00f6nce \u00f6l\u00e7\u00fcm ve bak\u0131m rutini olu\u015fturmak daha az yorucudur.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/tr\/vps\">VPS paketlerini inceleyin<\/a><\/p>\n<\/div>\n<h2 id=\"sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/h2>\n<div class=\"aiw-faq\">\n<details class=\"aiw-faq-item\" open>\n<summary>VPS&#039;te WordPress kurmak i\u00e7in hangi i\u015fletim sistemi kullan\u0131lmal\u0131?<\/summary>\n<p>Ubuntu 24.04 LTS veya Debian stable gibi uzun s\u00fcre desteklenen bir da\u011f\u0131t\u0131m tercih edilebilir. \u00d6rnek kurulum Ubuntu 24.04 \u00fczerinde Nginx, PHP-FPM ve MariaDB kullan\u0131r. Da\u011f\u0131t\u0131m se\u00e7erken yaln\u0131zca s\u00fcr\u00fcme de\u011fil, g\u00fcvenlik g\u00fcncellemelerinin d\u00fczenine, PHP paketlerinin g\u00fcncelli\u011fine ve kulland\u0131\u011f\u0131n\u0131z ara\u00e7lar\u0131n dok\u00fcmantasyonuna da bak\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>WordPress i\u00e7in VPS&#039;te ne kadar RAM gerekir?<\/summary>\n<p>K\u00fc\u00e7\u00fck ve d\u00fc\u015f\u00fck trafikli bir WordPress sitesi i\u00e7in 1 GB RAM \u00e7al\u0131\u015fabilir; i\u015fletim sistemi, PHP-FPM, MariaDB, \u00f6nbellek ve eklentiler ayn\u0131 belle\u011fi payla\u015f\u0131r. WooCommerce, g\u00f6rsel i\u015fleme veya yo\u011fun trafik varsa 2 GB ve \u00fczeri daha rahat bir ba\u015flang\u0131\u00e7 sa\u011flar. Kesin karar\u0131 tahminle de\u011fil, swap kullan\u0131m\u0131, PHP-FPM s\u00fcre\u00e7leri ve y\u00fck \u00f6l\u00e7\u00fcmleriyle verin.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>VPS WordPress kurulumu i\u00e7in Nginx mi Apache mi kullan\u0131lmal\u0131?<\/summary>\n<p>\u0130kisi de WordPress \u00e7al\u0131\u015ft\u0131rabilir. Nginx d\u00fc\u015f\u00fck bellek t\u00fcketimi ve ters proxy yap\u0131lar\u0131na uygunlu\u011fu nedeniyle VPS&#039;lerde s\u0131k tercih edilir; PHP kodunu do\u011frudan de\u011fil PHP-FPM \u00fczerinden \u00e7al\u0131\u015ft\u0131r\u0131r. Apache ise .htaccess uyumlulu\u011fu ve daha geni\u015f panel deste\u011fiyle baz\u0131 kurulumlar\u0131 kolayla\u015ft\u0131rabilir. Se\u00e7im, mevcut y\u00f6netim al\u0131\u015fkanl\u0131\u011f\u0131n\u0131za ve uygulama gereksinimlerinize ba\u011fl\u0131d\u0131r.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>WordPress VPS \u00fczerinde HTTPS olmadan \u00e7al\u0131\u015f\u0131r m\u0131?<\/summary>\n<p>Teknik olarak HTTP ile a\u00e7\u0131labilir, ancak \u00fcretim sitesinde \u00f6nerilmez. HTTPS; giri\u015f parolalar\u0131n\u0131, y\u00f6netici oturumlar\u0131n\u0131 ve formlar\u0131 a\u011f \u00fczerinde \u015fifreler. Let&#039;s Encrypt sertifikas\u0131 Certbot ile \u00fccretsiz al\u0131nabilir. Sertifika kurulduktan sonra HTTP&#039;den HTTPS&#039;e y\u00f6nlendirmeyi, WordPress&#039;in site adreslerini ve otomatik yenileme denemesini birlikte test edin.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>WordPress dosya izinleri VPS&#039;te nas\u0131l olmal\u0131?<\/summary>\n<p>Genel ba\u015flang\u0131\u00e7 noktas\u0131 dizinler i\u00e7in 755, dosyalar i\u00e7in 644 ve dosya sahibi olarak web sunucusu kullan\u0131c\u0131s\u0131d\u0131r; ancak her kurulumun g\u00fcncelleme ve y\u00fckleme modeli farkl\u0131d\u0131r. T\u00fcm siteye 777 vermeyin. Yazma ihtiyac\u0131 olan dizinleri belirleyin, PHP-FPM kullan\u0131c\u0131s\u0131n\u0131 ve Nginx yap\u0131land\u0131rmas\u0131n\u0131 kontrol edin. \u0130zin sorununu geni\u015f yetki vererek gizlemek g\u00fcvenlik a\u00e7\u0131\u011f\u0131 olu\u015fturabilir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>VPS&#039;teki WordPress nas\u0131l yedeklenir?<\/summary>\n<p>En az\u0131ndan MariaDB veritaban\u0131 ve WordPress&#039;in wp-content dizini yedeklenmelidir; tema, eklenti, medya ve y\u00fcklenen i\u00e7eriklerin \u00e7o\u011fu burada bulunur. Yede\u011fi ayn\u0131 diskte b\u0131rakmak donan\u0131m veya disk ar\u0131zas\u0131na kar\u015f\u0131 koruma sa\u011flamaz. Uzak bir hedef kullan\u0131n, yedek dosyas\u0131n\u0131 do\u011frulay\u0131n ve bo\u015f bir test ortam\u0131nda geri y\u00fckleme provas\u0131 yap\u0131n.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"kaynaklar\">Kaynaklar<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/wordpress.org\/documentation\/article\/requirements\/\" target=\"_blank\" rel=\"noopener\">WordPress &#8211; Requirements<\/a> \u2014 wordpress.org<\/li>\n<li><a href=\"https:\/\/nginx.org\/en\/docs\/\" target=\"_blank\" rel=\"noopener\">NGINX Documentation<\/a> \u2014 nginx.org<\/li>\n<li><a href=\"https:\/\/www.php.net\/manual\/en\/install.unix.debian.php\" target=\"_blank\" rel=\"noopener\">PHP Manual &#8211; Debian Installation<\/a> \u2014 php.net<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Ubuntu tabanl\u0131 bir VPS \u00fczerinde Nginx, PHP-FPM, MariaDB ve Let&#8217;s Encrypt kullanarak WordPress&#8217;i g\u00fcvenli bi\u00e7imde kurma ad\u0131mlar\u0131.<\/p>\n","protected":false},"author":2,"featured_media":773,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[666],"tags":[],"class_list":["post-775","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cms"],"lang":"tr","translations":{"tr":775,"en":776},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/775","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=775"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/775\/revisions"}],"predecessor-version":[{"id":777,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/775\/revisions\/777"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/773"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=775"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=775"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=775"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}