{"id":2622,"date":"2026-11-01T00:20:02","date_gmt":"2026-10-31T21:20:02","guid":{"rendered":"https:\/\/www.fibacloud.com\/community\/tutorials\/?p=2622"},"modified":"2026-11-01T00:20:02","modified_gmt":"2026-10-31T21:20:02","slug":"uptime-kuma-kurulumu","status":"publish","type":"post","link":"https:\/\/www.fibacloud.com\/community\/tutorials\/uptime-kuma-kurulumu\/","title":{"rendered":"Uptime Kuma Kurulumu: Site \u0130zleme ve Durum Sayfas\u0131"},"content":{"rendered":"<p>Uptime Kuma, web sitelerinizi ve servislerinizi belirli aral\u0131klarla kontrol eden, kesinti oldu\u011funda bildirim g\u00f6nderebilen a\u00e7\u0131k kaynakl\u0131 bir izleme arac\u0131d\u0131r. Bu rehberde mevcut bir Coolify sunucusuna Uptime Kuma kuracak; HTTPS \u00fczerinden giri\u015f yap\u0131p bir HTTP kontrol\u00fc, webhook bildirimi ve herkese a\u00e7\u0131k durum sayfas\u0131 olu\u015fturaca\u011f\u0131z. Ard\u0131ndan kontroll\u00fc bir uygulama kesintisini ve geri d\u00f6n\u00fc\u015f\u00fc izleyecek, kal\u0131c\u0131 verinin yede\u011fini al\u0131p geri y\u00fckleyece\u011fiz.<\/p>\n<p>\u0130zleme ekran\u0131nda ye\u015fil bir i\u015faret g\u00f6rmek tek ba\u015f\u0131na yeterli de\u011fildir. Kontrol\u00fcn do\u011fru adresi izledi\u011fini, ar\u0131za s\u0131ras\u0131nda durum de\u011fi\u015ftirdi\u011fini ve bildirimin ger\u00e7ekten ula\u015ft\u0131\u011f\u0131n\u0131 da s\u0131namak gerekir. Rehberin uygulama b\u00f6l\u00fcm\u00fc bu \u00fc\u00e7 noktay\u0131 birlikte ele al\u0131r.<\/p>\n<h2 id=\"test-ortami\">Test ortam\u0131 ve gerekenler<\/h2>\n<p>Bu kurulum yolu, \u00e7al\u0131\u015fan bir Coolify paneli ve sunucu ba\u011flant\u0131s\u0131 gerektirir. Temiz bir VPS ile ba\u015fl\u0131yorsan\u0131z \u00f6nce <a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/coolify-kurulumu-vps\/\">Coolify kurulumu ve ilk uygulamay\u0131 yay\u0131nlama<\/a> rehberini tamamlay\u0131n. Burada mevcut proxy&#8217;yi kullanaca\u011f\u0131z; ayn\u0131 80 ve 443 portlar\u0131na ikinci bir web sunucusu kurmayaca\u011f\u0131z.<\/p>\n<p>Kurulum 31 Ekim 2026&#8217;da Ubuntu 24.04.5 LTS, 2 vCPU ve 4 GB plan belle\u011fi bulunan bir FibaCloud VPS \u00fczerinde yap\u0131ld\u0131. Ayn\u0131 VPS&#8217;te mevcut Coolify kurulumu kullan\u0131ld\u0131; izlenecek test uygulamas\u0131 ayr\u0131 bir VPS&#8217;e kuruldu. Bu yap\u0131land\u0131rma bir kapasite s\u0131n\u0131r\u0131 veya belirli say\u0131da siteyi izleme garantisi de\u011fildir.<\/p>\n<table>\n<thead>\n<tr>\n<th>Bile\u015fen<\/th>\n<th>Do\u011frulanan s\u00fcr\u00fcm veya se\u00e7im<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Uptime Kuma<\/td>\n<td>2.5.9; resm\u00ee rootless imaj, digest ile sabitlenmi\u015f.<\/td>\n<\/tr>\n<tr>\n<td>Veritaban\u0131<\/td>\n<td>\u0130lk kurulum ekran\u0131nda SQLite se\u00e7ildi.<\/td>\n<\/tr>\n<tr>\n<td>Coolify<\/td>\n<td>4.5.3.<\/td>\n<\/tr>\n<tr>\n<td>Docker \/ Compose<\/td>\n<td>29.9.2 \/ 5.6.1.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Do\u011frulanan sonu\u00e7:<\/strong> HTTPS ve iki a\u015famal\u0131 giri\u015f, canl\u0131 WebSocket ba\u011flant\u0131s\u0131, iki HTTP\/HTTPS monitoru, ger\u00e7ek 503 kesintisinde Down\/Up webhook teslimat\u0131, herkese a\u00e7\u0131k durum sayfas\u0131 ve t\u00fcm veri yede\u011finden ayn\u0131 sunucuda geri d\u00f6n\u00fc\u015f s\u0131nand\u0131. Kurulum 31 Ekim\u2019de ba\u015flad\u0131; son kontroller T\u00fcrkiye saatiyle 1 Kas\u0131m 2026\u2019da tamamland\u0131.<\/p>\n<ul>\n<li>Coolify&#8217;de proje ve kaynak olu\u015fturma yetkisi; VPS \u00fczerinde SSH ve y\u00f6netici eri\u015fimi.<\/li>\n<li>VPS&#8217;in genel IP adresine y\u00f6nlenmi\u015f bir alt alan ad\u0131. \u00d6rnekte <code>uptime.example.com<\/code> kullan\u0131l\u0131yor; bunu kendi adresinizle de\u011fi\u015ftirin. Yanl\u0131\u015f bir IPv6 adresine giden AAAA kayd\u0131 varsa d\u00fczeltin.<\/li>\n<li>\u0130zleme i\u00e7in size ait bir web adresi ve kesinti testini g\u00fcvenle yapabilece\u011finiz ayr\u0131 bir test uygulamas\u0131.<\/li>\n<li>Bildirim do\u011frulamas\u0131 i\u00e7in kontrol\u00fcn\u00fczdeki bir webhook al\u0131c\u0131s\u0131. Bu rehberde ba\u015fkas\u0131na ait bir bildirim adresi veya genel webhook toplama hizmeti kullan\u0131lmaz.<\/li>\n<li>Veri yede\u011fi i\u00e7in yeterli disk alan\u0131 ve sunucu d\u0131\u015f\u0131ndaki \u00f6zel bir kopya konumu.<\/li>\n<\/ul>\n<p>SSH ba\u011flant\u0131s\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<\/a> rehberine bakabilirsiniz. \u0130maj, konteyner ve volume ayr\u0131m\u0131 yeni geliyorsa <a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/docker-ile-uygulama-nasil-dagitilir\/\">Docker kurulumu ve uygulama da\u011f\u0131t\u0131m\u0131<\/a> rehberi yararl\u0131 olacakt\u0131r.<\/p>\n<h2 id=\"izleme-yerlesimi\">Uptime Kuma&#8217;y\u0131 nereye kurmal\u0131s\u0131n\u0131z?<\/h2>\n<p>Uptime Kuma, kontrol iste\u011fini \u00e7al\u0131\u015ft\u0131\u011f\u0131 sunucudan g\u00f6nderir. \u0130zledi\u011finiz uygulamayla ayn\u0131 VPS&#8217;te oldu\u011funda uygulaman\u0131n hata vermesini g\u00f6rebilir; ancak VPS tamamen kapan\u0131rsa izleyici de kapan\u0131r ve yeni bildirim g\u00f6nderemez. D\u0131\u015far\u0131dan eri\u015filebilirli\u011fi izlemek i\u00e7in Kuma&#8217;y\u0131 hedefinizden ba\u011f\u0131ms\u0131z bir sunucuya, m\u00fcmk\u00fcnse ayn\u0131 a\u011f veya sa\u011flay\u0131c\u0131 ar\u0131zas\u0131ndan etkilenmeyecek bir konuma yerle\u015ftirin.<\/p>\n<p>HTTP kontrol\u00fc bir adresin verdi\u011fi yan\u0131t\u0131 \u00f6l\u00e7er. Ana sayfan\u0131n 200 d\u00f6nmesi; oturum a\u00e7ma, \u00f6deme veya veritaban\u0131na yazma i\u015flemlerinin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 kan\u0131tlamaz. Uygulaman\u0131z\u0131n ger\u00e7ekten kulland\u0131\u011f\u0131 ba\u011f\u0131ml\u0131l\u0131klar\u0131 de\u011ferlendiren, hassas veri d\u00f6nd\u00fcrmeyen bir sa\u011fl\u0131k adresi varsa onu da ayr\u0131 bir monitor olarak ekleyebilirsiniz.<\/p>\n<table>\n<thead>\n<tr>\n<th>Kontrol<\/th>\n<th>Ne g\u00f6sterir?<\/th>\n<th>Tek ba\u015f\u0131na neyi g\u00f6stermez?<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>HTTP\/HTTPS<\/td>\n<td>Se\u00e7ti\u011finiz URL&#8217;nin kabul edilen bir HTTP yan\u0131t\u0131 verip vermedi\u011fini.<\/td>\n<td>T\u00fcm kullan\u0131c\u0131 i\u015flemlerinin ba\u015far\u0131l\u0131 oldu\u011funu.<\/td>\n<\/tr>\n<tr>\n<td>Uygulama sa\u011fl\u0131k adresi<\/td>\n<td>Sa\u011fl\u0131k adresinin s\u0131nad\u0131\u011f\u0131 ba\u011f\u0131ml\u0131l\u0131klar\u0131n durumunu.<\/td>\n<td>Sa\u011fl\u0131k kontrol\u00fcne dahil edilmemi\u015f i\u015f ak\u0131\u015flar\u0131n\u0131.<\/td>\n<\/tr>\n<tr>\n<td>Durum sayfas\u0131<\/td>\n<td>Payla\u015fmay\u0131 se\u00e7ti\u011finiz kontrolleri ve yazd\u0131\u011f\u0131n\u0131z olay duyurular\u0131n\u0131.<\/td>\n<td>\u0130zleyicinin kendisi eri\u015filemiyorsa ba\u011f\u0131ms\u0131z kesinti ileti\u015fimini.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Bu rehberin testinde Kuma ile hedef uygulama ayr\u0131 VPS&#8217;lerde \u00e7al\u0131\u015f\u0131r. \u0130zleme sunucusundan hedefin <code>\/health<\/code> adresine eri\u015fim ve HTTP 200 yan\u0131t\u0131 do\u011fruland\u0131. Kontroll\u00fc kesintiyi bu hedef \u00fczerinde olu\u015fturaca\u011f\u0131z. Sunucular\u0131n ayr\u0131 olmas\u0131, ayn\u0131 sa\u011flay\u0131c\u0131y\u0131 veya ortak a\u011f ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 payla\u015fmad\u0131klar\u0131 anlam\u0131na gelmez.<\/p>\n<h2 id=\"compose-kurulumu\">Coolify&#8217;de Uptime Kuma servisini olu\u015fturun<\/h2>\n<p>Bu ak\u0131\u015fta Docker Compose tan\u0131m\u0131n\u0131 Coolify&#8217;ye gireriz. B\u00f6ylece \u00e7al\u0131\u015ft\u0131r\u0131lan imaj ve kal\u0131c\u0131 veri ba\u011flant\u0131s\u0131 ayn\u0131 kaynakta g\u00f6r\u00fcn\u00fcr. Uptime Kuma&#8217;n\u0131n HTTP kontrolleri i\u00e7in Docker socket ba\u011flant\u0131s\u0131na gerek yoktur.<\/p>\n<ol>\n<li><strong>Projects<\/strong> b\u00f6l\u00fcm\u00fcnde izleme i\u00e7in bir proje olu\u015fturun veya mevcut projenizi a\u00e7\u0131n. Testte <code>FibaCloud Monitoring Lab<\/code> projesi olu\u015fturuldu; <code>production<\/code> ortam\u0131 otomatik olarak haz\u0131r geldi.<\/li>\n<li>Bu ortamda <strong>New Resource<\/strong> d\u00fc\u011fmesine bas\u0131n.<\/li>\n<li><strong>Docker Compose<\/strong> kart\u0131ndaki <strong>Deploy<\/strong> d\u00fc\u011fmesini se\u00e7in. Bu kart, Git deposu ba\u011flamadan bir Compose tan\u0131m\u0131yla servis olu\u015fturur.<\/li>\n<\/ol>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-uptime-kuma-20261031\/uptime-kuma-project.png\" alt=\"FibaCloud Monitoring Lab projesinin bo\u015f production ortam\u0131 ve New Resource d\u00fc\u011fmesi.\" width=\"1152\" height=\"321\"  decoding=\"async\"><figcaption>\u0130zleme servisi, yeni projenin production ortam\u0131na eklenecek.<\/figcaption><\/figure>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-uptime-kuma-20261031\/uptime-kuma-compose-resource.png\" alt=\"Coolify Docker Compose kaynak kart\u0131 ve Deploy d\u00fc\u011fmesi.\" width=\"380\" height=\"219\"  decoding=\"async\"><figcaption>Servis tan\u0131m\u0131n\u0131 do\u011frudan girmek i\u00e7in Docker Compose kayna\u011f\u0131n\u0131 kullan\u0131n.<\/figcaption><\/figure>\n<p><strong>Docker Compose file<\/strong> alan\u0131na a\u015fa\u011f\u0131daki tan\u0131m\u0131 yap\u0131\u015ft\u0131r\u0131p <strong>Create Service<\/strong> ile servisi olu\u015fturun. Bu tan\u0131m temiz bir kurulum ve yeni bir volume i\u00e7indir. \u0130lk a\u015famada alan ad\u0131 yay\u0131nlamaz; 13001 portunu yaln\u0131z VPS&#8217;in kendi loopback adresine ba\u011flar.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>services:\n  uptime-kuma:\n    image: louislam\/uptime-kuma:2.5.9-rootless@sha256:ea1b2ceb6ef710a3d0d994debcc8cded062e534fb901f6e895f59caad68e0a9e\n    restart: unless-stopped\n    ports:\n      - \"127.0.0.1:13001:3001\"\n    volumes:\n      - uptime-kuma-data:\/app\/data\n    security_opt:\n      - no-new-privileges:true\n    labels:\n      - \"traefik.enable=false\"\n\nvolumes:\n  uptime-kuma-data:\n<\/code><\/pre>\n<\/div>\n<p><strong>General \u2192 Service name<\/strong> alan\u0131nda anla\u015f\u0131l\u0131r bir ad se\u00e7in; testte <code>FibaCloud Uptime Kuma<\/code> kullan\u0131ld\u0131. <strong>Save changes<\/strong> ile kaydedin. <strong>Network attachment<\/strong> se\u00e7imini <strong>Use the stack network only<\/strong> olarak b\u0131rak\u0131n.<\/p>\n<p><strong>Domains<\/strong> b\u00f6l\u00fcm\u00fcnde hen\u00fcz bir domain olmad\u0131\u011f\u0131n\u0131 kontrol edin. <code>traefik.enable=false<\/code> sat\u0131r\u0131n\u0131 bu a\u015famada koruyun ve <strong>Deploy<\/strong> d\u00fc\u011fmesine bas\u0131n. Servis ba\u015flayana kadar <strong>Runtime Logs<\/strong> ve kaynak durumunu izleyin. \u0130lk \u00e7al\u0131\u015ft\u0131rmada veritaban\u0131 se\u00e7im ekran\u0131n\u0131n kullan\u0131c\u0131 i\u015flemini beklemesi normaldir.<\/p>\n<p>Testte imaj\u0131n <code>node<\/code> kullan\u0131c\u0131s\u0131yla, UID\/GID <code>1000:1000<\/code> alt\u0131nda \u00e7al\u0131\u015ft\u0131\u011f\u0131; yeni veri volume&#8217;unun yaz\u0131labilir oldu\u011fu ve servis sa\u011fl\u0131k kontrol\u00fcn\u00fcn ge\u00e7ti\u011fi do\u011fruland\u0131. Volume i\u00e7in ek bir root konteyneri veya elle sahiplik de\u011fi\u015ftirme ad\u0131m\u0131 gerekmedi. Bu sonu\u00e7 mevcut bir v1 veri dizinini rootless imaja ta\u015f\u0131may\u0131 kapsamaz.<\/p>\n<p><code>\/app\/data<\/code>, Uptime Kuma&#8217;n\u0131n kal\u0131c\u0131 verisini i\u00e7erir. Konteyner yeniden olu\u015fturulurken ayn\u0131 volume&#8217;un ba\u011fl\u0131 kalmas\u0131 gerekir. Veriyi konteynerin ge\u00e7ici dosya sisteminde b\u0131rakmay\u0131n; resm\u00ee kurulum belgesi NFS gibi a\u011f dosya sistemlerini desteklenen veri konumu olarak kabul etmez.<\/p>\n<h3 id=\"ilk-hesap\">\u0130lk y\u00f6netici hesab\u0131n\u0131 koruyarak olu\u015fturun<\/h3>\n<p>Yeni kurulumun ilk hesap ekran\u0131n\u0131 herkese a\u00e7\u0131k b\u0131rakmay\u0131n. \u00d6nce yaln\u0131z size a\u00e7\u0131k ba\u011flant\u0131 \u00fczerinden y\u00f6netici hesab\u0131n\u0131 olu\u015fturun; ard\u0131ndan HTTPS alan ad\u0131n\u0131 yay\u0131nlay\u0131n. Parolay\u0131 benzersiz se\u00e7in ve bir parola y\u00f6neticisinde saklay\u0131n.<\/p>\n<p>A\u015fa\u011f\u0131daki komutu VPS \u00fczerinde de\u011fil, kendi bilgisayar\u0131n\u0131zda \u00e7al\u0131\u015ft\u0131r\u0131n. <code>203.0.113.10<\/code> yerine Kuma&#8217;n\u0131n kuruldu\u011fu VPS&#8217;in IP adresini, gerekiyorsa <code>root<\/code> yerine SSH kullan\u0131c\u0131n\u0131z\u0131 yaz\u0131n. Terminal a\u00e7\u0131k kalmal\u0131d\u0131r:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>ssh -N -L 127.0.0.1:13001:127.0.0.1:13001 root@203.0.113.10\n<\/code><\/pre>\n<\/div>\n<p>Taray\u0131c\u0131da <code>http:\/\/localhost:13001<\/code> adresini a\u00e7\u0131n. Taray\u0131c\u0131 ile uzak sunucu aras\u0131ndaki eri\u015fim bu SSH t\u00fcnelinden ge\u00e7er. Bilgisayar\u0131n\u0131zdaki 13001 portu doluysa yaln\u0131z ilk yerel portu de\u011fi\u015ftirin ve taray\u0131c\u0131da da ayn\u0131 yeni portu kullan\u0131n.<\/p>\n<ol>\n<li>\u0130lk ekranda <strong>Which database would you like to use?<\/strong> sorusu a\u00e7\u0131l\u0131r. Bu rehberin tek veritaban\u0131 dosyal\u0131 kurulumu i\u00e7in <strong>SQLite<\/strong> se\u00e7in.<\/li>\n<li><strong>Next<\/strong> ile ilerleyin. Veritaban\u0131 haz\u0131rland\u0131\u011f\u0131nda <strong>Create your admin account<\/strong> formu a\u00e7\u0131l\u0131r.<\/li>\n<li><strong>Username<\/strong>, <strong>Password<\/strong> ve <strong>Repeat Password<\/strong> alanlar\u0131n\u0131 doldurup <strong>Create<\/strong> d\u00fc\u011fmesine bas\u0131n.<\/li>\n<li><strong>Dashboard<\/strong> a\u00e7\u0131ld\u0131\u011f\u0131n\u0131 kontrol edin. Yeni kurulumda <strong>No Monitors, please add one<\/strong> mesaj\u0131 g\u00f6r\u00fcl\u00fcr; hen\u00fcz bir monitor olu\u015fturmad\u0131\u011f\u0131n\u0131z i\u00e7in bu beklenen durumdur.<\/li>\n<\/ol>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-uptime-kuma-20261031\/uptime-kuma-database-sqlite.png\" alt=\"Uptime Kuma ilk kurulum ekran\u0131nda SQLite se\u00e7imi ve Next d\u00fc\u011fmesi.\" width=\"640\" height=\"665\"  decoding=\"async\"><figcaption>Bu kurulumda y\u00f6netici hesab\u0131ndan \u00f6nce SQLite veritaban\u0131 se\u00e7ildi.<\/figcaption><\/figure>\n<p>Testte bu s\u0131ra tamamland\u0131 ve y\u00f6netici olu\u015fturulduktan sonra bo\u015f Dashboard a\u00e7\u0131ld\u0131. \u0130lk kurulum boyunca do\u011frudan eri\u015fim <code>127.0.0.1:13001<\/code> ile s\u0131n\u0131rl\u0131 kald\u0131; herkese a\u00e7\u0131k proxy rotas\u0131 hen\u00fcz eklenmemi\u015fti.<\/p>\n<p>Hesap olu\u015fturulduktan sonra <strong>Settings \u2192 Security \u2192 2FA Settings<\/strong> b\u00f6l\u00fcm\u00fcn\u00fc a\u00e7\u0131n. A\u00e7\u0131lan pencerede <strong>Current Password<\/strong> alan\u0131na parolan\u0131z\u0131 girip <strong>Enable 2FA<\/strong> d\u00fc\u011fmesine bas\u0131n. Olu\u015fan QR kodunu kimlik do\u011frulama uygulaman\u0131zla taray\u0131n; uygulamadaki kodu girip <strong>Verify Token \u2192 Save \u2192 Yes<\/strong> s\u0131ras\u0131n\u0131 tamamlay\u0131n. Testte durum <strong>Active<\/strong> oldu. QR kodunu veya kurulum anahtar\u0131n\u0131 ortak dok\u00fcmanlara koymay\u0131n.<\/p>\n<p>Oturum a\u00e7abildi\u011finizi ayr\u0131ca s\u0131nay\u0131n: testte yeni bir HTTPS oturumunda kullan\u0131c\u0131 ad\u0131 ve parola girildikten sonra <strong>Token<\/strong> ekran\u0131 istendi; ge\u00e7erli kodla <strong>Log in<\/strong> se\u00e7ildi\u011finde Dashboard a\u00e7\u0131ld\u0131.<\/p>\n<h3 id=\"alan-adi-https\">Alan ad\u0131 ve HTTPS ba\u011flant\u0131s\u0131n\u0131 tamamlay\u0131n<\/h3>\n<p>Alt alan ad\u0131n\u0131z\u0131n DNS kayd\u0131n\u0131 Kuma VPS&#8217;ine y\u00f6nlendirin. Coolify&#8217;de servisin <strong>Domains \u2192 Add Domain<\/strong> ekran\u0131n\u0131 a\u00e7\u0131n ve \u015fu alanlar\u0131 doldurun:<\/p>\n<table>\n<thead>\n<tr>\n<th>Alan<\/th>\n<th>De\u011fer<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Service application<\/td>\n<td><code>uptime-kuma<\/code><\/td>\n<\/tr>\n<tr>\n<td>Protocol<\/td>\n<td><code>https<\/code><\/td>\n<\/tr>\n<tr>\n<td>Domain<\/td>\n<td>Kendi alan ad\u0131n\u0131z, \u00f6rne\u011fin <code>uptime.example.com<\/code>; \u015fema veya port eklemeyin.<\/td>\n<\/tr>\n<tr>\n<td>Port<\/td>\n<td><code>3001<\/code><\/td>\n<\/tr>\n<tr>\n<td>Path<\/td>\n<td>Bo\u015f b\u0131rak\u0131n.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Save<\/strong> ile domain&#8217;i kaydedin. <strong>General \u2192 Edit Compose File<\/strong> i\u00e7inden yaln\u0131z ba\u015flang\u0131\u00e7 i\u00e7in ekledi\u011fimiz <code>traefik.enable=false<\/code> etiketini ve art\u0131k bo\u015f kal\u0131yorsa <code>labels:<\/code> sat\u0131r\u0131n\u0131 kald\u0131r\u0131n. Di\u011fer imaj, volume ve port ayarlar\u0131n\u0131 koruyun; Compose de\u011fi\u015fikli\u011fini kaydedip servisi yeniden da\u011f\u0131t\u0131n.<\/p>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-uptime-kuma-20261031\/uptime-kuma-https-domain.png\" alt=\"Coolify Add domain ekran\u0131nda https protokol\u00fc, Uptime Kuma alan ad\u0131 ve 3001 i\u00e7 portu.\" width=\"896\" height=\"362\"  decoding=\"async\"><figcaption>3001, proxy&#8217;nin konteyner i\u00e7inde ula\u015faca\u011f\u0131 porttur; taray\u0131c\u0131 ba\u011flant\u0131s\u0131 normal HTTPS adresini kullan\u0131r.<\/figcaption><\/figure>\n<p>Taray\u0131c\u0131da <code>https:\/\/uptime.example.com<\/code> adresini a\u00e7\u0131n; sonuna <code>:3001<\/code> eklemeyin. <code>127.0.0.1:13001<\/code> ba\u011flant\u0131s\u0131 \u00f6zel bak\u0131m eri\u015fimi i\u00e7in kalabilir. Bunu <code>0.0.0.0<\/code> adresinde yay\u0131nlamak gerekmez.<\/p>\n<p>Test alan ad\u0131 <code>docs-uptime.fibacloud.com<\/code> i\u00e7in 443 portunda g\u00fcvenilir Let\u2019s Encrypt sertifikas\u0131 do\u011fruland\u0131; HTTP eri\u015fimi HTTPS ba\u011flant\u0131s\u0131na y\u00f6nlendi. Yeni taray\u0131c\u0131 oturumunda iki a\u015famal\u0131 giri\u015f tamamland\u0131 ve <code>wss:\/\/<\/code> WebSocket ba\u011flant\u0131s\u0131nda veri al\u0131\u015fveri\u015fi g\u00f6zlendi. B\u00f6ylece yaln\u0131z sayfan\u0131n HTML yan\u0131t\u0131 de\u011fil, panelin canl\u0131 ba\u011flant\u0131s\u0131 da s\u0131nand\u0131.<\/p>\n<p>Uptime Kuma&#8217;n\u0131n aray\u00fcz\u00fc canl\u0131 ba\u011flant\u0131 kullan\u0131r. Sayfa a\u00e7\u0131ld\u0131\u011f\u0131 h\u00e2lde ba\u011flant\u0131 hatas\u0131 g\u00f6steriyorsa yaln\u0131z HTML yan\u0131t\u0131na bakmay\u0131n; proxy&#8217;nin WebSocket ba\u011flant\u0131s\u0131n\u0131 da ge\u00e7irdi\u011fini kontrol edin. Paneli <code>\/uptime<\/code> gibi bir alt dizine yerle\u015ftirmek yerine ayr\u0131 bir alt alan ad\u0131 kullan\u0131n.<\/p>\n<p>Y\u00f6netim paneliyle durum sayfas\u0131 ayn\u0131 alan ad\u0131nda olabilir. Y\u00f6netim alan\u0131 hesab\u0131n\u0131zla korunurken yaln\u0131z se\u00e7ti\u011finiz durum sayfas\u0131 herkese a\u00e7\u0131k olur. Bu ayr\u0131m\u0131, oturumunuzun bulunmad\u0131\u011f\u0131 ayr\u0131 bir taray\u0131c\u0131 penceresinde de kontrol edin.<\/p>\n<h2 id=\"test-hedefi\">Kesinti denemesi i\u00e7in ayr\u0131 bir HTTP hedefi haz\u0131rlay\u0131n<\/h2>\n<p>Kendi web sitenizi normal bi\u00e7imde izlemek i\u00e7in bu k\u00fc\u00e7\u00fck uygulamaya ihtiyac\u0131n\u0131z yoktur. Kesinti ve geri d\u00f6n\u00fc\u015f\u00fc kontroll\u00fc olarak s\u0131namak istiyorsan\u0131z a\u015fa\u011f\u0131daki hedefi ayr\u0131 bir test VPS&#8217;inde \u00e7al\u0131\u015ft\u0131r\u0131n. Hedef, normal durumda <code>\/health<\/code> adresinden 200 d\u00f6ner; yaln\u0131z SSH \u00fczerinden olu\u015fturulan bir bak\u0131m dosyas\u0131 varken 503 yan\u0131t\u0131 verir.<\/p>\n<p><a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-uptime-kuma-20261031\/uptime-kuma-examples.zip\">Test hedefi ve webhook al\u0131c\u0131s\u0131n\u0131n kaynak paketini indirin<\/a>. Paket, bu rehberde \u00e7al\u0131\u015ft\u0131r\u0131lan Python kaynaklar\u0131n\u0131, Dockerfile&#8217;lar\u0131 ve Compose tan\u0131mlar\u0131n\u0131 i\u00e7erir; parola, ger\u00e7ek olay kayd\u0131 veya uygulama yede\u011fi i\u00e7ermez. A\u015fa\u011f\u0131daki komut paket hash&#8217;ini ve i\u00e7indeki kaynak dosyalar\u0131n\u0131n hash&#8217;lerini kontrol eder.<\/p>\n<p>Bu ad\u0131m\u0131 <strong>ikinci VPS \u00fczerinde<\/strong> \u00e7al\u0131\u015ft\u0131r\u0131n. Docker, Compose, <code>curl<\/code> ve <code>unzip<\/code> haz\u0131r olmal\u0131d\u0131r. Yeni dizin, konteyner, imaj etiketi, a\u011f veya 18889 portu zaten kullan\u0131l\u0131yorsa komut durur; var olan kurulumu silerek devam etmeyin.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>sudo bash &lt;&lt;'TARGET_SETUP'\nset -euo pipefail\numask 077\nif [ -e \/root\/fibacloud-uptime-target ] || \\\n   docker container inspect fibacloud-uptime-target &gt;\/dev\/null 2&gt;&amp;1 || \\\n   docker image inspect fibacloud-uptime-target:20261031 &gt;\/dev\/null 2&gt;&amp;1 || \\\n   docker network inspect fibacloud-uptime-target_default &gt;\/dev\/null 2&gt;&amp;1; then\n  echo 'Example namespace already exists; inspect it before continuing.' &gt;&amp;2\n  exit 1\nfi\nif [ -n \"$(ss -H -ltn 'sport = :18889')\" ]; then\n  echo 'TCP 18889 is already in use.' &gt;&amp;2\n  exit 1\nfi\ninstall -d -m 0700 \/root\/fibacloud-uptime-target\ncd \/root\/fibacloud-uptime-target\ncurl -fSL 'https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-uptime-kuma-20261031\/uptime-kuma-examples.zip' -o examples.zip\nprintf '%s  examples.zip\\n' '74f3d8808903f7d53266ebff1ce056fc5185eae1027031b190a688c57b9e959d' | sha256sum -c -\nunzip -q examples.zip -d package\n(cd package &amp;&amp; sha256sum -c SHA256SUMS)\ninstall -m 0600 package\/target\/Dockerfile package\/target\/compose.yaml package\/target\/target.py .\ninstall -d -m 0755 state\ndocker compose config --quiet\ndocker compose up -d --build\ndocker compose ps\nTARGET_SETUP\n<\/code><\/pre>\n<\/div>\n<p>Hedef sunucuda HTTP yan\u0131t\u0131n\u0131 kontrol edin:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>curl --retry 10 --retry-connrefused --retry-delay 1 --retry-max-time 30 -fsS http:\/\/127.0.0.1:18889\/health\n<\/code><\/pre>\n<\/div>\n<p>\u00c7al\u0131\u015fan hedefin yan\u0131t\u0131 <code>{\"status\":\"ok\",\"service\":\"fibacloud-uptime-target\"}<\/code> olur. Ard\u0131ndan <strong>Kuma&#8217;n\u0131n bulundu\u011fu VPS&#8217;ten<\/strong> hedefin genel IP adresini kullanarak ba\u011flant\u0131y\u0131 s\u0131nay\u0131n; a\u015fa\u011f\u0131daki \u00f6rnek IP&#8217;yi kendi ikinci VPS&#8217;inizle de\u011fi\u015ftirin:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>curl -fsS -w '\\nHTTP %{http_code}\\n' http:\/\/203.0.113.20:18889\/health\n<\/code><\/pre>\n<\/div>\n<p>Bu testte ayr\u0131 VPS&#8217;ten HTTP 200 do\u011fruland\u0131. Eri\u015fim yoksa hedef sunucunun ve sa\u011flay\u0131c\u0131n\u0131n a\u011f kurallar\u0131nda 18889\/TCP ba\u011flant\u0131s\u0131n\u0131 kontrol edin. Bu porta yaln\u0131z sabit test yan\u0131t\u0131 sunulur; ger\u00e7ek uygulaman\u0131z\u0131n sa\u011fl\u0131k adresini kendi HTTPS yap\u0131land\u0131rmas\u0131yla izleyin.<\/p>\n<h2 id=\"http-monitor\">\u0130lk HTTP\/HTTPS kontrol\u00fcn\u00fc ekleyin<\/h2>\n<p>Kontrole a\u00e7\u0131klay\u0131c\u0131 bir ad verin. Birden fazla uygulama izlerken yaln\u0131z <code>Website<\/code> yerine <code>M\u00fc\u015fteri paneli \u2014 giri\u015f sayfas\u0131<\/code> veya <code>API \u2014 sa\u011fl\u0131k kontrol\u00fc<\/code> gibi isimler, bildirimin hangi bile\u015fene ait oldu\u011funu anlamay\u0131 kolayla\u015ft\u0131r\u0131r.<\/p>\n<p><strong>Add New Monitor<\/strong> d\u00fc\u011fmesine bas\u0131n. <strong>Monitor Type<\/strong> alan\u0131nda <strong>HTTP(s)<\/strong> se\u00e7in; <strong>Friendly Name<\/strong> alan\u0131na ad\u0131n\u0131 ve <strong>URL<\/strong> alan\u0131na kendi kontrol adresinizi yaz\u0131n. Testte iki ayr\u0131 kay\u0131t olu\u015fturuldu:<\/p>\n<table>\n<thead>\n<tr>\n<th>Monitor<\/th>\n<th>Kontrol edilen hedef<\/th>\n<th>Kapsam<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Independent HTTP endpoint<\/td>\n<td>Ayr\u0131 VPS&#8217;teki <code>http:\/\/194.116.236.155:18889\/health<\/code><\/td>\n<td>Kontroll\u00fc 503 kesinti testi. Bu a\u00e7\u0131k HTTP adresi gizli veri ta\u015f\u0131maz; sertifika kontrol\u00fc s\u0131namaz.<\/td>\n<\/tr>\n<tr>\n<td>Coolify HTTPS application<\/td>\n<td><code>https:\/\/docs-coolify-app.fibacloud.com\/health<\/code><\/td>\n<td>\u00d6nceki Coolify rehberindeki uygulaman\u0131n HTTPS yan\u0131t\u0131. Bu uygulama Kuma ile ayn\u0131 VPS&#8217;tedir; o VPS&#8217;in tamamen kapanmas\u0131n\u0131 ba\u011f\u0131ms\u0131z izleyemez.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Bu adresler rehberin test ortam\u0131n\u0131 g\u00f6sterir. Kendi kurulumunuzda kendi hedeflerinizi kullan\u0131n; yukar\u0131daki ayr\u0131 test hedefinin adresini ilk monitor i\u00e7in kullanabilirsiniz.<\/p>\n<table>\n<thead>\n<tr>\n<th>Ayar<\/th>\n<th>Testte kullan\u0131lan de\u011fer<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Heartbeat Interval<\/td>\n<td><code>60<\/code> saniye<\/td>\n<\/tr>\n<tr>\n<td>Retries<\/td>\n<td><code>1<\/code><\/td>\n<\/tr>\n<tr>\n<td>Heartbeat Retry Interval<\/td>\n<td><code>20<\/code> saniye<\/td>\n<\/tr>\n<tr>\n<td>Request Timeout<\/td>\n<td><code>5<\/code> saniye<\/td>\n<\/tr>\n<tr>\n<td>Resend Notification if Down X times consecutively<\/td>\n<td><code>0<\/code>; kesinti s\u00fcrerken tekrar g\u00f6nderim kapal\u0131.<\/td>\n<\/tr>\n<tr>\n<td>HTTP Options \u2192 Method<\/td>\n<td><code>GET<\/code><\/td>\n<\/tr>\n<tr>\n<td>Accepted Status Codes<\/td>\n<td><code>200-299<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-uptime-kuma-20261031\/uptime-kuma-monitor-settings.png\" alt=\"Ger\u00e7ek HTTP monitor ayarlar\u0131nda 60 saniye aral\u0131k, bir yeniden deneme, 20 saniye deneme aral\u0131\u011f\u0131 ve 5 saniye zaman a\u015f\u0131m\u0131.\" width=\"475\" height=\"855\"  decoding=\"async\"><figcaption>Kesinti testi bu kay\u0131tta se\u00e7ilen kontrol ve yeniden deneme de\u011ferleriyle yap\u0131l\u0131r.<\/figcaption><\/figure>\n<p>HTTPS hedefinde <strong>Certificate Expiry Notification<\/strong> etkinle\u015ftirildi; <strong>Ignore TLS\/SSL errors for HTTPS websites<\/strong> kapal\u0131 b\u0131rak\u0131ld\u0131. Sertifika hatalar\u0131n\u0131 gizleyerek ye\u015fil durum elde etmeyin. Bu rehberde s\u00fcresi ge\u00e7mi\u015f sertifika \u00fcretip alarm denemesi yap\u0131lmad\u0131; etkinle\u015ftirilen ayarla ger\u00e7ek HTTPS eri\u015fimi kontrol edildi. <strong>Domain Name Expiry Notification<\/strong> iki kontrolde de kapal\u0131d\u0131r.<\/p>\n<p><strong>Save<\/strong> ile kaydedin ve ilk kontrol\u00fcn tamamlanmas\u0131n\u0131 bekleyin. Yeni monitor i\u00e7in varsay\u0131lanlar\u0131 tahmin etmek yerine yukar\u0131daki alanlar\u0131 a\u00e7\u0131k\u00e7a se\u00e7in.<\/p>\n<p>Kontrol aral\u0131\u011f\u0131, yeni iste\u011fin ne s\u0131kl\u0131kla g\u00f6nderilece\u011fini belirler. Zaman a\u015f\u0131m\u0131, bir iste\u011fe ne kadar s\u00fcre tan\u0131naca\u011f\u0131n\u0131; yeniden deneme say\u0131s\u0131 ise ilk ba\u015far\u0131s\u0131zl\u0131ktan sonra durumun de\u011fi\u015fmesinden \u00f6nceki ek denemeleri etkiler. Daha k\u0131sa aral\u0131klar daha fazla istek \u00fcretir. Beklenen yan\u0131t s\u00fcresine ve uyar\u0131 ihtiyac\u0131n\u0131za g\u00f6re se\u00e7im yap\u0131n; a\u015f\u0131r\u0131 k\u0131sa de\u011ferler ge\u00e7ici a\u011f gecikmelerinde gereksiz alarm olu\u015fturabilir.<\/p>\n<p>\u0130zledi\u011finiz adres normalde 200 d\u00f6n\u00fcyorsa bu davran\u0131\u015f\u0131 do\u011frulay\u0131n. Hata sayfas\u0131n\u0131 200 durum koduyla sunan bir uygulama, basit HTTP kontrol\u00fcnde \u00e7al\u0131\u015f\u0131yor g\u00f6r\u00fcnebilir. B\u00f6yle bir uygulama i\u00e7in do\u011fru sa\u011fl\u0131k adresini veya yan\u0131t i\u00e7eri\u011fini de\u011ferlendiren ayr\u0131 bir kontrol se\u00e7in.<\/p>\n<p>\u0130ki monitor de ilk kontrolde HTTP 200 yan\u0131t\u0131yla <strong>Up<\/strong> durumuna ge\u00e7ti. A\u015fa\u011f\u0131daki g\u00f6r\u00fcnt\u00fc ayr\u0131 VPS&#8217;teki HTTP hedefinin ilk ba\u015far\u0131l\u0131 kontrol\u00fcnden al\u0131nm\u0131\u015ft\u0131r.<\/p>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-uptime-kuma-20261031\/uptime-kuma-monitor-up.png\" alt=\"Independent HTTP endpoint kontrol\u00fcn\u00fcn ger\u00e7ek URL'si, 60 saniye kontrol aral\u0131\u011f\u0131 ve Up durumu.\" width=\"950\" height=\"350\"  decoding=\"async\"><figcaption>\u0130lk ba\u015far\u0131l\u0131 kontrol, HTTP hedefinin eri\u015filebilir oldu\u011funu g\u00f6steriyor.<\/figcaption><\/figure>\n<p>Yeni kurulmu\u015f bir monitordaki y\u00fczde de\u011ferleri uzun d\u00f6nem hizmet ge\u00e7mi\u015fi de\u011fildir. Hen\u00fcz bir g\u00fcnl\u00fck veri olu\u015fmadan g\u00f6r\u00fclen 24 saat, 30 g\u00fcn veya bir y\u0131l ba\u015fl\u0131klar\u0131n\u0131 o s\u00fcre boyunca yap\u0131lm\u0131\u015f \u00f6l\u00e7\u00fcm gibi yorumlamay\u0131n.<\/p>\n<h2 id=\"webhook-bildirimi\">Webhook bildirimi ekleyin ve ger\u00e7ekten ula\u015ft\u0131\u011f\u0131n\u0131 kontrol edin<\/h2>\n<p>Webhook, durum de\u011fi\u015fti\u011finde se\u00e7ti\u011finiz adrese HTTP iste\u011fi g\u00f6nderir. Uptime Kuma bildirim ayarlar\u0131n\u0131 kaydetmek ile al\u0131c\u0131n\u0131n iste\u011fi i\u015flemesi farkl\u0131 a\u015famalard\u0131r. Testi hem Kuma aray\u00fcz\u00fcnden hem al\u0131c\u0131n\u0131n kayd\u0131ndan kontrol edin.<\/p>\n<h3 id=\"webhook-alicisi\">\u00d6zel test al\u0131c\u0131s\u0131n\u0131 \u00e7al\u0131\u015ft\u0131r\u0131n<\/h3>\n<p>Kaynak paketindeki al\u0131c\u0131y\u0131 <strong>Kuma&#8217;n\u0131n bulundu\u011fu VPS&#8217;e<\/strong> kurun. Bu k\u00fc\u00e7\u00fck servis yaln\u0131z \u00f6zel Docker a\u011f\u0131nda \u00e7al\u0131\u015f\u0131r; genel IP&#8217;de port a\u00e7maz. Gelen bildirimin t\u00fcr\u00fcn\u00fc, zaman\u0131n\u0131 ve durumunu kaydederek iste\u011fin ger\u00e7ekten ula\u015ft\u0131\u011f\u0131n\u0131 kontrol etmemizi sa\u011flar.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>sudo bash &lt;&lt;'RECEIVER_SETUP'\nset -euo pipefail\numask 077\nif [ -e \/root\/fibacloud-uptime-lab ] || \\\n   docker container inspect fibacloud-uptime-webhook &gt;\/dev\/null 2&gt;&amp;1 || \\\n   docker image inspect fibacloud-uptime-webhook:20261031 &gt;\/dev\/null 2&gt;&amp;1 || \\\n   docker network inspect fibacloud-uptime-webhook &gt;\/dev\/null 2&gt;&amp;1 || \\\n   docker volume inspect fibacloud-uptime-webhook-events &gt;\/dev\/null 2&gt;&amp;1; then\n  echo 'Example namespace already exists; inspect it before continuing.' &gt;&amp;2\n  exit 1\nfi\ninstall -d -m 0700 \/root\/fibacloud-uptime-lab\/receiver\ncd \/root\/fibacloud-uptime-lab\/receiver\ncurl -fSL 'https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-uptime-kuma-20261031\/uptime-kuma-examples.zip' -o examples.zip\nprintf '%s  examples.zip\\n' '74f3d8808903f7d53266ebff1ce056fc5185eae1027031b190a688c57b9e959d' | sha256sum -c -\nunzip -q examples.zip -d package\n(cd package &amp;&amp; sha256sum -c SHA256SUMS)\ninstall -m 0600 package\/receiver\/Dockerfile package\/receiver\/compose.yaml package\/receiver\/receiver.py .\ndocker compose config --quiet\ndocker compose up -d --build\ndocker compose ps\nRECEIVER_SETUP\n<\/code><\/pre>\n<\/div>\n<p><code>docker compose ps<\/code> \u00e7\u0131kt\u0131s\u0131nda al\u0131c\u0131 <code>healthy<\/code> oldu\u011funda Coolify&#8217;de Kuma servisinin <strong>General \u2192 Edit Compose File<\/strong> ekran\u0131n\u0131 a\u00e7\u0131n. Y\u00f6netici hesab\u0131n\u0131 \u00f6nceden olu\u015fturdu\u011funuz bu kurulumda, HTTPS domain ayar\u0131n\u0131 koruyarak a\u015fa\u011f\u0131daki tam Compose tan\u0131m\u0131n\u0131 kaydedin:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>services:\n  uptime-kuma:\n    image: louislam\/uptime-kuma:2.5.9-rootless@sha256:ea1b2ceb6ef710a3d0d994debcc8cded062e534fb901f6e895f59caad68e0a9e\n    restart: unless-stopped\n    ports:\n      - \"127.0.0.1:13001:3001\"\n    volumes:\n      - uptime-kuma-data:\/app\/data\n    security_opt:\n      - no-new-privileges:true\n    networks:\n      - webhook\nvolumes:\n  uptime-kuma-data:\nnetworks:\n  webhook:\n    external: true\n    name: fibacloud-uptime-webhook\n<\/code><\/pre>\n<\/div>\n<p><strong>Network attachment<\/strong> alan\u0131n\u0131 <strong>Use the stack network only<\/strong> olarak b\u0131rak\u0131n. <strong>Save changes<\/strong> ile kaydedip servisi yeniden da\u011f\u0131t\u0131n. Kuma kendi kal\u0131c\u0131 volume&#8217;unu kullanmaya devam eder; ek <code>webhook<\/code> a\u011f\u0131 yaln\u0131z \u00f6zel al\u0131c\u0131ya ula\u015fmas\u0131 i\u00e7indir. Coolify kendi proxy a\u011f\u0131na ba\u011flant\u0131y\u0131 y\u00f6netir.<\/p>\n<p>Testte al\u0131c\u0131n\u0131n container sa\u011fl\u0131k kontrol\u00fc ve HTTP 200 yan\u0131t\u0131 do\u011fruland\u0131. Genel a\u011fa yay\u0131nlanan al\u0131c\u0131 portu yoktur; bu nedenle a\u015fa\u011f\u0131daki <code>webhook-receiver<\/code> ad\u0131 taray\u0131c\u0131n\u0131zdan de\u011fil, ayn\u0131 Docker a\u011f\u0131ndaki Kuma servisinden \u00e7\u00f6z\u00fcl\u00fcr.<\/p>\n<h3 id=\"bildirim-ayari\">Bildirimi monitora ba\u011flay\u0131n<\/h3>\n<p><strong>Settings \u2192 Notifications \u2192 Set Up Notification<\/strong> ekran\u0131n\u0131 a\u00e7\u0131n ve a\u015fa\u011f\u0131daki de\u011ferleri girin:<\/p>\n<table>\n<thead>\n<tr>\n<th>Alan<\/th>\n<th>Testteki se\u00e7im<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Notification Type<\/td>\n<td>Webhook<\/td>\n<\/tr>\n<tr>\n<td>Friendly Name<\/td>\n<td>Docs Lab Webhook<\/td>\n<\/tr>\n<tr>\n<td>Post URL<\/td>\n<td><code>http:\/\/webhook-receiver:8080\/events<\/code><\/td>\n<\/tr>\n<tr>\n<td>HTTP Method<\/td>\n<td>POST<\/td>\n<\/tr>\n<tr>\n<td>Request Body<\/td>\n<td><strong>Preset &#8211; application\/json<\/strong><\/td>\n<\/tr>\n<tr>\n<td>Additional Headers<\/td>\n<td>Kapal\u0131; bu al\u0131c\u0131 yaln\u0131z \u00f6zel Docker a\u011f\u0131ndan eri\u015filebilir.<\/td>\n<\/tr>\n<tr>\n<td>Default enabled<\/td>\n<td>Kapal\u0131; yeni monitorlara otomatik atanmaz.<\/td>\n<\/tr>\n<tr>\n<td>Apply on all existing monitors<\/td>\n<td>A\u00e7\u0131k; bu testteki mevcut iki monitora atan\u0131r.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Request Body<\/strong> listesinden <strong>Preset &#8211; application\/json<\/strong> se\u00e7ene\u011fini a\u00e7\u0131k\u00e7a se\u00e7in. Testte ilk a\u00e7\u0131lan formda bu gerekli alan bo\u015f kalm\u0131\u015ft\u0131: <strong>Test<\/strong> iste\u011fi ula\u015fmas\u0131na ra\u011fmen <strong>Save<\/strong> i\u015flemi taray\u0131c\u0131 do\u011frulamas\u0131na tak\u0131ld\u0131. Se\u00e7im yap\u0131ld\u0131ktan sonra bildirim kaydedildi.<\/p>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-uptime-kuma-20261031\/uptime-kuma-webhook-settings.png\" alt=\"Uptime Kuma Webhook formunda POST, JSON g\u00f6vdesi ve mevcut monitorlara atama se\u00e7imi.\" width=\"500\" height=\"922\"  decoding=\"async\"><figcaption>Bu al\u0131c\u0131 URL\u2019si yaln\u0131z rehberde olu\u015fturulan \u00f6zel Docker a\u011f\u0131 i\u00e7indir.<\/figcaption><\/figure>\n<p><strong>Test<\/strong> d\u00fc\u011fmesine bas\u0131n; ba\u015far\u0131l\u0131 sonu\u00e7tan sonra <strong>Save<\/strong> ile kaydedin. Kuma VPS\u2019inde al\u0131c\u0131n\u0131n kay\u0131tlar\u0131n\u0131 okuyun:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>sudo docker exec fibacloud-uptime-webhook cat \/data\/events.jsonl\n<\/code><\/pre>\n<\/div>\n<p>Ger\u00e7ek test iste\u011fi 31 Ekim 2026 saat <code>20:53:25 UTC<\/code> an\u0131nda al\u0131c\u0131ya ula\u015ft\u0131 ve <code>kind: test<\/code> olarak kaydedildi. Bu yaln\u0131z ba\u011flant\u0131 denemesidir; a\u015fa\u011f\u0131daki kesinti testinde ayr\u0131ca Down ve Up olaylar\u0131n\u0131n ula\u015ft\u0131\u011f\u0131n\u0131 do\u011frulayaca\u011f\u0131z. Mevcut b\u00fct\u00fcn monitorlara atamak istemiyorsan\u0131z toplu se\u00e7ene\u011fi kapal\u0131 tutup ilgili monitorun d\u00fczenleme ekran\u0131nda yaln\u0131z istedi\u011finiz bildirimi etkinle\u015ftirin.<\/p>\n<p>Webhook adresi veya ek ba\u015fl\u0131\u011f\u0131 bir eri\u015fim anahtar\u0131 i\u00e7eriyorsa bunu ekran g\u00f6r\u00fcnt\u00fclerinde ve ortak dok\u00fcmanlarda payla\u015fmay\u0131n. Ayn\u0131 al\u0131c\u0131y\u0131 ba\u015fka otomasyonlara ba\u011flarken yaln\u0131z ba\u015far\u0131l\u0131 HTTP yan\u0131t\u0131na g\u00fcvenmeyin; olay\u0131n do\u011fru servise, do\u011fru durumda ve do\u011fru zamanda ula\u015ft\u0131\u011f\u0131n\u0131 da inceleyin.<\/p>\n<p>Bu rehberin bildirim denemesi kontroll\u00fc webhook al\u0131c\u0131s\u0131n\u0131 kapsar. Telegram, Discord veya SMTP gibi ba\u015fka bir y\u00f6ntem se\u00e7erseniz kendi hesab\u0131n\u0131z\u0131n ba\u011flant\u0131 bilgilerini tan\u0131mlay\u0131p o kanala ayr\u0131 bir ger\u00e7ek teslimat testi yap\u0131n.<\/p>\n<h2 id=\"kesinti-testi\">Kontroll\u00fc kesinti ve geri d\u00f6n\u00fc\u015f testi yap\u0131n<\/h2>\n<p>Bu ad\u0131m\u0131 m\u00fc\u015fteri trafi\u011fi alan uygulamada yapmay\u0131n. \u0130zleme amac\u0131yla ay\u0131rd\u0131\u011f\u0131n\u0131z test hedefinin yan\u0131t\u0131n\u0131 ge\u00e7ici olarak ba\u015far\u0131s\u0131z duruma getirin. Kuma&#8217;n\u0131n kendisini veya ortak proxy&#8217;yi durdurmak, uygulama kesintisi testinin kapsam\u0131n\u0131 de\u011fi\u015ftirir.<\/p>\n<p>Bu rehberdeki hedefi kurduysan\u0131z a\u015fa\u011f\u0131daki komutu <strong>ikinci VPS \u00fczerinde<\/strong> \u00e7al\u0131\u015ft\u0131r\u0131n. Yaln\u0131z ayr\u0131lm\u0131\u015f test dizinine bir bak\u0131m dosyas\u0131 ekler; hedef konteyneri yeniden ba\u015flatmaz:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>sudo python3 - &lt;&lt;&#x27;PYTHON&#x27;\nfrom pathlib import Path\nroot = Path(&#x27;\/root\/fibacloud-uptime-target\/state&#x27;)\nassert root.is_dir() and not root.is_symlink()\nflag = root \/ &#x27;maintenance&#x27;\nassert not flag.exists() and not flag.is_symlink()\nwith flag.open(&#x27;x&#x27;) as stream:\n    stream.write(&#x27;Controlled FibaCloud documentation test\\n&#x27;)\nflag.chmod(0o644)\nPYTHON\ncurl -sS -w &#x27;\\nHTTP %{http_code}\\n&#x27; http:\/\/127.0.0.1:18889\/health\n<\/code><\/pre>\n<\/div>\n<p>Yan\u0131t <code>HTTP 503<\/code> olmal\u0131d\u0131r. Kuma panelinde <strong>Independent HTTP endpoint<\/strong> kontrol\u00fcn\u00fc a\u00e7\u0131k tutun. Se\u00e7ti\u011fimiz bir yeniden deneme tamamland\u0131ktan sonra <strong>Down<\/strong> durumunu ve webhook al\u0131c\u0131s\u0131nda <code>status: 0<\/code> kayd\u0131n\u0131 bekleyin. Ard\u0131ndan ayn\u0131 hedef VPS\u2019inde a\u015fa\u011f\u0131daki komutla yaln\u0131z bu denemenin bak\u0131m dosyas\u0131n\u0131 kald\u0131r\u0131n:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>sudo python3 - &lt;&lt;&#x27;PYTHON&#x27;\nfrom pathlib import Path\nroot = Path(&#x27;\/root\/fibacloud-uptime-target\/state&#x27;)\nassert root.is_dir() and not root.is_symlink()\nflag = root \/ &#x27;maintenance&#x27;\nassert flag.is_file() and not flag.is_symlink()\nassert flag.read_text() == &#x27;Controlled FibaCloud documentation test\\n&#x27;\nflag.unlink()\nPYTHON\ncurl -fsS -w &#x27;\\nHTTP %{http_code}\\n&#x27; http:\/\/127.0.0.1:18889\/health\n<\/code><\/pre>\n<\/div>\n<p>Hedef yeniden <code>HTTP 200<\/code> d\u00f6nd\u00fc\u011f\u00fcnde Kuma\u2019n\u0131n sonraki kontrol\u00fcn\u00fc bekleyin. Panelin <strong>Up<\/strong> olmas\u0131 ve al\u0131c\u0131ya <code>status: 1<\/code> gelmesi iki ayr\u0131 do\u011frulamad\u0131r. Al\u0131c\u0131 kay\u0131tlar\u0131n\u0131 bir \u00f6nceki b\u00f6l\u00fcmdeki <code>docker exec<\/code> komutuyla okuyabilirsiniz.<\/p>\n<p>Hedefin hata vermesinden sonraki ilk sorgu, yeniden denemeler ve bildirim teslimat\u0131 ayr\u0131 zamanlard\u0131r. A\u015fa\u011f\u0131daki sonu\u00e7lar bu deneyin se\u00e7ilen ayarlarla g\u00f6zlenen davran\u0131\u015f\u0131n\u0131 g\u00f6sterir; her kesintinin ayn\u0131 s\u00fcrede fark edilece\u011fi anlam\u0131na gelmez.<\/p>\n<table>\n<thead>\n<tr>\n<th>Ger\u00e7ek olay<\/th>\n<th>31 Ekim 2026, UTC<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Hedefte 503 olu\u015fturuldu.<\/td>\n<td>20:56:41.362<\/td>\n<\/tr>\n<tr>\n<td>Kuma Down kaydetti.<\/td>\n<td>20:57:36.285<\/td>\n<\/tr>\n<tr>\n<td>Down webhook\u2019u al\u0131c\u0131ya ula\u015ft\u0131.<\/td>\n<td>20:57:36.348<\/td>\n<\/tr>\n<tr>\n<td>Hedef yeniden 200 durumuna al\u0131nd\u0131.<\/td>\n<td>20:58:36.690<\/td>\n<\/tr>\n<tr>\n<td>Kuma Up kaydetti.<\/td>\n<td>20:59:36.289<\/td>\n<\/tr>\n<tr>\n<td>Up webhook\u2019u al\u0131c\u0131ya ula\u015ft\u0131.<\/td>\n<td>20:59:36.333<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Sunucular\u0131n kaydetti\u011fi saatlere g\u00f6re Down yakla\u015f\u0131k <strong>55 saniye<\/strong>, Up yakla\u015f\u0131k <strong>60 saniye<\/strong> sonra g\u00f6r\u00fcld\u00fc. Bunlar tek kontroll\u00fc deneyin g\u00f6zlemleridir; genel gecikme s\u0131n\u0131r\u0131 veya SLA de\u011fildir. Tabloda UTC kullan\u0131l\u0131r; ekran g\u00f6r\u00fcnt\u00fclerindeki panel saatleri T\u00fcrkiye saatiyle, UTC+3 g\u00f6sterilir.<\/p>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-uptime-kuma-20261031\/uptime-kuma-monitor-down.png\" alt=\"Kontroll\u00fc HTTP 503 sonras\u0131nda ger\u00e7ek Uptime Kuma kontrol\u00fcn\u00fcn Down durumu.\" width=\"940\" height=\"350\"  decoding=\"async\"><figcaption>Ayr\u0131 test hedefi hata verirken kontrol Down durumuna ge\u00e7ti.<\/figcaption><\/figure>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-uptime-kuma-20261031\/uptime-kuma-recovery-history.png\" alt=\"Uptime Kuma ge\u00e7mi\u015finde ilk Up, HTTP 503 nedeniyle Down ve HTTP 200 ile yeniden Up kay\u0131tlar\u0131.\" width=\"940\" height=\"560\"  decoding=\"async\"><figcaption>Ge\u00e7mi\u015fte kesinti ve normale d\u00f6n\u00fc\u015f birlikte g\u00f6r\u00fcl\u00fcr; bildirim al\u0131c\u0131s\u0131 her iki olay\u0131 ayr\u0131ca kaydetti.<\/figcaption><\/figure>\n<p>Test tamamland\u0131\u011f\u0131nda hedefi yeniden sa\u011fl\u0131kl\u0131 duruma al\u0131n. Kontrol\u00fcn tekrar <strong>Up<\/strong> oldu\u011funu ve kurtarma bildiriminin de al\u0131c\u0131ya ula\u015ft\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n. Yaln\u0131z ilk alarm\u0131n \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 g\u00f6rmek, normale d\u00f6n\u00fc\u015f ak\u0131\u015f\u0131n\u0131 do\u011frulamaz.<\/p>\n<h2 id=\"durum-sayfasi\">Herkese a\u00e7\u0131k durum sayfas\u0131 olu\u015fturun<\/h2>\n<p>Durum sayfas\u0131na yaln\u0131z payla\u015f\u0131lmas\u0131nda sak\u0131nca olmayan kontrolleri ekleyin. \u0130\u00e7 a\u011f adlar\u0131, \u00f6zel y\u00f6netim u\u00e7lar\u0131 veya m\u00fc\u015fteri isimleri i\u00e7eren monitor adlar\u0131n\u0131 herkese a\u00e7madan \u00f6nce g\u00f6zden ge\u00e7irin. Kullan\u0131c\u0131ya hizmetin ad\u0131n\u0131 ve mevcut durumunu anlatmak genellikle yeterlidir.<\/p>\n<ol>\n<li>\u00dcst men\u00fcde <strong>Status Pages<\/strong> b\u00f6l\u00fcm\u00fcnden yeni durum sayfas\u0131 olu\u015fturun.<\/li>\n<li><strong>Add New Status Page<\/strong> formunda <strong>Name<\/strong> ve <strong>Slug<\/strong> girip <strong>Next<\/strong> d\u00fc\u011fmesine bas\u0131n. Testte ad <code>FibaCloud Docs Lab Status<\/code>, slug <code>docs-lab<\/code> se\u00e7ildi.<\/li>\n<li>D\u00fczenleme ekran\u0131nda <strong>Title<\/strong> ve <strong>Description<\/strong> alanlar\u0131n\u0131 g\u00f6zden ge\u00e7irin. Test sayfas\u0131n\u0131n a\u00e7\u0131klamas\u0131nda bunun dok\u00fcmantasyon denemesi oldu\u011fu ve FibaCloud servislerinin genel durumunu g\u00f6stermedi\u011fi a\u00e7\u0131k\u00e7a yaz\u0131ld\u0131.<\/li>\n<li><strong>Add a monitor<\/strong> listesinden payla\u015faca\u011f\u0131n\u0131z monitoru se\u00e7in; ikinci monitor i\u00e7in ayn\u0131 i\u015flemi tekrarlay\u0131n. Testte <strong>Services<\/strong> grubu otomatik olu\u015ftu ve iki monitor buraya eklendi.<\/li>\n<li><strong>Save<\/strong> ile kaydedin. Sayfay\u0131 oturum a\u00e7\u0131lmam\u0131\u015f bir pencerede <code>https:\/\/uptime.example.com\/status\/docs-lab<\/code> adresinden kontrol edin; domain\u2019i kendi adresinizle de\u011fi\u015ftirin.<\/li>\n<\/ol>\n<p>Testte y\u00f6netim paneline giri\u015f gerekmeye devam ederken durum sayfas\u0131 ayr\u0131, oturumsuz taray\u0131c\u0131da a\u00e7\u0131ld\u0131. Ba\u015flang\u0131\u00e7ta iki monitor da sa\u011fl\u0131kl\u0131yd\u0131 ve sayfa <strong>All Systems Operational<\/strong> g\u00f6sterdi. Yeni olu\u015fan birka\u00e7 dakikal\u0131k ge\u00e7mi\u015fi uzun s\u00fcreli eri\u015filebilirlik sonucu gibi yorumlamay\u0131n.<\/p>\n<p>Planl\u0131 bak\u0131m veya ara\u015ft\u0131r\u0131lan bir kesinti i\u00e7in k\u0131sa bir olay duyurusu ekleyebilirsiniz. Etkilenen hizmeti, ba\u015flang\u0131\u00e7 zaman\u0131n\u0131 ve bilinen durumu yaz\u0131n; do\u011frulanmam\u0131\u015f bir k\u00f6k neden veya kesin \u00e7\u00f6z\u00fcm saati vermeyin. Sorun \u00e7\u00f6z\u00fcld\u00fc\u011f\u00fcnde ayn\u0131 duyuruyu g\u00fcncelleyin.<\/p>\n<p>Ger\u00e7ek denemede durum sayfas\u0131n\u0131n d\u00fczenleme ekran\u0131ndan <strong>Create Incident<\/strong> se\u00e7ildi. <strong>Title<\/strong> ve <strong>Content<\/strong> alanlar\u0131na bunun ayr\u0131 bir test hedefindeki kontroll\u00fc kesinti oldu\u011fu yaz\u0131l\u0131p <strong>Post<\/strong> ile yay\u0131nland\u0131. Hedef d\u00fczeldi\u011finde <strong>Edit<\/strong> \u00fczerinden metin g\u00fcncellendi, <strong>Post<\/strong> ile kaydedildi ve <strong>Resolve<\/strong> ile olay kapat\u0131ld\u0131.<\/p>\n<p>Oturum a\u00e7\u0131lmam\u0131\u015f taray\u0131c\u0131da son kontrol yap\u0131ld\u0131\u011f\u0131nda sayfa <strong>All Systems Operational<\/strong> g\u00f6sterdi; tamamlanan duyuru <strong>Past Incidents<\/strong> b\u00f6l\u00fcm\u00fcne ta\u015f\u0131nm\u0131\u015ft\u0131. Duyuruda hedefin 20:58:36 UTC\u2019de 200 verdi\u011fi, Kuma ve webhook geri d\u00f6n\u00fc\u015f\u00fcn\u00fcn 20:59:36 UTC\u2019de do\u011fruland\u0131\u011f\u0131 belirtildi.<\/p>\n<figure><img loading=\"lazy\" src=\"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-content\/uploads\/2026\/10\/fibacloud-uptime-kuma-20261031\/uptime-kuma-status-page.png\" alt=\"Herkese a\u00e7\u0131k durum sayfas\u0131nda sa\u011fl\u0131kl\u0131 iki kontrol, kesinti izleri ve Past Incidents b\u00f6l\u00fcm\u00fcndeki tamamlanm\u0131\u015f test duyurusu.\" width=\"1300\" height=\"770\"  decoding=\"async\"><figcaption>Anonim eri\u015fimle al\u0131nan ger\u00e7ek durum sayfas\u0131. Y\u00fczdeler yaln\u0131z yakla\u015f\u0131k 18 dakikal\u0131k bu test ge\u00e7mi\u015fine aittir; FibaCloud hizmet eri\u015filebilirli\u011fi \u00f6l\u00e7\u00fcm\u00fc de\u011fildir.<\/figcaption><\/figure>\n<p>Kuma ile durum sayfas\u0131 ayn\u0131 sunucuda bulundu\u011funda, o sunucunun kesintisi sayfay\u0131 da eri\u015filemez yapar. T\u00fcm altyap\u0131 ar\u0131zas\u0131nda ileti\u015fim kurman\u0131z gerekiyorsa ba\u011f\u0131ms\u0131z bir durum sayfas\u0131 veya ikinci bir ileti\u015fim kanal\u0131 planlay\u0131n.<\/p>\n<h2 id=\"yedek-geri-yukleme\">Kal\u0131c\u0131 veriyi yedekleyin ve geri y\u00fcklemeyi s\u0131nay\u0131n<\/h2>\n<p>Kal\u0131c\u0131 volume, konteyner de\u011fi\u015fiminde veriyi korur; sunucu diski kayboldu\u011funda kullanabilece\u011finiz ikinci bir kopya de\u011fildir. Uptime Kuma 2&#8217;de eski JSON d\u0131\u015fa\/i\u00e7e aktarma \u00f6zelli\u011fi kald\u0131r\u0131lm\u0131\u015ft\u0131r. Bu ak\u0131\u015fta t\u00fcm <code>\/app\/data<\/code> i\u00e7eri\u011fini tutarl\u0131 bi\u00e7imde yedekleriz.<\/p>\n<p>Yedek; y\u00f6netici hesab\u0131n\u0131, monitor ayarlar\u0131n\u0131, ge\u00e7mi\u015fi ve bildirim ba\u011flant\u0131 bilgilerini i\u00e7erebilir. Dosyay\u0131 \u00f6zel tutun, eri\u015fimini s\u0131n\u0131rlay\u0131n ve sunucu d\u0131\u015f\u0131nda korunan bir kopyas\u0131n\u0131 saklay\u0131n. Ekran g\u00f6r\u00fcnt\u00fclerini veya bir Compose dosyas\u0131n\u0131 tek ba\u015f\u0131na uygulama yede\u011fi olarak de\u011ferlendirmeyin.<\/p>\n<p>\u00d6nce Coolify\u2019deki kaynak ad\u0131n\u0131 \u00e7al\u0131\u015fan konteynerle e\u015fle\u015ftirin. Kuma VPS\u2019inde \u015fu listeyi a\u00e7\u0131n:<\/p>\n<div class=\"fc-code-example\">\n<pre><code>sudo docker ps --format &#x27;table {{.Names}}\\t{{.Image}}\\t{{.Status}}&#x27;\n<\/code><\/pre>\n<\/div>\n<p>A\u015fa\u011f\u0131daki <code>REPLACE_WITH_YOUR_RESOURCE_ID<\/code> k\u0131sm\u0131n\u0131 kendi ger\u00e7ek kaynak kimli\u011finizle de\u011fi\u015ftirin. Bu tarif, testte uygulanan durdurma, t\u00fcm volume\u2019u ar\u015fivleme ve ayn\u0131 konteyneri ba\u015flatma i\u015flemlerinin okuyucuya uyarlanm\u0131\u015f h\u00e2lidir. SQLite ve Docker\u2019\u0131n varsay\u0131lan yerel volume yolu i\u00e7in haz\u0131rlanm\u0131\u015ft\u0131r; farkl\u0131 veri konumu veya veritaban\u0131nda do\u011frudan kullanmay\u0131n. \u0130\u015flem boyunca Coolify\u2019den e\u015fzamanl\u0131 da\u011f\u0131t\u0131m ba\u015flatmay\u0131n.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>sudo bash &lt;&lt;&#x27;KUMA_BACKUP&#x27;\nset -euo pipefail\numask 077\nKUMA_CONTAINER=&#x27;uptime-kuma-REPLACE_WITH_YOUR_RESOURCE_ID&#x27;\n[[ &quot;$KUMA_CONTAINER&quot; != *REPLACE* ]]\nKUMA_ID=&quot;$(docker container inspect --format &#x27;{{.Id}}&#x27; &quot;$KUMA_CONTAINER&quot;)&quot;\nKUMA_VOLUME=&quot;$(docker container inspect --format &#x27;{{range .Mounts}}{{if and (eq .Destination &quot;\/app\/data&quot;) (eq .Type &quot;volume&quot;)}}{{println .Name}}{{end}}{{end}}&#x27; &quot;$KUMA_ID&quot;)&quot;\n[[ &quot;$KUMA_VOLUME&quot; =~ ^[a-zA-Z0-9][a-zA-Z0-9_.-]+$ ]]\nKUMA_DATA=&quot;$(docker volume inspect --format &#x27;{{.Mountpoint}}&#x27; &quot;$KUMA_VOLUME&quot;)&quot;\n[[ &quot;$KUMA_DATA&quot; == &quot;\/var\/lib\/docker\/volumes\/$KUMA_VOLUME\/_data&quot; ]]\n[[ &quot;$(realpath &quot;$KUMA_DATA&quot;)&quot; == &quot;$KUMA_DATA&quot; ]]\n[[ -f &quot;$KUMA_DATA\/kuma.db&quot; &amp;&amp; -f &quot;$KUMA_DATA\/db-config.json&quot; ]]\n[[ &quot;$(docker ps -aq --no-trunc --filter &quot;volume=$KUMA_VOLUME&quot;)&quot; == &quot;$KUMA_ID&quot; ]]\n[[ &quot;$(docker container inspect --format &#x27;{{.State.Running}}&#x27; &quot;$KUMA_ID&quot;)&quot; == true ]]\nKUMA_BACKUP_DIR=&quot;$(mktemp -d \/root\/kuma-backup-XXXXXXXX)&quot;\nprintf &#x27;%s\\n&#x27; &quot;$KUMA_CONTAINER&quot; &gt; &quot;$KUMA_BACKUP_DIR\/container-name.txt&quot;\nprintf &#x27;%s\\n&#x27; &quot;$KUMA_ID&quot; &gt; &quot;$KUMA_BACKUP_DIR\/container-id.txt&quot;\ndocker container inspect --format &#x27;{{.Image}}&#x27; &quot;$KUMA_ID&quot; &gt; &quot;$KUMA_BACKUP_DIR\/image-id.txt&quot;\nprintf &#x27;%s\\n&#x27; &quot;$KUMA_VOLUME&quot; &gt; &quot;$KUMA_BACKUP_DIR\/volume-name.txt&quot;\ndocker container inspect --format &#x27;{{.Config.Image}}&#x27; &quot;$KUMA_ID&quot; &gt; &quot;$KUMA_BACKUP_DIR\/image.txt&quot;\ntrap &#x27;if [[ &quot;$(docker container inspect --format &quot;{{.State.Running}}&quot; &quot;$KUMA_ID&quot;)&quot; == false ]]; then docker start &quot;$KUMA_ID&quot; &gt;\/dev\/null; fi&#x27; EXIT\ndocker stop --time 30 &quot;$KUMA_ID&quot;\n[[ &quot;$(docker container inspect --format &#x27;{{.State.Running}}&#x27; &quot;$KUMA_ID&quot;)&quot; == false ]]\n[[ -z &quot;$(docker ps -q --filter &quot;volume=$KUMA_VOLUME&quot;)&quot; ]]\ntar --numeric-owner --acls --xattrs --one-file-system \\\n  -czpf &quot;$KUMA_BACKUP_DIR\/data.tar.gz&quot; -C &quot;$KUMA_DATA&quot; .\nchmod 0600 &quot;$KUMA_BACKUP_DIR\/data.tar.gz&quot;\n(cd &quot;$KUMA_BACKUP_DIR&quot; &amp;&amp; sha256sum data.tar.gz &gt; data.sha256)\ntar -tzf &quot;$KUMA_BACKUP_DIR\/data.tar.gz&quot; &gt; &quot;$KUMA_BACKUP_DIR\/members.txt&quot;\ndocker start &quot;$KUMA_ID&quot;\ntrap - EXIT\nKUMA_HEALTHY=false\nfor attempt in {1..60}; do\n  if [[ &quot;$(docker container inspect --format &#x27;{{.State.Running}} {{.State.Health.Status}}&#x27; &quot;$KUMA_ID&quot;)&quot; == &quot;true healthy&quot; ]]; then\n    KUMA_HEALTHY=true\n    break\n  fi\n  sleep 2\ndone\nif [[ &quot;$KUMA_HEALTHY&quot; != true ]]; then\n  docker container inspect --format &#x27;{{json .State}}&#x27; &quot;$KUMA_ID&quot;\n  exit 1\nfi\nprintf &#x27;Backup directory: %s\\n&#x27; &quot;$KUMA_BACKUP_DIR&quot;\nKUMA_BACKUP\n<\/code><\/pre>\n<\/div>\n<p>Komut, volume ad\u0131n\u0131 tahmin etmek yerine konteynerin <code>\/app\/data<\/code> ba\u011flant\u0131s\u0131ndan \u00e7\u00f6zer. Ayn\u0131 volume ba\u015fka bir konteynere de ba\u011fl\u0131ysa durur. Yedek al\u0131n\u0131rken Kuma ve bu sunucudaki durum sayfas\u0131 k\u0131sa s\u00fcreli\u011fine hizmet veremez. Ar\u015fiv okumas\u0131 ba\u015far\u0131s\u0131z olursa \u00e7\u0131k\u0131\u015f i\u015flemi ayn\u0131 konteyneri yeniden ba\u015flatmay\u0131 dener; \u00e7\u0131kt\u0131y\u0131 ve son servis durumunu kontrol edin.<\/p>\n<p>Yazd\u0131r\u0131lan <code>\/root\/kuma-backup-\u2026<\/code> dizinini kaydedin. \u0130\u00e7indeki <code>data.tar.gz<\/code>, sa\u011flama toplam\u0131 ve kaynak kimli\u011fi dosyalar\u0131 geri y\u00fcklemede birlikte kullan\u0131l\u0131r. Konteynerin <strong>healthy<\/strong> durumuna d\u00f6nmesi i\u00e7in en fazla yakla\u015f\u0131k iki dakika beklenir; bekleme ba\u015far\u0131s\u0131z olursa komut hata ile \u00e7\u0131kar ve durum bilgisini g\u00f6sterir.<\/p>\n<p>Ger\u00e7ek testte yaln\u0131z <code>kuma.db<\/code> de\u011fil; <code>db-config.json<\/code>, <code>docker-tls<\/code>, <code>screenshots<\/code>, <code>upload<\/code> ve veri dizininin kendisi sahiplik ve izinleriyle ar\u015fivlendi. Yedek ayr\u0131ca \u015fifrelenerek ba\u015fka bir sunucuda \u00f6zel olarak sakland\u0131; \u015fifresi a\u00e7\u0131lan kopyan\u0131n dosya hash\u2019leri ve ar\u015fiv \u00fcyeleri do\u011fruland\u0131. Siz de kendi yedekleme sisteminizle sunucu d\u0131\u015f\u0131na \u015fifreli kopya al\u0131n ve geri okunabildi\u011fini s\u0131nay\u0131n; yukar\u0131daki komut yaln\u0131z yerel yede\u011fi olu\u015fturur.<\/p>\n<h3 id=\"geri-donus-denemesi\">Ayn\u0131 sunucuda geri d\u00f6n\u00fc\u015f denemesi<\/h3>\n<p>Geri y\u00fckleme, se\u00e7ti\u011finiz yedekteki duruma d\u00f6nd\u00fcr\u00fcr. Yedekten sonra olu\u015fan kay\u0131tlar korunmayabilir. \u0130\u015fleme ba\u015flamadan \u00f6nce mevcut verinin ayr\u0131ca kopyas\u0131n\u0131 al\u0131n ve ger\u00e7ekten do\u011fru volume&#8217;u se\u00e7ti\u011finizi kontrol edin.<\/p>\n<p>Bu testte, yedekten sonra <code>Restore canary - created after backup<\/code> adl\u0131 \u00fc\u00e7\u00fcnc\u00fc bir monitor olu\u015fturuldu; bildirimleri kapal\u0131 b\u0131rak\u0131ld\u0131 ve monitor duraklat\u0131ld\u0131. B\u00f6ylece yaln\u0131z konteyneri yeniden ba\u015flatmakla kar\u0131\u015ft\u0131r\u0131lmayacak bir geri d\u00f6n\u00fc\u015f i\u015fareti elde edildi: eski yedek ger\u00e7ekten y\u00fcklenirse bu yeni monitor bulunmamal\u0131d\u0131r.<\/p>\n<p>A\u015fa\u011f\u0131daki iki de\u011fi\u015fkeni kendi konteyneriniz ve yukar\u0131da olu\u015fturdu\u011funuz yedek diziniyle de\u011fi\u015ftirin. Bu tarif ayn\u0131 konteyner kimli\u011fini, ayn\u0131 imaj\u0131 ve ayn\u0131 volume\u2019u bekler; yeni bir sunucuya ta\u015f\u0131ma i\u015flemi de\u011fildir. Yaln\u0131z size ait, g\u00fcvenilir ve sa\u011flama toplam\u0131 do\u011frulanan ar\u015fivi kullan\u0131n.<\/p>\n<div class=\"fc-code-example\">\n<pre><code>sudo bash &lt;&lt;&#x27;KUMA_RESTORE&#x27;\nset -euo pipefail\numask 077\nKUMA_CONTAINER=&#x27;uptime-kuma-REPLACE_WITH_YOUR_RESOURCE_ID&#x27;\nKUMA_BACKUP_DIR=&#x27;\/root\/kuma-backup-REPLACE_WITH_YOUR_DIRECTORY&#x27;\n[[ &quot;$KUMA_CONTAINER$KUMA_BACKUP_DIR&quot; != *REPLACE* ]]\n[[ -d &quot;$KUMA_BACKUP_DIR&quot; &amp;&amp; ! -L &quot;$KUMA_BACKUP_DIR&quot; ]]\n[[ &quot;$(realpath &quot;$KUMA_BACKUP_DIR&quot;)&quot; == &quot;$KUMA_BACKUP_DIR&quot; ]]\n[[ &quot;$(cat &quot;$KUMA_BACKUP_DIR\/container-name.txt&quot;)&quot; == &quot;$KUMA_CONTAINER&quot; ]]\n(cd &quot;$KUMA_BACKUP_DIR&quot; &amp;&amp; sha256sum -c data.sha256)\nKUMA_ID=&quot;$(docker container inspect --format &#x27;{{.Id}}&#x27; &quot;$KUMA_CONTAINER&quot;)&quot;\n[[ &quot;$KUMA_ID&quot; == &quot;$(cat &quot;$KUMA_BACKUP_DIR\/container-id.txt&quot;)&quot; ]]\n[[ &quot;$(docker container inspect --format &#x27;{{.Image}}&#x27; &quot;$KUMA_ID&quot;)&quot; == &quot;$(cat &quot;$KUMA_BACKUP_DIR\/image-id.txt&quot;)&quot; ]]\n[[ &quot;$(docker container inspect --format &#x27;{{.Config.Image}}&#x27; &quot;$KUMA_ID&quot;)&quot; == &quot;$(cat &quot;$KUMA_BACKUP_DIR\/image.txt&quot;)&quot; ]]\nKUMA_VOLUME=&quot;$(docker container inspect --format &#x27;{{range .Mounts}}{{if and (eq .Destination &quot;\/app\/data&quot;) (eq .Type &quot;volume&quot;)}}{{println .Name}}{{end}}{{end}}&#x27; &quot;$KUMA_ID&quot;)&quot;\n[[ &quot;$KUMA_VOLUME&quot; =~ ^[a-zA-Z0-9][a-zA-Z0-9_.-]+$ ]]\n[[ &quot;$KUMA_VOLUME&quot; == &quot;$(cat &quot;$KUMA_BACKUP_DIR\/volume-name.txt&quot;)&quot; ]]\nKUMA_DATA=&quot;$(docker volume inspect --format &#x27;{{.Mountpoint}}&#x27; &quot;$KUMA_VOLUME&quot;)&quot;\n[[ &quot;$KUMA_DATA&quot; == &quot;\/var\/lib\/docker\/volumes\/$KUMA_VOLUME\/_data&quot; ]]\n[[ &quot;$(realpath &quot;$KUMA_DATA&quot;)&quot; == &quot;$KUMA_DATA&quot; ]]\n[[ &quot;$(docker ps -aq --no-trunc --filter &quot;volume=$KUMA_VOLUME&quot;)&quot; == &quot;$KUMA_ID&quot; ]]\npython3 - &quot;$KUMA_BACKUP_DIR\/data.tar.gz&quot; &lt;&lt;&#x27;ARCHIVE_CHECK&#x27;\nimport sys, tarfile\nfrom pathlib import PurePosixPath\nwith tarfile.open(sys.argv[1], &#x27;r:gz&#x27;) as archive:\n    seen = set()\n    for member in archive.getmembers():\n        path = PurePosixPath(member.name)\n        assert not path.is_absolute() and &#x27;..&#x27; not in path.parts\n        assert member.isfile() or member.isdir()\n        assert str(path) not in seen\n        seen.add(str(path))\n    assert &#x27;kuma.db&#x27; in seen and &#x27;db-config.json&#x27; in seen\nARCHIVE_CHECK\nKUMA_RESCUE_DIR=&quot;$(mktemp -d \/root\/kuma-before-restore-XXXXXXXX)&quot;\ndocker stop --time 30 &quot;$KUMA_ID&quot;\n[[ &quot;$(docker container inspect --format &#x27;{{.State.Running}}&#x27; &quot;$KUMA_ID&quot;)&quot; == false ]]\n[[ -z &quot;$(docker ps -q --filter &quot;volume=$KUMA_VOLUME&quot;)&quot; ]]\ntar --numeric-owner --acls --xattrs --one-file-system \\\n  -czpf &quot;$KUMA_RESCUE_DIR\/newer-data.tar.gz&quot; -C &quot;$KUMA_DATA&quot; .\n(cd &quot;$KUMA_RESCUE_DIR&quot; &amp;&amp; sha256sum newer-data.tar.gz &gt; newer-data.sha256)\ntar -tzf &quot;$KUMA_RESCUE_DIR\/newer-data.tar.gz&quot; &gt; &quot;$KUMA_RESCUE_DIR\/members.txt&quot;\nmkdir -m 0700 &quot;$KUMA_RESCUE_DIR\/quarantine&quot;\nfind &quot;$KUMA_DATA&quot; -mindepth 1 -maxdepth 1 \\\n  -exec mv -t &quot;$KUMA_RESCUE_DIR\/quarantine&quot; -- {} +\ntar --same-owner --acls --xattrs \\\n  -xzpf &quot;$KUMA_BACKUP_DIR\/data.tar.gz&quot; -C &quot;$KUMA_DATA&quot;\ntar --compare --gzip --file &quot;$KUMA_BACKUP_DIR\/data.tar.gz&quot; --directory &quot;$KUMA_DATA&quot;\ndocker start &quot;$KUMA_ID&quot;\nKUMA_HEALTHY=false\nfor attempt in {1..60}; do\n  if [[ &quot;$(docker container inspect --format &#x27;{{.State.Running}} {{.State.Health.Status}}&#x27; &quot;$KUMA_ID&quot;)&quot; == &quot;true healthy&quot; ]]; then\n    KUMA_HEALTHY=true\n    break\n  fi\n  sleep 2\ndone\nif [[ &quot;$KUMA_HEALTHY&quot; != true ]]; then\n  docker container inspect --format &#x27;{{json .State}}&#x27; &quot;$KUMA_ID&quot;\n  exit 1\nfi\nprintf &#x27;Newer state preserved in: %s\\n&#x27; &quot;$KUMA_RESCUE_DIR&quot;\nKUMA_RESTORE\n<\/code><\/pre>\n<\/div>\n<p>\u0130\u015flem \u00f6nce daha yeni durumun ayr\u0131 yede\u011fini al\u0131r ve mevcut dosyalar\u0131 <code>quarantine<\/code> klas\u00f6r\u00fcne ta\u015f\u0131r. Ard\u0131ndan eski ar\u015fivi ayn\u0131 volume\u2019a a\u00e7ar; <code>tar --compare<\/code> kontrol\u00fc ge\u00e7meden Kuma\u2019y\u0131 ba\u015flatmaz. Durdurma sonras\u0131nda hata olu\u015fursa otomatik silme veya zorla devam etme yoktur: Kuma\u2019n\u0131n durumunu kontrol edin ve korunan g\u00fcncel kopyayla hatay\u0131 \u00e7\u00f6z\u00fcn.<\/p>\n<p>Ger\u00e7ek geri y\u00fckleme, di\u011fer sunucudaki \u015fifreli yede\u011fin do\u011frulanm\u0131\u015f \u00e7\u00f6z\u00fclm\u00fc\u015f kopyas\u0131yla tamamland\u0131. Servis ba\u015flat\u0131lmadan \u00f6nce dosya i\u00e7erikleri, UID\/GID de\u011ferleri ve izinler eski yedekle e\u015fle\u015fti; yedekten sonra olu\u015fturulan duraklat\u0131lm\u0131\u015f monitor bulunmad\u0131. Ayn\u0131 Kuma konteyneri yeniden sa\u011fl\u0131kl\u0131 \u00e7al\u0131\u015ft\u0131 ve mevcut Coolify uygulamas\u0131 korunarak i\u015flem tamamland\u0131.<\/p>\n<table>\n<thead>\n<tr>\n<th>Geri d\u00f6n\u00fc\u015f sonras\u0131 kontrol<\/th>\n<th>Ger\u00e7ek sonu\u00e7<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Yeni taray\u0131c\u0131 oturumunda giri\u015f<\/td>\n<td>Parola ve TOTP koduyla Dashboard a\u00e7\u0131ld\u0131.<\/td>\n<\/tr>\n<tr>\n<td>Monitorlar<\/td>\n<td>\u0130ki orijinal monitor Up; yedekten sonra olu\u015fturulan duraklat\u0131lm\u0131\u015f test monitoru yok.<\/td>\n<\/tr>\n<tr>\n<td>\u00d6nceki kesinti ge\u00e7mi\u015fi<\/td>\n<td>20:57:36 UTC Down ve 20:59:36 UTC Up kay\u0131tlar\u0131 korundu.<\/td>\n<\/tr>\n<tr>\n<td>Bildirim<\/td>\n<td>Geri y\u00fcklenen webhook ayar\u0131nda Test ba\u015far\u0131l\u0131 oldu; al\u0131c\u0131 21:05:32 UTC\u2019de yeni test olay\u0131n\u0131 kaydetti.<\/td>\n<\/tr>\n<tr>\n<td>Herkese a\u00e7\u0131k durum sayfas\u0131<\/td>\n<td>Oturumsuz taray\u0131c\u0131da iki monitor ve Past Incidents i\u00e7indeki tamamlanm\u0131\u015f duyuru a\u00e7\u0131ld\u0131.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Bu sonu\u00e7, yaln\u0131z servisin yeniden ba\u015flamas\u0131n\u0131 de\u011fil, \u00f6nceki uygulama durumunun geri geldi\u011fini g\u00f6sterir. Sunucu kayb\u0131, farkl\u0131 bir VPS\u2019e ta\u015f\u0131ma ve s\u00fcr\u00fcm y\u00fckseltmesinden geri d\u00f6nme bu deneyin kapsam\u0131 d\u0131\u015f\u0131ndad\u0131r.<\/p>\n<p>Ger\u00e7ek bir felaket plan\u0131nda yaln\u0131z Kuma verisini de\u011fil, alan ad\u0131 y\u00f6nlendirmesini, Coolify eri\u015fimini ve proxy yap\u0131land\u0131rmas\u0131n\u0131 da yeniden kurabilmelisiniz. Bu rehberde g\u00f6sterilen geri d\u00f6n\u00fc\u015f\u00fcn kapsam\u0131n\u0131 a\u015fan yeni sunucuya ge\u00e7i\u015fi ayr\u0131ca prova edin.<\/p>\n<h2 id=\"bakim-sorun-giderme\">Bak\u0131m ve s\u0131k kar\u015f\u0131la\u015f\u0131lan sorunlar<\/h2>\n<table>\n<thead>\n<tr>\n<th>Belirti<\/th>\n<th>Kontrol edilecek nokta<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Alan ad\u0131 a\u00e7\u0131lm\u0131yor veya proxy hata veriyor.<\/td>\n<td>A\/AAAA kay\u0131tlar\u0131n\u0131, \u00e7al\u0131\u015fan Kuma servisini ve domain&#8217;in y\u00f6nlendi\u011fi i\u00e7 portu kontrol edin. Ayn\u0131 host portuna ikinci servis ba\u011flamay\u0131n.<\/td>\n<\/tr>\n<tr>\n<td>Panel a\u00e7\u0131l\u0131yor fakat canl\u0131 ba\u011flant\u0131 kurulam\u0131yor.<\/td>\n<td>WebSocket aktar\u0131m\u0131n\u0131 ve taray\u0131c\u0131 a\u011f kay\u0131tlar\u0131n\u0131 kontrol edin. Uygulamay\u0131 alt dizin yerine alt alan ad\u0131nda yay\u0131nlay\u0131n.<\/td>\n<\/tr>\n<tr>\n<td>Taray\u0131c\u0131da site a\u00e7\u0131l\u0131yor, monitor ba\u015far\u0131s\u0131z oluyor.<\/td>\n<td>\u0130ste\u011fin Kuma sunucusundan \u00e7\u0131kt\u0131\u011f\u0131n\u0131 hat\u0131rlay\u0131n. O sunucunun DNS, IPv4\/IPv6, TLS ve hedef g\u00fcvenlik duvar\u0131 davran\u0131\u015f\u0131n\u0131 inceleyin.<\/td>\n<\/tr>\n<tr>\n<td>Monitor hata sayfas\u0131nda bile Up g\u00f6r\u00fcn\u00fcyor.<\/td>\n<td>Yan\u0131t durum kodunu kontrol edin. Uygulama hatay\u0131 200 ile d\u00f6n\u00fcyorsa daha anlaml\u0131 bir sa\u011fl\u0131k adresi veya i\u00e7erik kontrol\u00fc gerekir.<\/td>\n<\/tr>\n<tr>\n<td>Durum de\u011fi\u015fiyor ancak bildirim yok.<\/td>\n<td>Bildirim ba\u011flant\u0131s\u0131n\u0131n o monitora atand\u0131\u011f\u0131n\u0131, testin ba\u015far\u0131l\u0131 oldu\u011funu ve al\u0131c\u0131n\u0131n ger\u00e7ek olay\u0131 kaydetti\u011fini do\u011frulay\u0131n.<\/td>\n<\/tr>\n<tr>\n<td>Yeniden da\u011f\u0131t\u0131m sonras\u0131 ilk kurulum ekran\u0131 geldi.<\/td>\n<td>Yeni hesap olu\u015fturmadan \u00f6nce <code>\/app\/data<\/code> ba\u011flant\u0131s\u0131n\u0131 ve ger\u00e7ek volume ad\u0131n\u0131 kontrol edin. Yanl\u0131\u015f veya bo\u015f volume ba\u011flanm\u0131\u015f olabilir.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>\u0130maj etiketini de\u011fi\u015ftirmeden \u00f6nce s\u00fcr\u00fcm notlar\u0131n\u0131 okuyun, tutarl\u0131 yedek al\u0131n ve bak\u0131m s\u0131ras\u0131nda izlemenin durabilece\u011fini hesaba kat\u0131n. G\u00fcncellemeden sonra giri\u015f, monitor, bildirim ve durum sayfas\u0131n\u0131 yeniden kontrol edin. \u00d6nceki imaja d\u00f6nmek, veritaban\u0131 \u015femas\u0131 de\u011fi\u015fmi\u015fse tek ba\u015f\u0131na geri d\u00f6n\u00fc\u015f plan\u0131 de\u011fildir.<\/p>\n<p>Uzun s\u00fcre veri tutuyorsan\u0131z disk kullan\u0131m\u0131n\u0131 ve kendi ihtiyac\u0131n\u0131za g\u00f6re ge\u00e7mi\u015f saklama s\u00fcresini takip edin. Uptime Kuma web eri\u015filebilirli\u011fi i\u00e7in uygundur; ayr\u0131nt\u0131l\u0131 CPU, bellek ve uygulama metrikleri i\u00e7in <a href=\"https:\/\/www.fibacloud.com\/community\/tutorials\/ubuntu-ustunde-grafana-kurulumu\/\">Grafana rehberi<\/a> farkl\u0131 bir g\u00f6zlem katman\u0131 sunar.<\/p>\n<h2 id=\"sik-sorulan-sorular\">S\u0131k sorulan sorular<\/h2>\n<h3 id=\"uptime-kuma-ucretsiz-mi\">Uptime Kuma \u00fccretsiz mi?<\/h3>\n<p>Uptime Kuma a\u00e7\u0131k kaynakl\u0131d\u0131r. Kendi sunucunuzda \u00e7al\u0131\u015ft\u0131rd\u0131\u011f\u0131n\u0131zda sunucu, depolama ve se\u00e7ti\u011finiz bildirim sa\u011flay\u0131c\u0131s\u0131n\u0131n maliyetleri size aittir.<\/p>\n<h3 id=\"coolify-olmadan-kurulum\">Coolify olmadan kurulabilir mi?<\/h3>\n<p>Evet. Proje do\u011frudan Docker kurulumunu da destekler. Bu makale, mevcut Coolify proxy&#8217;sini ve servis y\u00f6netimini kullanan yolu g\u00f6sterir; bare-metal veya ayr\u0131 Nginx kurulumu bu ad\u0131mlar\u0131n par\u00e7as\u0131 de\u011fildir.<\/p>\n<h3 id=\"ayni-vps-uzerinde-izleme\">Uygulamamla ayn\u0131 VPS&#8217;e kurmam yeterli mi?<\/h3>\n<p>Uygulama yan\u0131t\u0131n\u0131n bozulmas\u0131n\u0131 izlemek i\u00e7in yararl\u0131 olabilir. VPS&#8217;in veya bulundu\u011fu a\u011f\u0131n tamamen eri\u015filemez olmas\u0131n\u0131 ba\u011f\u0131ms\u0131z olarak izlemek i\u00e7in ba\u015fka bir sunucu gerekir.<\/p>\n<h3 id=\"tek-monitor-kapsami\">Bir monitor ile her \u015feyi izleyebilir miyim?<\/h3>\n<p>Her kontrol yaln\u0131z yap\u0131land\u0131rd\u0131\u011f\u0131n\u0131z hedefi ve ko\u015fulu s\u0131nar. Web aray\u00fcz\u00fc, API ve farkl\u0131 ba\u011f\u0131ml\u0131l\u0131klar i\u00e7in ihtiyaca g\u00f6re ayr\u0131 kontroller olu\u015fturun; gereksiz ve birbirini tekrar eden alarmlardan ka\u00e7\u0131n\u0131n.<\/p>\n<h2 id=\"kaynaklar\">Kaynaklar<\/h2>\n<ul>\n<li><a href=\"https:\/\/github.com\/louislam\/uptime-kuma\/releases\/tag\/2.5.9\" rel=\"nofollow noopener\" target=\"_blank\">Uptime Kuma 2.5.9 s\u00fcr\u00fcm\u00fc<\/a><\/li>\n<li><a href=\"https:\/\/github.com\/louislam\/uptime-kuma\/blob\/2.5.9\/README.md\" rel=\"nofollow noopener\" target=\"_blank\">Uptime Kuma kurulumu ve \u00f6zellikleri<\/a><\/li>\n<li><a href=\"https:\/\/github.com\/louislam\/uptime-kuma\/wiki\/Reverse-Proxy\" rel=\"nofollow noopener\" target=\"_blank\">Uptime Kuma reverse proxy belgesi<\/a><\/li>\n<li><a href=\"https:\/\/github.com\/louislam\/uptime-kuma\/wiki\/Migration-From-v1-To-v2\" rel=\"nofollow noopener\" target=\"_blank\">Uptime Kuma v2 de\u011fi\u015fiklikleri ve veri yede\u011fi<\/a><\/li>\n<li><a href=\"https:\/\/coolify.io\/docs\/applications\/builds\/docker-compose\" rel=\"nofollow noopener\" target=\"_blank\">Coolify Docker Compose belgesi<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Coolify \u00fczerinde Uptime Kuma kurun; HTTPS, site izleme, webhook bildirimi ve durum sayfas\u0131n\u0131 yap\u0131land\u0131r\u0131n. Ger\u00e7ek kesinti ve veri geri y\u00fckleme ad\u0131mlar\u0131n\u0131 izleyin.<\/p>\n","protected":false},"author":1,"featured_media":2624,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[54,72,294],"class_list":["post-2622","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","tag-docker","tag-ubuntu","tag-uptime-kuma"],"lang":"tr","translations":{"tr":2622,"en":2623},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts\/2622","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=2622"}],"version-history":[{"count":1,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts\/2622\/revisions"}],"predecessor-version":[{"id":2626,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/posts\/2622\/revisions\/2626"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/media\/2624"}],"wp:attachment":[{"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/media?parent=2622"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/categories?post=2622"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fibacloud.com\/community\/tutorials\/wp-json\/wp\/v2\/tags?post=2622"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}