{"id":2610,"date":"2026-10-31T16:21:48","date_gmt":"2026-10-31T13:21:48","guid":{"rendered":"https:\/\/www.fibacloud.com\/community\/tutorials\/?p=2610"},"modified":"2026-10-31T16:21:48","modified_gmt":"2026-10-31T13:21:48","slug":"n8n-kurulumu-ubuntu-docker","status":"publish","type":"post","link":"https:\/\/www.fibacloud.com\/community\/tutorials\/n8n-kurulumu-ubuntu-docker\/","title":{"rendered":"n8n Kurulumu: Ubuntu VPS, Docker Compose ve HTTPS"},"content":{"rendered":"<p>n8n\u2019i kendi Ubuntu VPS\u2019inize kurarak i\u015f ak\u0131\u015flar\u0131n\u0131z\u0131 kendi alan ad\u0131n\u0131zda \u00e7al\u0131\u015ft\u0131rabilirsiniz. Bu rehber, Docker Compose ile n8n, PostgreSQL, Caddy ve harici task runner kurulumunu birlikte ele al\u0131r. Sonunda HTTPS \u00fczerinden bir istek g\u00f6nderecek, kimlik do\u011frulamas\u0131n\u0131 s\u0131nayacak ve verilerinizin yeniden ba\u015flatma ile yedekten d\u00f6n\u00fc\u015f s\u0131ras\u0131nda korundu\u011funu kontrol edeceksiniz.<\/p>\n<p>Bu kurulum, sunucuyu ve g\u00fcncellemeleri kendisi y\u00f6netmek isteyen kullan\u0131c\u0131lar i\u00e7indir. n8n\u2019in Community s\u00fcr\u00fcm\u00fcyle kendi i\u015f s\u00fcre\u00e7lerinizi otomatikle\u015ftirebilirsiniz; sunucu, alan ad\u0131 ve kullanaca\u011f\u0131n\u0131z d\u0131\u015f servislerin \u00fccretleri ayr\u0131 kalemlerdir. n8n\u2019i m\u00fc\u015fterilere eri\u015filebilir bir hizmet olarak sunmak i\u00e7in lisans ko\u015fullar\u0131n\u0131 ayr\u0131ca de\u011ferlendirmek gerekir.<\/p>\n<h2 id=\"test-ortami\">Test ortam\u0131 ve rehberin kapsam\u0131<\/h2>\n<p>Bu kurulum 31 Ekim 2026\u2019da Ubuntu \u00fczerinde \u00e7al\u0131\u015ft\u0131r\u0131ld\u0131. Rehberdeki k\u00fc\u00e7\u00fck ak\u0131\u015f, kimlik do\u011frulamal\u0131 bir POST iste\u011fini al\u0131r, Code d\u00fc\u011f\u00fcm\u00fcnde 41\u2019e bir ekler ve JSON yan\u0131t\u0131 d\u00f6nd\u00fcr\u00fcr.<\/p>\n<table>\n<thead>\n<tr>\n<th>\u00d6\u011fe<\/th>\n<th>Testte kullan\u0131lan de\u011fer<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>\u0130\u015fletim sistemi<\/td>\n<td>Ubuntu 24.04.5 LTS, amd64<\/td>\n<\/tr>\n<tr>\n<td>Sunucu<\/td>\n<td>1 vCPU, yakla\u015f\u0131k 1967 MiB RAM, 4 GiB swap<\/td>\n<\/tr>\n<tr>\n<td>Docker \/ Compose<\/td>\n<td>29.9.2 \/ 5.6.1<\/td>\n<\/tr>\n<tr>\n<td>\u00c7al\u0131\u015ft\u0131r\u0131lan imajlar<\/td>\n<td>n8n ve runners 2.45.7, PostgreSQL 17.11, Caddy 2.11.7; s\u00fcr\u00fcm ve digest ile sabitlendi, indirilen digest\u2019ler kontrol edildi.<\/td>\n<\/tr>\n<tr>\n<td>D\u0131\u015f ba\u011flant\u0131<\/td>\n<td>G\u00fcvenilir Let\u2019s Encrypt sertifikas\u0131yla TLS 1.3; ilk kurulum IP kural\u0131nda izin verilmeyen adrese HTTP 403. 5432, 5678, 5679 ve 5680 portlar\u0131na d\u0131\u015far\u0131dan eri\u015filemedi.<\/td>\n<\/tr>\n<tr>\n<td>\u0130\u015flev ve kal\u0131c\u0131l\u0131k<\/td>\n<td>Ger\u00e7ek edit\u00f6rde \u00fc\u00e7 d\u00fc\u011f\u00fcml\u00fc ak\u0131\u015f, \u00fcretim webhook\u2019unda 403\/403\/200 kontrolleri, n8n ve runner konteynerleri yenilendikten sonra ayn\u0131 sonu\u00e7 ve ayr\u0131 proje\/volume\u2019lara geri y\u00fcklenen kimlik bilgisi do\u011fruland\u0131.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Harici runner ayr\u0131 konteynerde UID 1000 ve salt okunur k\u00f6k dosya sistemiyle \u00e7al\u0131\u015ft\u0131. Geri y\u00fcklenen \u00f6rnekte <code>external<\/code> modu ve ba\u015far\u0131l\u0131 Code kontrol\u00fcyle ayn\u0131 zamana denk gelen JavaScript runner s\u00fcreci g\u00fcnl\u00fcklerden do\u011fruland\u0131.<\/p>\n<p>As\u0131l kurulumun oturum ve webhook kontrolleri do\u011frulanan HTTPS \u00fczerinden yap\u0131ld\u0131. Geri y\u00fcklenen kopyan\u0131n host portu a\u00e7\u0131lmad\u0131; onun webhook\u2019u ve kay\u0131tl\u0131 hesapla oturum a\u00e7ma iste\u011fi konteyner i\u00e7indeki HTTP ba\u011flant\u0131s\u0131yla s\u0131nand\u0131. Bu ikinci test, yeni bir genel HTTPS u\u00e7 noktas\u0131n\u0131n do\u011frulamas\u0131 de\u011fildir. Python, ek topluluk d\u00fc\u011f\u00fcmleri ve yo\u011fun paralel y\u00fck bu denemeye dahil de\u011fildi.<\/p>\n<p>\u00d6rneklerde <code>n8n.example.com<\/code> alan ad\u0131, <code>203.0.113.10\/32<\/code> y\u00f6netici IP adresi ve <code>\/opt\/n8n<\/code> \u00e7al\u0131\u015fma dizini kullan\u0131l\u0131yor. Alan ad\u0131n\u0131 ve IP adresini kendi de\u011ferlerinizle de\u011fi\u015ftirin. Ayr\u0131nt\u0131l\u0131 \u00f6l\u00e7\u00fcm yap\u0131lmadan RAM miktar\u0131ndan i\u015f ak\u0131\u015f\u0131 veya e\u015f zamanl\u0131 kullan\u0131c\u0131 kapasitesi \u00e7\u0131kar\u0131lamaz; b\u00fcy\u00fck dosyalar ve ayn\u0131 anda \u00e7al\u0131\u015fan i\u015fler kaynak ihtiyac\u0131n\u0131 de\u011fi\u015ftirir.<\/p>\n<p>Bu rehber n8n\u2019in temel i\u015f ak\u0131\u015flar\u0131n\u0131 ve Code d\u00fc\u011f\u00fcm\u00fc i\u00e7in harici runner\u2019\u0131 kapsar. Assistant \u00f6zelli\u011fi uygulamada g\u00f6r\u00fcnebilir; burada Assistant i\u00e7in model ba\u011flant\u0131s\u0131 veya sandbox yap\u0131land\u0131r\u0131lmaz.<\/p>\n<h2 id=\"gereksinimler\">Ba\u015flamadan \u00f6nce gerekenler<\/h2>\n<ul>\n<li>SSH ve <code>sudo<\/code> eri\u015fimine sahip Ubuntu sunucu. \u0130lk ba\u011flant\u0131 i\u00e7in <a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/ssh-ile-uzak-sunucuya-baglanti-nasil-yapilir\/\">SSH ile uzak sunucuya ba\u011flant\u0131 rehberini<\/a> kullanabilirsiniz.<\/li>\n<li>Docker Engine ve Compose eklentisi. Kurulu de\u011filse \u00f6nce <a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/docker-ile-uygulama-nasil-dagitilir\/\">Docker kurulum ve uygulama da\u011f\u0131t\u0131m rehberini<\/a> tamamlay\u0131n.<\/li>\n<li>Sunucunun genel IP adresine y\u00f6nlenen bir alt alan ad\u0131. A kayd\u0131n\u0131 kontrol edin; AAAA kayd\u0131 varsa do\u011fru IPv6 adresine gitmelidir.<\/li>\n<li>Sunucuya ula\u015fan 80\/TCP ve 443\/TCP portlar\u0131. 443\/UDP, Caddy\u2019nin HTTP\/3 deste\u011fi i\u00e7indir. Bulut g\u00fcvenlik duvar\u0131n\u0131 ve sunucudaki kurallar\u0131 birlikte kontrol edin.<\/li>\n<li>\u0130lk y\u00f6netici hesab\u0131n\u0131 a\u00e7aca\u011f\u0131n\u0131z bilgisayar\u0131n genel IP adresi. \u0130lk kurulum ekran\u0131n\u0131 bu adrese s\u0131n\u0131rlayaca\u011f\u0131z.<\/li>\n<\/ul>\n<div class=\"fc-code-example\">\n<pre><code>docker --version\ndocker compose version\nsudo ss -ltnup<\/code><\/pre>\n<\/div>\n<p><code>ss<\/code> \u00e7\u0131kt\u0131s\u0131nda 80 veya 443 ba\u015fka bir servis taraf\u0131ndan kullan\u0131l\u0131yorsa devam etmeden port payla\u015f\u0131m\u0131n\u0131 \u00e7\u00f6z\u00fcn. Plesk, Apache veya Nginx \u00e7al\u0131\u015fan bir sunucuda mevcut web servisini rastgele durdurmak siteleri kesintiye u\u011frat\u0131r. Bu rehber, Caddy\u2019nin bu portlar\u0131 kullanabildi\u011fi ayr\u0131 bir uygulama sunucusunu esas al\u0131r; panelinizin y\u00f6netti\u011fi reverse proxy\u2019ye ekleme ayr\u0131 bir yap\u0131land\u0131rmad\u0131r.<\/p>\n<h2 id=\"mimari\">Hangi servis ne yapacak?<\/h2>\n<table>\n<thead>\n<tr>\n<th>Servis<\/th>\n<th>G\u00f6revi<\/th>\n<th>Veri ve eri\u015fim<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Caddy<\/td>\n<td>HTTPS, sertifika yenileme ve n8n\u2019e istek iletme<\/td>\n<td>Yaln\u0131zca 80\/443 d\u0131\u015far\u0131 a\u00e7\u0131l\u0131r; sertifikalar kal\u0131c\u0131 volume\u2019da tutulur.<\/td>\n<\/tr>\n<tr>\n<td>n8n<\/td>\n<td>Edit\u00f6r, webhook ve i\u015f ak\u0131\u015flar\u0131n\u0131n y\u00f6netimi<\/td>\n<td>5678 konteyner a\u011f\u0131nda kal\u0131r; <code>.n8n<\/code> dizini kal\u0131c\u0131d\u0131r.<\/td>\n<\/tr>\n<tr>\n<td>PostgreSQL<\/td>\n<td>\u0130\u015f ak\u0131\u015flar\u0131, kullan\u0131c\u0131lar ve kimlik bilgileri i\u00e7in veritaban\u0131<\/td>\n<td>5432 d\u0131\u015far\u0131 yay\u0131nlanmaz; n8n ayr\u0131 bir veritaban\u0131 rol\u00fcyle ba\u011flan\u0131r.<\/td>\n<\/tr>\n<tr>\n<td>Task runner<\/td>\n<td>Code d\u00fc\u011f\u00fcm\u00fcndeki kodu ayr\u0131 bir konteynerde \u00e7al\u0131\u015ft\u0131rma<\/td>\n<td>5679 \u00fczerindeki n8n broker\u2019\u0131na \u00f6zel anahtarla ba\u011flan\u0131r; veritaban\u0131 parolas\u0131 ve n8n \u015fifreleme anahtar\u0131n\u0131 almaz.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Harici runner, n8n\u2019in \u00f6nerdi\u011fi kod \u00e7al\u0131\u015ft\u0131rma d\u00fczenidir. Webhook ve Edit Fields gibi d\u00fc\u011f\u00fcmler kendi ba\u015flar\u0131na Code runner\u2019\u0131na i\u015f g\u00f6ndermez; yine de Code \u00f6zelli\u011fi kullan\u0131labilsin diye bu kuruluma runner dahil edilmi\u015ftir. n8n ve runner\u2019\u0131n uygulama s\u00fcr\u00fcm\u00fc ayn\u0131 olmal\u0131; iki farkl\u0131 imaj\u0131n digest de\u011ferleri ise do\u011fal olarak farkl\u0131d\u0131r. <a href=\"https:\/\/docs.n8n.io\/deploy\/host-n8n\/configure-n8n\/set-up-task-runners.md\" rel=\"nofollow noopener\" target=\"_blank\">Resm\u00ee task runner a\u00e7\u0131klamas\u0131<\/a> bu ayr\u0131m\u0131 anlat\u0131r.<\/p>\n<h2 id=\"dosyalar\">Kurulum dizinini ve gizli de\u011ferleri haz\u0131rlay\u0131n<\/h2>\n<p>Yap\u0131land\u0131rmalar\u0131 a\u015fa\u011f\u0131daki ad\u0131mlarla olu\u015fturabilir veya <a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/n8n-compose.zip\">Compose dosya paketini indirebilirsiniz<\/a>. Paket ger\u00e7ek parola i\u00e7ermez; alan ad\u0131, y\u00f6netici IP\u2019si ve gizli de\u011ferleri kendi kurulumunuz i\u00e7in haz\u0131rlay\u0131n. \u00d6rnek ak\u0131\u015f\u0131 yeniden kurmak i\u00e7in <a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/workflow.json\">webhook i\u015f ak\u0131\u015f\u0131 JSON dosyas\u0131<\/a> da kullan\u0131labilir; Header Auth kimlik bilgisini kendi n8n hesab\u0131n\u0131zda olu\u015fturman\u0131z gerekir.<\/p>\n<p>A\u015fa\u011f\u0131daki ad\u0131mlar yeni bir <code>\/opt\/n8n<\/code> dizini i\u00e7indir. Ayn\u0131 yolda mevcut kurulumunuz varsa dosyalar\u0131n \u00fczerine yazmay\u0131n. Komutlar bu noktadan itibaren y\u00f6netici kabu\u011funda \u00e7al\u0131\u015f\u0131r; dizin ve gizli dosyalar di\u011fer kullan\u0131c\u0131lara a\u00e7\u0131lmaz.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>sudo -i\ninstall -d -m 700 \/opt\/n8n\ncd \/opt\/n8n\numask 077<\/code><\/pre>\n<\/div>\n<p><code>.env<\/code> dosyas\u0131n\u0131 olu\u015fturun. <code>N8N_HOST<\/code> ve <code>BOOTSTRAP_ALLOWED_IP<\/code> de\u011ferlerini kendi alan ad\u0131n\u0131z ve y\u00f6netici IP\u2019nizle de\u011fi\u015ftirin. \u00d6rnek IP\u2019yi b\u0131rak\u0131rsan\u0131z ilk kurulum ekran\u0131na eri\u015femezsiniz.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cat &gt; .env &lt;&lt;&#x27;ENV&#x27;\nCOMPOSE_PROJECT_NAME=n8n\nN8N_HOST=n8n.example.com\nBOOTSTRAP_ALLOWED_IP=203.0.113.10\/32\nGENERIC_TIMEZONE=Europe\/Istanbul\n\nPOSTGRES_ADMIN_PASSWORD=REPLACE_WITH_SEPARATE_RANDOM_64_HEX_CHARACTERS\nN8N_DB_PASSWORD=REPLACE_WITH_SEPARATE_RANDOM_64_HEX_CHARACTERS\nN8N_ENCRYPTION_KEY=REPLACE_WITH_SEPARATE_RANDOM_64_HEX_CHARACTERS_AND_KEEP_FOR_RESTORE\nN8N_RUNNERS_AUTH_TOKEN=REPLACE_WITH_SEPARATE_RANDOM_64_HEX_CHARACTERS\n\nN8N_IMAGE=docker.io\/n8nio\/n8n:2.45.7@sha256:9a8d8dcea75667496695d7810d7e1fe018a65efb36cc499d347f3931b3957b5d\nRUNNERS_IMAGE=docker.io\/n8nio\/runners:2.45.7@sha256:2f07088829b6a1df2b6a84746bb8b32c1eaef270315fb5466aa01b1045e9b300\nPOSTGRES_IMAGE=docker.io\/library\/postgres:17.11-bookworm@sha256:839fbb5a4942a7758dd93e18b42ea5649807491a0545b5eeeb8f0b8bb11857a5\nCADDY_IMAGE=docker.io\/library\/caddy:2.11.7-alpine@sha256:e70b164da81ef698b3ad19af799ea6086ce6d9e48ed4079eb9fe26f6fbf14ee5\nENV<\/code><\/pre>\n<\/div>\n<p>\u015eimdi d\u00f6rt farkl\u0131 rastgele gizli de\u011fer \u00fcretin. Bu komut yaln\u0131zca <code>REPLACE_WITH_<\/code> ile ba\u015flayan alanlar\u0131 de\u011fi\u015ftirir ve de\u011ferleri ekrana yazmaz. \u00d6nceden \u00fcretilmi\u015f bir \u015fifreleme anahtar\u0131n\u0131 tekrar \u00fcretmez.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>python3 - &lt;&lt;&#x27;PY&#x27;\nfrom pathlib import Path\nfrom secrets import token_hex\nimport re\n\npath = Path(&quot;.env&quot;)\ntext = path.read_text()\nkeys = (\n    &quot;POSTGRES_ADMIN_PASSWORD&quot;,\n    &quot;N8N_DB_PASSWORD&quot;,\n    &quot;N8N_ENCRYPTION_KEY&quot;,\n    &quot;N8N_RUNNERS_AUTH_TOKEN&quot;,\n)\nfor key in keys:\n    text = re.sub(\n        rf&quot;^{key}=REPLACE_WITH_[^\\n]*$&quot;,\n        lambda match: f&quot;{key}={token_hex(32)}&quot;,\n        text,\n        flags=re.MULTILINE,\n    )\nif &quot;REPLACE_WITH_&quot; in text:\n    raise SystemExit(&quot;Unreplaced placeholder in .env&quot;)\npath.write_text(text)\npath.chmod(0o600)\nPY<\/code><\/pre>\n<\/div>\n<p><code>N8N_ENCRYPTION_KEY<\/code>, n8n\u2019de saklanan kimlik bilgilerinin \u00e7\u00f6z\u00fclebilmesi i\u00e7in gereklidir. Veritaban\u0131 yede\u011finin yan\u0131nda bu anahtar\u0131 da koruyun. Sunucuya yeniden kurulum yapmak, mevcut veritaban\u0131n\u0131 yeni bir anahtarla a\u00e7abilece\u011finiz anlam\u0131na gelmez. Ger\u00e7ek <code>.env<\/code> dosyas\u0131n\u0131 Git deposuna, destek mesaj\u0131na veya ekran g\u00f6r\u00fcnt\u00fcs\u00fcne eklemeyin.<\/p>\n<h2 id=\"compose\">Docker Compose ve PostgreSQL yap\u0131land\u0131rmas\u0131<\/h2>\n<p>A\u015fa\u011f\u0131daki dosya servisleri, sa\u011fl\u0131k kontrollerini ve kal\u0131c\u0131 volume\u2019lar\u0131 tan\u0131mlar. \u0130majlar s\u00fcr\u00fcm ve digest ile sabitlenmi\u015ftir. B\u00f6ylece yeniden olu\u015fturma s\u0131ras\u0131nda farkl\u0131 bir imaja istemeden ge\u00e7ilmez; g\u00fcncellemeyi ayr\u0131ca planlars\u0131n\u0131z.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cat &gt; compose.yml &lt;&lt;&#x27;YAML&#x27;\nservices:\n  postgres:\n    image: ${POSTGRES_IMAGE:?Set POSTGRES_IMAGE in .env}\n    restart: unless-stopped\n    environment:\n      POSTGRES_USER: postgres\n      POSTGRES_DB: n8n\n      POSTGRES_PASSWORD: ${POSTGRES_ADMIN_PASSWORD:?Generate POSTGRES_ADMIN_PASSWORD}\n      N8N_DB_PASSWORD: ${N8N_DB_PASSWORD:?Generate N8N_DB_PASSWORD}\n    volumes:\n      - postgres_data:\/var\/lib\/postgresql\/data\n      - .\/initdb.sh:\/docker-entrypoint-initdb.d\/10-n8n.sh:ro\n    networks:\n      - database\n    healthcheck:\n      test: [&quot;CMD&quot;, &quot;pg_isready&quot;, &quot;-h&quot;, &quot;127.0.0.1&quot;, &quot;-U&quot;, &quot;postgres&quot;, &quot;-d&quot;, &quot;n8n&quot;]\n      interval: 10s\n      timeout: 5s\n      retries: 12\n      start_period: 30s\n    logging:\n      driver: json-file\n      options:\n        max-size: &quot;10m&quot;\n        max-file: &quot;3&quot;\n\n  n8n:\n    image: ${N8N_IMAGE:?Set N8N_IMAGE in .env}\n    restart: unless-stopped\n    depends_on:\n      postgres:\n        condition: service_healthy\n    environment:\n      DB_TYPE: postgresdb\n      DB_POSTGRESDB_HOST: postgres\n      DB_POSTGRESDB_PORT: &quot;5432&quot;\n      DB_POSTGRESDB_DATABASE: n8n\n      DB_POSTGRESDB_USER: n8n_app\n      DB_POSTGRESDB_PASSWORD: ${N8N_DB_PASSWORD:?Generate N8N_DB_PASSWORD}\n      N8N_ENCRYPTION_KEY: ${N8N_ENCRYPTION_KEY:?Generate and preserve N8N_ENCRYPTION_KEY}\n      N8N_HOST: ${N8N_HOST:?Set the DNS hostname}\n      N8N_PORT: &quot;5678&quot;\n      N8N_LISTEN_ADDRESS: &quot;0.0.0.0&quot;\n      N8N_PROTOCOL: https\n      N8N_EDITOR_BASE_URL: https:\/\/${N8N_HOST:?Set the DNS hostname}\/\n      N8N_WEBHOOK_URL: https:\/\/${N8N_HOST:?Set the DNS hostname}\/\n      N8N_PROXY_HOPS: &quot;1&quot;\n      GENERIC_TIMEZONE: ${GENERIC_TIMEZONE:-Europe\/Istanbul}\n      TZ: ${GENERIC_TIMEZONE:-Europe\/Istanbul}\n      N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS: &quot;true&quot;\n      N8N_BLOCK_ENV_ACCESS_IN_NODE: &quot;true&quot;\n      N8N_AI_ENABLED: &quot;false&quot;\n      N8N_RUNNERS_MODE: external\n      N8N_RUNNERS_BROKER_LISTEN_ADDRESS: &quot;0.0.0.0&quot;\n      N8N_RUNNERS_AUTH_TOKEN: ${N8N_RUNNERS_AUTH_TOKEN:?Generate N8N_RUNNERS_AUTH_TOKEN}\n      EXECUTIONS_DATA_PRUNE: &quot;true&quot;\n      EXECUTIONS_DATA_MAX_AGE: &quot;168&quot;\n    volumes:\n      - n8n_data:\/home\/node\/.n8n\n    networks:\n      - edge\n      - database\n      - runner\n    healthcheck:\n      test:\n        - CMD\n        - node\n        - -e\n        - &quot;fetch(&#x27;http:\/\/127.0.0.1:5678\/healthz\/readiness&#x27;, {signal: AbortSignal.timeout(4000)}).then(r =&gt; process.exit(r.ok ? 0 : 1)).catch(() =&gt; process.exit(1))&quot;\n      interval: 15s\n      timeout: 5s\n      retries: 12\n      start_period: 120s\n    stop_grace_period: 60s\n    logging:\n      driver: json-file\n      options:\n        max-size: &quot;10m&quot;\n        max-file: &quot;3&quot;\n\n  task-runners:\n    image: ${RUNNERS_IMAGE:?Set the runner image matching the n8n version}\n    restart: unless-stopped\n    depends_on:\n      n8n:\n        condition: service_healthy\n    environment:\n      N8N_RUNNERS_TASK_BROKER_URI: http:\/\/n8n:5679\n      N8N_RUNNERS_AUTH_TOKEN: ${N8N_RUNNERS_AUTH_TOKEN:?Generate N8N_RUNNERS_AUTH_TOKEN}\n      N8N_RUNNERS_AUTO_SHUTDOWN_TIMEOUT: &quot;15&quot;\n      GENERIC_TIMEZONE: ${GENERIC_TIMEZONE:-Europe\/Istanbul}\n    read_only: true\n    tmpfs:\n      - \/tmp:rw,noexec,nosuid,size=64m\n    cap_drop:\n      - ALL\n    security_opt:\n      - no-new-privileges:true\n    networks:\n      - runner\n    logging:\n      driver: json-file\n      options:\n        max-size: &quot;10m&quot;\n        max-file: &quot;3&quot;\n\n  caddy:\n    image: ${CADDY_IMAGE:?Set CADDY_IMAGE in .env}\n    restart: unless-stopped\n    depends_on:\n      n8n:\n        condition: service_healthy\n    environment:\n      N8N_HOST: ${N8N_HOST:?Set the DNS hostname}\n      BOOTSTRAP_ALLOWED_IP: ${BOOTSTRAP_ALLOWED_IP:?Set the initial operator public IP}\n    ports:\n      - &quot;80:80&quot;\n      - &quot;443:443&quot;\n      - &quot;443:443\/udp&quot;\n    volumes:\n      - .\/Caddyfile:\/etc\/caddy\/Caddyfile:ro\n      - caddy_data:\/data\n      - caddy_config:\/config\n    networks:\n      - edge\n    logging:\n      driver: json-file\n      options:\n        max-size: &quot;10m&quot;\n        max-file: &quot;3&quot;\n\nvolumes:\n  postgres_data:\n  n8n_data:\n  caddy_data:\n  caddy_config:\n\nnetworks:\n  edge:\n  database:\n    internal: true\n  runner:\n    internal: true\nYAML<\/code><\/pre>\n<\/div>\n<p>n8n i\u00e7in veritaban\u0131n\u0131n tamam\u0131nda s\u00fcper kullan\u0131c\u0131 yetkisi gerekmez. \u0130lk PostgreSQL a\u00e7\u0131l\u0131\u015f\u0131nda yaln\u0131zca <code>n8n<\/code> veritaban\u0131n\u0131 y\u00f6neten <code>n8n_app<\/code> rol\u00fcn\u00fc olu\u015fturun:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cat &gt; initdb.sh &lt;&lt;&#x27;SH&#x27;\n#!\/bin\/sh\nset -eu\n\n# Runs only when postgres_data is first initialized. Identifiers are fixed;\n# psql safely quotes the application password as a SQL literal.\n: &quot;${N8N_DB_PASSWORD:?N8N_DB_PASSWORD must be set}&quot;\npsql --username &quot;$POSTGRES_USER&quot; --dbname &quot;$POSTGRES_DB&quot; \\\n  --set=ON_ERROR_STOP=1 --set=n8n_password=&quot;$N8N_DB_PASSWORD&quot; &lt;&lt;&#x27;SQL&#x27;\nCREATE ROLE n8n_app WITH LOGIN PASSWORD :&#x27;n8n_password&#x27; NOSUPERUSER NOCREATEDB NOCREATEROLE;\nALTER DATABASE n8n OWNER TO n8n_app;\nGRANT ALL ON SCHEMA public TO n8n_app;\nSQL\nSH\nchmod 644 initdb.sh<\/code><\/pre>\n<\/div>\n<p>Bu ba\u015flang\u0131\u00e7 beti\u011fi yaln\u0131zca bo\u015f veritaban\u0131 volume\u2019unda \u00e7al\u0131\u015f\u0131r. Daha sonra <code>.env<\/code> i\u00e7inde parola de\u011fi\u015ftirmek mevcut PostgreSQL rol\u00fcn\u00fcn parolas\u0131n\u0131 kendili\u011finden de\u011fi\u015ftirmez; parola de\u011fi\u015fikli\u011fini veritaban\u0131 ve n8n taraf\u0131nda birlikte uygulaman\u0131z gerekir.<\/p>\n<p>\u00dc\u00e7 uygulama portu host\u2019a yay\u0131nlanmad\u0131\u011f\u0131 i\u00e7in n8n edit\u00f6r\u00fcne, broker\u2019a veya veritaban\u0131na do\u011frudan internetten eri\u015fim yolu a\u00e7\u0131lmaz. Runner yaln\u0131zca kendi \u00f6zel a\u011f\u0131na ba\u011fl\u0131d\u0131r; n8n\u2019in normal servis ba\u011flant\u0131lar\u0131 i\u00e7in d\u0131\u015f a\u011fa \u00e7\u0131k\u0131\u015f\u0131 devam eder. Bu yap\u0131 Docker\u2019\u0131n yay\u0131nlanan portlar\u0131yla g\u00fcvenlik duvar\u0131 aras\u0131ndaki ili\u015fkiye g\u00fcvenerek bir veritaban\u0131n\u0131 korumaya \u00e7al\u0131\u015fmaz.<\/p>\n<h2 id=\"https-ilk-hesap\">HTTPS\u2019i a\u00e7\u0131n ve ilk hesab\u0131 koruyun<\/h2>\n<p>\u00d6nce normal Caddy yap\u0131land\u0131rmas\u0131n\u0131 <code>Caddyfile.final<\/code> olarak kaydedin. Caddy, alan ad\u0131 i\u00e7in sertifika al\u0131r, yeniler ve HTTP isteklerini HTTPS\u2019e y\u00f6nlendirir. Verinin tutuldu\u011fu <code>\/data<\/code> volume\u2019u sertifika anahtarlar\u0131n\u0131 da i\u00e7erir. <a href=\"https:\/\/caddyserver.com\/docs\/automatic-https\" rel=\"nofollow noopener\" target=\"_blank\">Otomatik HTTPS ko\u015fullar\u0131<\/a> DNS\u2019in do\u011fru olmas\u0131 ve gerekli portlar\u0131n Caddy\u2019ye ula\u015fmas\u0131d\u0131r.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cat &gt; Caddyfile.final &lt;&lt;&#x27;CADDY&#x27;\n{$N8N_HOST} {\n    reverse_proxy n8n:5678\n}\nCADDY<\/code><\/pre>\n<\/div>\n<p>\u0130lk a\u00e7\u0131l\u0131\u015fta ise a\u015fa\u011f\u0131daki dosyay\u0131 kullan\u0131n. Bu ge\u00e7ici kural, n8n\u2019in ilk sahip hesab\u0131 ekran\u0131n\u0131 yaln\u0131zca sizin IP adresinize a\u00e7ar. Sertifika do\u011frulamas\u0131n\u0131 Caddy y\u00f6netmeye devam eder. Alan ad\u0131n\u0131 araya eklenmi\u015f bir CDN\/proxy olmadan do\u011frudan sunucuya y\u00f6nlendirin; bu kural do\u011frudan ba\u011flanan istemci adresini esas al\u0131r.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cat &gt; Caddyfile &lt;&lt;&#x27;CADDY&#x27;\n{$N8N_HOST} {\n    @notOperator not remote_ip {$BOOTSTRAP_ALLOWED_IP}\n    respond @notOperator &quot;Initial setup is restricted.&quot; 403\n    reverse_proxy n8n:5678\n}\nCADDY<\/code><\/pre>\n<\/div>\n<p>Yap\u0131land\u0131rmay\u0131 kontrol edin, imajlar\u0131 indirin ve servisleri ba\u015flat\u0131n. Tam <code>docker compose config<\/code> \u00e7\u0131kt\u0131s\u0131 parolalar\u0131 a\u00e7\u0131\u011fa \u00e7\u0131karabilece\u011finden burada <code>--quiet<\/code> kullan\u0131yoruz.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker compose config --quiet\ndocker compose pull\ndocker compose run --rm --no-deps caddy caddy validate --config \/etc\/caddy\/Caddyfile --adapter caddyfile\ndocker compose up -d\ndocker compose ps<\/code><\/pre>\n<\/div>\n<p>\u0130lk a\u00e7\u0131l\u0131\u015fta veritaban\u0131 haz\u0131rlan\u0131r ve n8n migration\u2019lar\u0131 uygulan\u0131r. <code>docker compose ps<\/code> ile PostgreSQL ve n8n\u2019in sa\u011fl\u0131kl\u0131 duruma geldi\u011fini, runner\u2019\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 kontrol edin. S\u00fcr\u00fcm ve son uygulama mesajlar\u0131 i\u00e7in:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker compose exec n8n n8n --version\ndocker compose exec postgres psql -U postgres -d n8n -c &#x27;SELECT version();&#x27;\ndocker compose exec caddy caddy version\ndocker compose logs --tail=60 n8n task-runners<\/code><\/pre>\n<\/div>\n<p>\u0130zin verdi\u011finiz ba\u011flant\u0131dan <code>https:\/\/n8n.example.com<\/code> adresini a\u00e7\u0131n. Ba\u015fka bir a\u011fdan gelen iste\u011fin bu a\u015famada 403 almas\u0131 beklenir. <strong>Set up owner account<\/strong> ekran\u0131nda e-posta, ad ve g\u00fc\u00e7l\u00fc bir parola ile sahip hesab\u0131n\u0131 olu\u015fturup <strong>Next<\/strong> se\u00e7in. Ard\u0131ndan gelen <strong>Customize n8n to you<\/strong> ekran\u0131ndaki sorular\u0131 iste\u011fe ba\u011fl\u0131 b\u0131rak\u0131p <strong>Get started<\/strong> ile ilerleyebilirsiniz. \u00dccretsiz lisans anahtar\u0131 teklifi g\u00f6r\u00fcn\u00fcrse bu kurulum i\u00e7in <strong>Skip<\/strong> ile ge\u00e7ebilirsiniz.<\/p>\n<figure><a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/owner-setup.webp\"><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/owner-setup.webp\" width=\"440\" height=\"680\"  decoding=\"async\" alt=\"n8n sahip hesab\u0131 olu\u015fturma ekran\u0131; e-posta ve parola gizlenmi\u015f\"><\/a><figcaption>\u0130lk sahip hesab\u0131n\u0131 IP eri\u015fim kural\u0131 a\u00e7\u0131kken olu\u015fturun. \u00d6rnekte e-posta ve parola gizlenmi\u015ftir.<\/figcaption><\/figure>\n<p>\u0130lk a\u00e7\u0131l\u0131\u015fta <strong>Assistant Preview<\/strong> ekran\u0131 gelirse, bu rehberdeki i\u015f ak\u0131\u015f\u0131 edit\u00f6r\u00fcne ge\u00e7mek i\u00e7in <strong>Turn off for this instance<\/strong> se\u00e7ene\u011fini kullan\u0131p <strong>Turn off n8n Assistant<\/strong> ileti\u015fim kutusunu onaylay\u0131n. Ard\u0131ndan ayn\u0131 alan ad\u0131n\u0131 gizli bir taray\u0131c\u0131 penceresinde a\u00e7\u0131n; <strong>Sign in<\/strong> ekran\u0131ndan olu\u015fturdu\u011funuz e-posta ve parola ile giri\u015f yapabildi\u011finizi do\u011frulay\u0131n. Sahip hesab\u0131 ve oturum a\u00e7ma kontrol\u00fc tamamlan\u0131nca normal proxy yap\u0131land\u0131rmas\u0131na ge\u00e7in:<\/p>\n<figure><a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/sign-in.webp\"><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/sign-in.webp\" width=\"440\" height=\"470\"  decoding=\"async\" alt=\"n8n Sign in ekran\u0131nda e-posta ve parola alanlar\u0131\"><\/a><figcaption>Yeni bir gizli taray\u0131c\u0131 penceresinde oturum a\u00e7may\u0131 do\u011frulay\u0131n.<\/figcaption><\/figure>\n<div class=\"fc-code-example\">\n<pre><code>cp Caddyfile.final Caddyfile\ndocker compose exec caddy caddy reload --config \/etc\/caddy\/Caddyfile --adapter caddyfile<\/code><\/pre>\n<\/div>\n<p><code>cp<\/code> mevcut dosyan\u0131n i\u00e7eri\u011fini de\u011fi\u015ftirir; Caddy\u2019nin bind mount \u00fczerinden g\u00f6rd\u00fc\u011f\u00fc dosya korunur. Dosyay\u0131 atomik yeniden adland\u0131rmayla de\u011fi\u015ftiriyorsan\u0131z konteynerin eski dosyay\u0131 tutmamas\u0131 i\u00e7in Caddy\u2019yi yeniden olu\u015fturun. Son durumda ilk hesap ekran\u0131 yerine n8n\u2019in oturum a\u00e7ma ekran\u0131 g\u00f6r\u00fcnmelidir.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>curl -I http:\/\/n8n.example.com\/\ncurl -I https:\/\/n8n.example.com\/<\/code><\/pre>\n<\/div>\n<p>HTTPS kontrol\u00fcn\u00fc <code>-k<\/code> eklemeden yap\u0131n; sertifika do\u011frulamas\u0131n\u0131 kapatmak TLS testini ge\u00e7erli k\u0131lmaz. Caddy gerekli <code>X-Forwarded-*<\/code> ba\u015fl\u0131klar\u0131n\u0131 ve WebSocket ge\u00e7i\u015fini y\u00f6netir. Bu tek proxy d\u00fczeninde <code>N8N_PROXY_HOPS=1<\/code> ve <code>N8N_WEBHOOK_URL=https:\/\/alan-ad\u0131n\u0131z\/<\/code> birbiriyle uyumludur. Eski \u00f6rneklerde g\u00f6r\u00fclen <code>WEBHOOK_URL<\/code> art\u0131k deprecated durumdad\u0131r.<\/p>\n<h2 id=\"ilk-webhook\">\u0130lk kimlik do\u011frulamal\u0131 webhook\u2019u \u00e7al\u0131\u015ft\u0131r\u0131n<\/h2>\n<p>Kurulumun a\u00e7\u0131lmas\u0131 tek ba\u015f\u0131na yeterli de\u011fil. \u00dc\u00e7 d\u00fc\u011f\u00fcml\u00fc bir ak\u0131\u015fla HTTPS giri\u015fini, saklanan kimlik bilgisini, i\u015f ak\u0131\u015f\u0131 y\u00fcr\u00fctmesini ve harici Code runner\u2019\u0131n\u0131 birlikte kontrol edelim: <strong>Webhook \u2192 Code \u2192 Respond to Webhook<\/strong>.<\/p>\n<p>\u0130stek g\u00f6ndermek i\u00e7in ayr\u0131 bir anahtar olu\u015fturun. A\u015fa\u011f\u0131daki dosya zaten varsa komut \u00fczerine yazmay\u0131 reddeder:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>install -d -m 700 \/opt\/n8n\/secrets\npython3 - &lt;&lt;&#x27;PY&#x27;\nfrom pathlib import Path\nfrom secrets import token_hex\n\npath = Path(&quot;\/opt\/n8n\/secrets\/webhook-header.txt&quot;)\nwith path.open(&quot;x&quot;) as output:\n    output.write(&quot;Authorization: Bearer &quot; + token_hex(32) + &quot;\\n&quot;)\npath.chmod(0o600)\nPY<\/code><\/pre>\n<\/div>\n<p>\u0130ndirilen \u00f6rnek JSON\u2019u kullanacaksan\u0131z \u00e7al\u0131\u015fma alan\u0131nda <strong>Build a workflow<\/strong> se\u00e7in. \u00dcstteki \u00fc\u00e7 nokta men\u00fcs\u00fcnden <strong>Import \u2192 From file<\/strong> yoluyla dosyay\u0131 a\u00e7\u0131n. <strong>Importing this from an AI tool?<\/strong> teklifi \u00e7\u0131karsa <strong>Skip<\/strong> ile ge\u00e7in; bu \u00f6rne\u011fin MCP ba\u011flant\u0131s\u0131na ihtiyac\u0131 yoktur. \u00dc\u00e7 d\u00fc\u011f\u00fcm g\u00f6r\u00fcnd\u00fc\u011f\u00fcnde <strong>Ctrl+S<\/strong> ile kaydedin.<\/p>\n<p>n8n edit\u00f6r\u00fcnde Webhook d\u00fc\u011f\u00fcm\u00fcn\u00fc a\u00e7\u0131n; s\u0131f\u0131rdan haz\u0131rl\u0131yorsan\u0131z bu d\u00fc\u011f\u00fcm\u00fc ekleyin. HTTP Method de\u011ferini <strong>POST<\/strong>, Path de\u011ferini <code>fc-n8n-runner-check<\/code>, Authentication de\u011ferini <strong>Header Auth<\/strong> se\u00e7in. <strong>Connect to Header Auth<\/strong> ile kimlik bilgisi kayd\u0131n\u0131 a\u00e7\u0131n. Name <code>Authorization<\/code>, Value ise \u00f6zel dosyan\u0131zdaki <code>Bearer <\/code> ile ba\u015flayan de\u011fer olmal\u0131; <strong>Save<\/strong> ile kaydedin. Bu de\u011feri yaln\u0131zca kendi g\u00fcvenli terminalinizden okuyup HTTPS aray\u00fcz\u00fcne aktar\u0131n; ortak loglara veya ekran g\u00f6r\u00fcnt\u00fclerine koymay\u0131n. Webhook\u2019un \u00e7al\u0131\u015ft\u0131rma verileri istek ba\u015fl\u0131klar\u0131n\u0131 ve bu de\u011feri g\u00f6sterebilir; otomatik olarak gizlendi\u011fini varsaymay\u0131n.<\/p>\n<p>Webhook\u2019un yan\u0131t ayar\u0131n\u0131 <strong>Using Respond to Webhook Node<\/strong> yap\u0131n. Ard\u0131ndan Code d\u00fc\u011f\u00fcm\u00fcnde JavaScript ve <strong>Run Once for All Items<\/strong> se\u00e7erek \u015fu kodu girin:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>const body = $input.first().json.body;\nreturn [{\n  json: {\n    ok: true,\n    received: String(body.message ?? &#x27;&#x27;),\n    result: Number(body.value) + 1\n  }\n}];<\/code><\/pre>\n<\/div>\n<p>Son d\u00fc\u011f\u00fcm olan Respond to Webhook i\u00e7in <strong>First Incoming Item<\/strong> ve HTTP 200 se\u00e7in; bu basit JSON yan\u0131t\u0131nda streaming\u2019i kapat\u0131n. Gelen istek ba\u015fl\u0131klar\u0131n\u0131 yan\u0131ta eklemiyoruz. B\u00f6ylece kimlik do\u011frulama de\u011feri istemciye geri d\u00f6nmez.<\/p>\n<p>Webhook\u2019un <strong>Test URL<\/strong> sekmesindeki adresi kopyalay\u0131n, d\u00fc\u011f\u00fcm panelini kapat\u0131p ak\u0131\u015f\u0131 kaydedin. \u00dc\u00e7 d\u00fc\u011f\u00fcm\u00fc birlikte s\u0131namak i\u00e7in canvas\u2019\u0131n alt\u0131ndaki <strong>Execute<\/strong> d\u00fc\u011fmesine bas\u0131n; <strong>Waiting for you to call the Test URL<\/strong> mesaj\u0131n\u0131 bekleyin. D\u00fc\u011f\u00fcm i\u00e7indeki <strong>Listen for test event<\/strong> tek ba\u015f\u0131na Webhook\u2019u s\u0131nar: bu s\u00fcr\u00fcmde o ad\u0131m HTTP 200 ve bo\u015f g\u00f6vde d\u00f6nd\u00fcrd\u00fc, Code ile yan\u0131t d\u00fc\u011f\u00fcm\u00fcn\u00fc \u00e7al\u0131\u015ft\u0131rmad\u0131. A\u015fa\u011f\u0131daki iste\u011fi tam ak\u0131\u015f dinleyicisi a\u00e7\u0131kken g\u00f6nderin; alan ad\u0131n\u0131 ve gerekirse yolu kopyalad\u0131\u011f\u0131n\u0131z URL\u2019ye g\u00f6re d\u00fczeltin:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>curl --fail-with-body --silent --show-error \\\n  --header @\/opt\/n8n\/secrets\/webhook-header.txt \\\n  --header &#x27;Content-Type: application\/json&#x27; \\\n  --data &#x27;{&quot;value&quot;:41,&quot;message&quot;:&quot;fibacloud-lab&quot;}&#x27; \\\n  &#x27;https:\/\/n8n.example.com\/webhook-test\/fc-n8n-runner-check&#x27;<\/code><\/pre>\n<\/div>\n<p>Tam ak\u0131\u015f testinde al\u0131nan ve kendi kurulumunuzda beklemeniz gereken yan\u0131t:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>{&quot;ok&quot;:true,&quot;received&quot;:&quot;fibacloud-lab&quot;,&quot;result&quot;:42}<\/code><\/pre>\n<\/div>\n<figure><a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/code-result.webp\"><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/code-result.webp\" width=\"1015\" height=\"485\"  decoding=\"async\" alt=\"n8n Code d\u00fc\u011f\u00fcm\u00fcndeki JavaScript ve ok true, received fibacloud-lab, result 42 \u00e7\u0131kt\u0131s\u0131\"><\/a><figcaption>Ger\u00e7ek tam ak\u0131\u015f testinde Code d\u00fc\u011f\u00fcm\u00fc 41 girdisini 42 sonucuna d\u00f6n\u00fc\u015ft\u00fcrd\u00fc. G\u00f6rsel yaln\u0131z kodu ve se\u00e7ilen yan\u0131t alanlar\u0131n\u0131 g\u00f6sterir.<\/figcaption><\/figure>\n<p>Test URL yaln\u0131zca test dinleyicisi a\u00e7\u0131kken kullan\u0131l\u0131r. Kal\u0131c\u0131 webhook i\u00e7in \u00fcstteki <strong>Publish<\/strong> d\u00fc\u011fmesine bas\u0131n, <strong>Publish workflow<\/strong> penceresinde bir s\u00fcr\u00fcm ad\u0131 girip tekrar <strong>Publish<\/strong> se\u00e7in. <strong>Workflow published<\/strong> bildirimini <strong>Got it<\/strong> ile kapat\u0131n; \u00fcstte <strong>Published<\/strong> durumu g\u00f6r\u00fcnmelidir. Ard\u0131ndan Webhook\u2019taki <strong>Production URL<\/strong> sekmesinden adresi kopyalay\u0131n. \u00dcretim iste\u011fi i\u00e7in test dinleyicisini a\u00e7man\u0131z gerekmez.<\/p>\n<figure><a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/workflow.webp\"><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-n8n-20261031\/workflow.webp\" width=\"1440\" height=\"1080\"  decoding=\"async\" alt=\"Published durumundaki Webhook, Code ve Respond to Webhook ak\u0131\u015f\u0131\"><\/a><figcaption>Yay\u0131mlanm\u0131\u015f \u00fc\u00e7 d\u00fc\u011f\u00fcml\u00fc \u00f6rnek ak\u0131\u015f. B\u00fcy\u00fck g\u00f6r\u00fcnt\u00fcy\u00fc a\u00e7mak i\u00e7in g\u00f6rsele t\u0131klay\u0131n.<\/figcaption><\/figure>\n<div class=\"fc-code-example\">\n<pre><code>curl --fail-with-body --silent --show-error \\\n  --header @\/opt\/n8n\/secrets\/webhook-header.txt \\\n  --header &#x27;Content-Type: application\/json&#x27; \\\n  --data &#x27;{&quot;value&quot;:41,&quot;message&quot;:&quot;fibacloud-lab&quot;}&#x27; \\\n  &#x27;https:\/\/n8n.example.com\/webhook\/fc-n8n-runner-check&#x27;<\/code><\/pre>\n<\/div>\n<p>\u00dcretim iste\u011finden sonra <strong>Executions<\/strong> sekmesinde yeni kayd\u0131n <strong>Succeeded<\/strong> durumunu kontrol edin; \u00fcretim sonucu edit\u00f6rdeki \u00f6nceki test \u00e7\u0131kt\u0131s\u0131n\u0131 kendili\u011finden yenilemez. Bir de ayn\u0131 \u00fcretim adresine anahtars\u0131z ve yanl\u0131\u015f anahtarl\u0131 istekleri deneyin:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>curl --silent --show-error --output \/dev\/null --write-out &#x27;%{http_code}\\n&#x27; \\\n  --header &#x27;Content-Type: application\/json&#x27; \\\n  --data &#x27;{&quot;value&quot;:41,&quot;message&quot;:&quot;fibacloud-lab&quot;}&#x27; \\\n  &#x27;https:\/\/n8n.example.com\/webhook\/fc-n8n-runner-check&#x27;\n\ncurl --silent --show-error --output \/dev\/null --write-out &#x27;%{http_code}\\n&#x27; \\\n  --header &#x27;Authorization: Bearer invalid-test-value&#x27; \\\n  --header &#x27;Content-Type: application\/json&#x27; \\\n  --data &#x27;{&quot;value&quot;:41,&quot;message&quot;:&quot;fibacloud-lab&quot;}&#x27; \\\n  &#x27;https:\/\/n8n.example.com\/webhook\/fc-n8n-runner-check&#x27;<\/code><\/pre>\n<\/div>\n<p>Bu laboratuvarda iki istek de HTTP <strong>403<\/strong> ile reddedildi; do\u011fru anahtar HTTP <strong>200<\/strong> ve yukar\u0131daki JSON\u2019u d\u00f6nd\u00fcrd\u00fc. Kendi kurulumunuzda ba\u015far\u0131l\u0131 JSON \u00e7\u0131kt\u0131s\u0131n\u0131 ve reddedilen isteklerin HTTP kodlar\u0131n\u0131 birlikte kontrol edin. Edit\u00f6re giri\u015f yapm\u0131\u015f olman\u0131z, d\u0131\u015far\u0131dan gelen bir webhook iste\u011finin otomatik olarak yetkilendirildi\u011fi anlam\u0131na gelmez; burada onu Header Auth korur. <a href=\"https:\/\/docs.n8n.io\/integrations\/builtin\/credentials\/webhook\" rel=\"nofollow noopener\" target=\"_blank\">Webhook kimlik bilgisi belgesi<\/a> desteklenen y\u00f6ntemleri a\u00e7\u0131klar.<\/p>\n<p>Yaln\u0131zca alan ekleme veya yeniden adland\u0131rma yapacaksan\u0131z Code yerine Edit Fields kullanabilirsiniz. \u00d6rne\u011fin <code>received<\/code> alan\u0131n\u0131 <code>{{ $json.body.message }}<\/code> ifadesine ba\u011flamak i\u00e7in \u00f6zel JavaScript gerekmez. Bu \u00f6rnekte Code\u2019un kullan\u0131lmas\u0131, harici runner\u2019\u0131n da ger\u00e7ekten \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 s\u0131namak i\u00e7indir.<\/p>\n<h2 id=\"kalicilik-kaynak\">Yeniden ba\u015flatma ve kaynak kullan\u0131m\u0131n\u0131 kontrol edin<\/h2>\n<p>Ak\u0131\u015f kaydedildikten sonra n8n ve runner konteynerlerini yeniden olu\u015fturun. Volume\u2019lar\u0131 silmeyin:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker compose up -d --no-deps --force-recreate --wait --wait-timeout 240 n8n task-runners\ndocker compose ps<\/code><\/pre>\n<\/div>\n<p>Tekrar oturum a\u00e7\u0131n ve ayn\u0131 \u00fcretim webhook iste\u011fini ayn\u0131 anahtarla \u00e7al\u0131\u015ft\u0131r\u0131n. Ak\u0131\u015f, yay\u0131n durumu ve kimlik bilgisi kaybolmamal\u0131d\u0131r. Bunun ard\u0131ndan bo\u015fta ve k\u00fc\u00e7\u00fck \u00f6rnek ak\u0131\u015f \u00e7al\u0131\u015f\u0131rken bellek kullan\u0131m\u0131n\u0131 g\u00f6zlemleyin:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>free -h\ndocker stats --no-stream\ndocker compose ps<\/code><\/pre>\n<\/div>\n<p>Bu k\u0131sa kontrol bir y\u00fck testi de\u011fildir. B\u00fcy\u00fck JSON listeleri, dosyalar, uzun \u00e7al\u0131\u015fan Code d\u00fc\u011f\u00fcmleri ve paralel ak\u0131\u015flar farkl\u0131 kaynak t\u00fcketir. Bellek yetersizli\u011finde \u00f6nce yeniden ba\u015flama\/OOM belirtilerini ve ak\u0131\u015f\u0131n veri boyutunu inceleyin; sa\u011fl\u0131kl\u0131 g\u00f6r\u00fcnen tek bir k\u00fc\u00e7\u00fck \u00e7al\u0131\u015ft\u0131rmay\u0131 \u00fcretim kapasitesi s\u00f6z\u00fcne d\u00f6n\u00fc\u015ft\u00fcrmeyin.<\/p>\n<p>A\u015fa\u011f\u0131daki <code>docker stats --no-stream<\/code> de\u011ferleri k\u00fc\u00e7\u00fck \u00f6rnek ak\u0131\u015ftan sonra al\u0131nan tek bir g\u00f6r\u00fcnt\u00fcd\u00fcr. O anda host yakla\u015f\u0131k 385 MiB swap kullan\u0131yordu. Bu de\u011ferler yo\u011fun andaki tepe t\u00fcketim veya 2 GB\u2019l\u0131k bir sunucunun \u00fcretim kapasitesi de\u011fildir.<\/p>\n<table>\n<thead>\n<tr>\n<th>Servis<\/th>\n<th>Ak\u0131\u015f sonras\u0131 RAM g\u00f6r\u00fcnt\u00fcs\u00fc<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>n8n<\/td>\n<td>443,6 MiB<\/td>\n<\/tr>\n<tr>\n<td>Task runner<\/td>\n<td>90,16 MiB<\/td>\n<\/tr>\n<tr>\n<td>PostgreSQL<\/td>\n<td>64,1 MiB<\/td>\n<\/tr>\n<tr>\n<td>Caddy<\/td>\n<td>58,86 MiB<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"yedek-geri-yukleme\">Yedek al\u0131n ve ayr\u0131 bir kurulumda geri y\u00fckleyin<\/h2>\n<p>Kurtar\u0131labilir n8n yede\u011fi; PostgreSQL veritaban\u0131n\u0131, <code>n8n_data<\/code> volume\u2019unu, de\u011fi\u015fmeyen <code>N8N_ENCRYPTION_KEY<\/code> de\u011ferini ve kurulum dosyalar\u0131n\u0131 birlikte kapsar. Caddy sertifikalar\u0131n\u0131 da korumak yeniden kurulumda gereksiz sertifika taleplerini \u00f6nler. Yaln\u0131zca ak\u0131\u015f JSON\u2019unu d\u0131\u015far\u0131 aktarmak kullan\u0131c\u0131lar\u0131, kimlik bilgilerini ve b\u00fct\u00fcn kurulum durumunu yedeklemez.<\/p>\n<p>\u0130ndirme paketindeki <code>maintenance.py<\/code> dosyas\u0131n\u0131 <code>\/opt\/n8n\/maintenance.py<\/code> olarak yerle\u015ftirin; mevcut <code>.env<\/code> dosyan\u0131z\u0131n \u00fczerine \u00f6rnek dosya yazmay\u0131n. Betik Python 3 ve Docker eri\u015fimi olan root kabu\u011funda \u00e7al\u0131\u015f\u0131r. Yedek hedefi yeni bir dizin olmal\u0131; sonraki yedeklerde tarih veya ad\u0131n\u0131 de\u011fi\u015ftirin.<\/p>\n<p>Betik Caddy, n8n ve runner\u2019\u0131 durdurur; PostgreSQL a\u00e7\u0131kken <code>pg_dump<\/code> ile mant\u0131ksal yede\u011fi al\u0131r. n8n\/Caddy volume\u2019lar\u0131n\u0131 ve d\u00f6rt yap\u0131land\u0131rma dosyas\u0131n\u0131 kaydeder, sekiz yedek dosyas\u0131n\u0131n hash\u2019lerini <code>manifest.json<\/code> i\u00e7ine yazar, ard\u0131ndan as\u0131l servisleri yeniden ba\u015flatmay\u0131 dener. Canl\u0131 PostgreSQL veri dizinini d\u00fcz bir ar\u015fivle kopyalamaz. Yedek parolalar, kimlik bilgileri ve sertifika anahtarlar\u0131 i\u00e7erir; \u00f6zel dizinde tutun.<\/p>\n<p>Bu k\u00fc\u00e7\u00fck sunucuda iki kurulumu ayn\u0131 anda \u00e7al\u0131\u015ft\u0131rmamak i\u00e7in, yedek tamamland\u0131ktan sonra as\u0131l projeyi yeniden durdurun. Aray\u00fcz ve webhook\u2019lar geri y\u00fckleme kontrol\u00fc bitene kadar kullan\u0131lamaz; bunun i\u00e7in bir bak\u0131m aral\u0131\u011f\u0131 ay\u0131r\u0131n.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cd \/opt\/n8n\npython3 maintenance.py backup \/root\/n8n-backup-20261031\ndocker compose stop<\/code><\/pre>\n<\/div>\n<p>A\u015fa\u011f\u0131daki geri y\u00fckleme yeni bir dizin, farkl\u0131 proje ad\u0131 ve bo\u015f volume\u2019lar kullan\u0131r. Betik hash\u2019leri do\u011frular; var olan hedefin, proje verilerinin veya volume\u2019lar\u0131n \u00fczerine yazmay\u0131 reddeder. \u015eifreleme anahtar\u0131 eksikse veya veritaban\u0131yla e\u015fle\u015fmiyorsa kay\u0131tl\u0131 kimlik bilgileri kullan\u0131lamaz.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>python3 maintenance.py restore \\\n  \/root\/n8n-backup-20261031 \\\n  \/opt\/n8n-restore \\\n  --project n8n-restore<\/code><\/pre>\n<\/div>\n<p>Kopyada yaln\u0131z PostgreSQL, n8n ve runner ba\u015flat\u0131l\u0131r. Caddy a\u00e7\u0131lmaz, host portu yay\u0131mlanmaz ve ba\u011fl\u0131 Compose a\u011flar\u0131 <code>internal<\/code> kal\u0131r. Bu kopyay\u0131 yeni bir genel HTTPS kurulumu gibi de\u011ferlendirmeyin. A\u011f s\u0131n\u0131r\u0131 zamanlay\u0131c\u0131lar\u0131 durdurmaz; i\u015fler kopyan\u0131n kendi veritaban\u0131n\u0131 de\u011fi\u015ftirebilir. Bu nedenle a\u015fa\u011f\u0131daki denemeyi yaln\u0131z rehberdeki kontroll\u00fc webhook ak\u0131\u015f\u0131yla yap\u0131n.<\/p>\n<p>Orijinal anahtar dosyas\u0131n\u0131 standart giri\u015ften aktararak kopyan\u0131n i\u00e7inden kimlik do\u011frulamas\u0131n\u0131 s\u0131nay\u0131n. Komut anahtar\u0131 ekrana veya i\u015flem arg\u00fcmanlar\u0131na yazmaz. Eksik\/yanl\u0131\u015f anahtarda ret, do\u011fru anahtarda HTTP 200 ve <code>result: 42<\/code> bekler:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cd \/opt\/n8n-restore\ndocker compose -f compose.yml -f restore.override.json exec -T n8n node -e &#x27;\nconst prefix = &quot;Authorization: &quot;;\nconst line = require(&quot;node:fs&quot;).readFileSync(0, &quot;utf8&quot;).trim();\nif (!line.startsWith(prefix)) throw new Error(&quot;Invalid header file&quot;);\nconst savedHeader = line.slice(prefix.length);\n(async () =&gt; {\n  for (const [name, key] of [\n    [&quot;missing&quot;, null],\n    [&quot;wrong&quot;, &quot;Bearer invalid-test-value&quot;],\n    [&quot;valid&quot;, savedHeader],\n  ]) {\n    const headers = { &quot;Content-Type&quot;: &quot;application\/json&quot; };\n    if (key) headers.Authorization = key;\n    const response = await fetch(\n      &quot;http:\/\/127.0.0.1:5678\/webhook\/fc-n8n-runner-check&quot;,\n      {\n        method: &quot;POST&quot;,\n        headers,\n        body: JSON.stringify({ value: 41, message: &quot;fibacloud-lab&quot; }),\n        signal: AbortSignal.timeout(90000),\n      },\n    );\n    const body = await response.text();\n    console.log(JSON.stringify({ case: name, status: response.status, body }));\n    if (name === &quot;valid&quot;) {\n      const result = JSON.parse(body);\n      if (response.status !== 200 || result.ok !== true ||\n          result.received !== &quot;fibacloud-lab&quot; || result.result !== 42) {\n        throw new Error(&quot;Restored webhook result did not match&quot;);\n      }\n    } else if (![401, 403].includes(response.status)) {\n      throw new Error(&quot;Unauthenticated request was not rejected&quot;);\n    }\n  }\n})().catch(error =&gt; {\n  console.error(error.message);\n  process.exitCode = 1;\n});\n&#x27; &lt; \/opt\/n8n\/secrets\/webhook-header.txt<\/code><\/pre>\n<\/div>\n<p>Laboratuvarda geri y\u00fcklenen \u00f6rnek eksik ve yanl\u0131\u015f anahtara HTTP 403, orijinal anahtara HTTP 200 ve ayn\u0131 JSON yan\u0131t\u0131n\u0131 verdi. Kay\u0131tl\u0131 sahip hesab\u0131yla yap\u0131lan oturum a\u00e7ma iste\u011fi de 200 d\u00f6nd\u00fcrd\u00fc. Ayr\u0131 proje, yeni volume\u2019lar, kapal\u0131 host portlar\u0131 ve i\u00e7 a\u011flar ger\u00e7ek Docker incelemesiyle kontrol edildi. Sonu\u00e7 yaln\u0131z konteynerlerin a\u00e7\u0131ld\u0131\u011f\u0131n\u0131 de\u011fil, veritaban\u0131 ile \u015fifreleme anahtar\u0131n\u0131n birlikte geri geldi\u011fini g\u00f6sterdi. Beti\u011fin \u00f6zel <code>restore-receipt.json<\/code> kayd\u0131n\u0131 yedek manifest\u2019iyle birlikte saklay\u0131n.<\/p>\n<p>Kontrol bitince kopyay\u0131 durdurup as\u0131l kurulumu yeniden ba\u015flat\u0131n. Kopya i\u00e7in iki <code>-f<\/code> dosyas\u0131n\u0131 da kullan\u0131n; b\u00f6ylece geri y\u00fcklemenin a\u011f ve servis ayarlar\u0131 korunur. Kontrol ba\u015far\u0131s\u0131zsa da as\u0131l projeyi geri a\u00e7\u0131n ve orijinal volume\u2019lar\u0131 silmeden sorunu inceleyin:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>cd \/opt\/n8n-restore\ndocker compose -f compose.yml -f restore.override.json stop\n\ncd \/opt\/n8n\ndocker compose up -d --wait --wait-timeout 240\ndocker compose ps<\/code><\/pre>\n<\/div>\n<p>As\u0131l HTTPS adresinde oturum a\u00e7may\u0131 ve do\u011fru anahtarl\u0131 \u00fcretim webhook\u2019unu yeniden kontrol edin. Yede\u011fin bir kopyas\u0131n\u0131 sunucudan ayr\u0131, eri\u015fimi k\u0131s\u0131tl\u0131 ve \u015fifreli bir yerde tutun. Ayn\u0131 diskteki ar\u015fiv yanl\u0131\u015f bir g\u00fcncellemeye kar\u015f\u0131 yararl\u0131d\u0131r; sunucunun veya diskin tamamen kayb\u0131n\u0131 tek ba\u015f\u0131na kar\u015f\u0131lamaz.<\/p>\n<h2 id=\"guncelleme\">n8n\u2019i ve di\u011fer servisleri nas\u0131l g\u00fcncellemelisiniz?<\/h2>\n<p>\u00d6nce \u00e7al\u0131\u015fan yede\u011fi ve geri y\u00fckleme kontrol\u00fcn\u00fc tamamlay\u0131n. n8n\u2019in <a href=\"https:\/\/github.com\/n8n-io\/n8n\/releases\" rel=\"nofollow noopener\" target=\"_blank\">s\u00fcr\u00fcm notlar\u0131n\u0131<\/a> okuyun; ana s\u00fcr\u00fcm de\u011fi\u015fikliklerinde migration ad\u0131mlar\u0131n\u0131 ayr\u0131ca de\u011ferlendirin. <code>.env<\/code> i\u00e7indeki n8n ve runner imajlar\u0131n\u0131 ayn\u0131 yeni uygulama s\u00fcr\u00fcm\u00fcne, her birini kendi do\u011frulanm\u0131\u015f digest\u2019iyle birlikte g\u00fcncelleyin.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>docker compose pull\ndocker compose up -d\ndocker compose ps<\/code><\/pre>\n<\/div>\n<p>Yeniden HTTPS oturumunu ve kimlik do\u011frulamal\u0131 webhook\u2019u kontrol edin. Sadece <code>docker compose restart<\/code> yeni imaj\u0131 veya de\u011fi\u015ftirilmi\u015f ortam de\u011fi\u015fkenlerini uygulamaz. Veritaban\u0131 migration\u2019\u0131 yap\u0131ld\u0131ysa eski imaj\u0131 ba\u015flatmak da tek ba\u015f\u0131na g\u00fcvenilir geri d\u00f6n\u00fc\u015f de\u011fildir; gerekti\u011finde uyumlu imajlarla g\u00fcncelleme \u00f6ncesi yede\u011fi geri y\u00fckleyin.<\/p>\n<p>PostgreSQL\u2019in ayn\u0131 ana s\u00fcr\u00fcm i\u00e7indeki bak\u0131m g\u00fcncellemelerini takip edin. PostgreSQL 17\u2019den 18\u2019e ge\u00e7i\u015fi s\u0131radan etiket de\u011fi\u015fimi gibi uygulamay\u0131n; ana s\u00fcr\u00fcm de\u011fi\u015fiminde veri ta\u015f\u0131ma y\u00f6ntemi gerekir. <a href=\"https:\/\/www.postgresql.org\/support\/versioning\/\" rel=\"nofollow noopener\" target=\"_blank\">PostgreSQL s\u00fcr\u00fcm politikas\u0131<\/a> destek s\u00fcrelerini ve g\u00fcncelleme ayr\u0131m\u0131n\u0131 a\u00e7\u0131klar. Caddy\u2019nin bak\u0131m s\u00fcr\u00fcm\u00fcn\u00fc de ayn\u0131 plan i\u00e7inde g\u00fcncelleyin.<\/p>\n<p>Bu Compose \u00f6rne\u011fi Docker loglar\u0131n\u0131 dosya ba\u015f\u0131na 10 MB ve \u00fc\u00e7 dosyayla s\u0131n\u0131rlar; n8n\u2019in eski \u00e7al\u0131\u015ft\u0131rma verilerini temizlemesini a\u00e7ar ve ya\u015f e\u015fi\u011fini 168 saat yapar. Saklama s\u00fcresini kendi inceleme ve veri ihtiyac\u0131n\u0131za g\u00f6re belirleyin; saklanan \u00e7al\u0131\u015ft\u0131rma verileri m\u00fc\u015fteri bilgileri i\u00e7erebilir.<\/p>\n<h2 id=\"sorun-giderme\">S\u0131k kar\u015f\u0131la\u015f\u0131lan sorunlar<\/h2>\n<table>\n<thead>\n<tr>\n<th>Belirti<\/th>\n<th>\u0130lk kontrol<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>\u0130lk kurulumda 403<\/td>\n<td><code>BOOTSTRAP_ALLOWED_IP<\/code> ger\u00e7ek ba\u011flant\u0131 IP\u2019niz mi? VPN veya a\u011f de\u011fi\u015fikli\u011fi adresinizi de\u011fi\u015ftirmi\u015f olabilir.<\/td>\n<\/tr>\n<tr>\n<td>502 Bad Gateway<\/td>\n<td>n8n sa\u011fl\u0131kl\u0131 m\u0131, PostgreSQL ba\u011flant\u0131s\u0131 kurulmu\u015f mu, Caddy ile n8n ayn\u0131 <code>edge<\/code> a\u011f\u0131nda m\u0131?<\/td>\n<\/tr>\n<tr>\n<td>Sertifika al\u0131nam\u0131yor<\/td>\n<td>A\/AAAA kay\u0131tlar\u0131 do\u011fru mu, 80\/443 ger\u00e7ekten Caddy\u2019ye ula\u015f\u0131yor mu, ayn\u0131 portta ba\u015fka servis var m\u0131?<\/td>\n<\/tr>\n<tr>\n<td>Webhook 404<\/td>\n<td>Test ve Production URL kar\u0131\u015fm\u0131\u015f m\u0131? Test dinleyicisi a\u00e7\u0131k m\u0131 veya ak\u0131\u015f yay\u0131mlanm\u0131\u015f m\u0131? HTTP y\u00f6ntemi POST mu?<\/td>\n<\/tr>\n<tr>\n<td>Kimlik do\u011frulamas\u0131 reddediliyor<\/td>\n<td>Header ad\u0131 <code>Authorization<\/code> m\u0131, de\u011fer <code>Bearer <\/code> bo\u015flu\u011fuyla birlikte ayn\u0131 m\u0131, do\u011fru credential se\u00e7ili mi?<\/td>\n<\/tr>\n<tr>\n<td>Code \u00e7al\u0131\u015ft\u0131rmas\u0131 bekliyor<\/td>\n<td>Runner \u00e7al\u0131\u015f\u0131yor mu, uygulama s\u00fcr\u00fcm\u00fc n8n ile ayn\u0131 m\u0131, broker URI ve payla\u015f\u0131lan anahtar e\u015fle\u015fiyor mu?<\/td>\n<\/tr>\n<tr>\n<td>Yeniden ba\u015flatmada veri kayb\u0131<\/td>\n<td>Ayn\u0131 Compose proje ad\u0131 ve ayn\u0131 volume\u2019lar kullan\u0131l\u0131yor mu? Yanl\u0131\u015fl\u0131kla farkl\u0131 dizinden farkl\u0131 proje olu\u015fturulmu\u015f olabilir.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div class=\"fc-code-example\">\n<pre><code>docker compose ps\ndocker compose logs --tail=80 n8n task-runners caddy\ndf -h<\/code><\/pre>\n<\/div>\n<p>Loglar\u0131 payla\u015fmadan \u00f6nce alan adlar\u0131, istek i\u00e7erikleri ve gizli de\u011ferler a\u00e7\u0131s\u0131ndan kontrol edin. <code>docker compose down -v<\/code> kal\u0131c\u0131 volume\u2019lar\u0131 da siler; sorun giderme i\u00e7in s\u0131radan bir yeniden ba\u015flatma komutu de\u011fildir.<\/p>\n<h2 id=\"sss\">S\u0131k sorulan sorular<\/h2>\n<h3 id=\"n8n-ucretsiz\">n8n kendi sunucumda \u00fccretsiz mi?<\/h3>\n<p>Community s\u00fcr\u00fcm\u00fc Sustainable Use License kapsam\u0131nda kullan\u0131labilir. Kurumunuzdaki ki\u015filerin ak\u0131\u015f olu\u015fturdu\u011fu i\u00e7 kullan\u0131m ile d\u0131\u015f m\u00fc\u015fterilerin ak\u0131\u015f olu\u015fturabildi\u011fi, yap\u0131land\u0131rabildi\u011fi veya n8n\u2019e hizmet olarak eri\u015fti\u011fi kullan\u0131m ayn\u0131 de\u011fildir. Sunucu \u00fccretinin d\u0131\u015f\u0131nda ticari lisans veya ba\u011fland\u0131\u011f\u0131n\u0131z API\u2019ler i\u00e7in \u00fccret gerekebilir. Kullan\u0131m bi\u00e7iminizi <a href=\"https:\/\/support.n8n.io\/article\/can-i-use-your-license-for-my-use-case\" rel=\"nofollow noopener\" target=\"_blank\">n8n\u2019in g\u00fcncel lisans a\u00e7\u0131klamas\u0131yla<\/a> kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<h3 id=\"n8n-kac-gb-ram\">n8n i\u00e7in ka\u00e7 GB RAM gerekir?<\/h3>\n<p>\u0130htiya\u00e7, kurdu\u011funuz servisler ve i\u015f ak\u0131\u015flar\u0131n\u0131n veri hacmiyle birlikte de\u011ferlendirilir. Bu rehberin test kutusunda yer alan \u00f6l\u00e7\u00fcm yaln\u0131zca belirtilen k\u00fc\u00e7\u00fck ak\u0131\u015f\u0131 kapsar. Assistant, yerel model, b\u00fcy\u00fck dosya i\u015fleme veya yo\u011fun paralellik i\u00e7in ayn\u0131 sonucu varsaymay\u0131n.<\/p>\n<h3 id=\"n8n-domain\">Alan ad\u0131 ve HTTPS zorunlu mu?<\/h3>\n<p>Yerel deneme ayr\u0131 bir senaryodur. Bu rehberde internetten eri\u015filen edit\u00f6r ve webhook i\u00e7in kendi alt alan ad\u0131n\u0131z\u0131 ve do\u011frulanabilir HTTPS sertifikas\u0131n\u0131 kullan\u0131yoruz. B\u00f6ylece oturum ve webhook kimlik bilgilerini \u015fifreli ba\u011flant\u0131yla ta\u015f\u0131yabilirsiniz.<\/p>\n<h3 id=\"n8n-cpanel-plesk\">cPanel veya Plesk \u00fczerinde ayn\u0131 komutlar\u0131 kullanabilir miyim?<\/h3>\n<p>Payla\u015f\u0131ml\u0131 hosting hesab\u0131, Docker servisleri \u00e7al\u0131\u015ft\u0131rabilece\u011finiz bir VPS\u2019in yerini tutmaz. Kendi VPS\u2019inizde panel varsa portlar ve web servisi panel taraf\u0131ndan y\u00f6netilebilir. Mevcut siteleri koruyarak panelin proxy d\u00fczenine uyarlay\u0131n veya uygulamay\u0131 ayr\u0131 bir sunucuda \u00e7al\u0131\u015ft\u0131r\u0131n.<\/p>\n<p>n8n i\u015f y\u00fck\u00fcn\u00fcz\u00fc kendi altyap\u0131n\u0131zda \u00e7al\u0131\u015ft\u0131rmak i\u00e7in <a href=\"https:\/\/www.fibacloud.com\/tr\/urunler\/shared\">FibaCloud bulut sunucu se\u00e7eneklerini<\/a> inceleyebilirsiniz. Kaynak se\u00e7imini ak\u0131\u015f\u0131n\u0131z\u0131n \u00f6l\u00e7\u00fclen t\u00fcketimine g\u00f6re yap\u0131n; yedekleme ve bak\u0131m sorumlulu\u011funu da kurulumun bir par\u00e7as\u0131 olarak planlay\u0131n.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Ubuntu VPS \u00fczerinde n8n\u2019i Docker Compose, PostgreSQL, Caddy ve harici task runner ile kurun; HTTPS, kimlik do\u011frulamal\u0131 webhook ve yedekten d\u00f6n\u00fc\u015f\u00fc kontrol edin.<\/p>\n","protected":false},"author":1,"featured_media":2612,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[54,280,72],"class_list":["post-2610","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","tag-docker","tag-n8n","tag-ubuntu"],"lang":"tr","translations":{"tr":2610,"en":2611},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts\/2610","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/comments?post=2610"}],"version-history":[{"count":1,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts\/2610\/revisions"}],"predecessor-version":[{"id":2614,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts\/2610\/revisions\/2614"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/media\/2612"}],"wp:attachment":[{"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/media?parent=2610"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/categories?post=2610"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/tags?post=2610"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}