Uptime Kuma Free Website Status Cras Linux Servo Cras Software

Solent externam catenam promotionis et amicitiae nexum ipsum viverra opus facere.

Si externae nexus et amicitiae nexus pereunt;SEOOrdo etiam declinabit, ideo magni momenti est ut statum paginae paginae paginae paginae externae monitorem praebeat.

Cur Uptime Kuma utere ad Monitor Websites?

Quomodo SEO monitor amicitiae nexus?

His additis nexus externos et nexus amicitiae permutantes, solemus nosuptime robot AddingConfigurare website magna vigilantia in suggestu nubem vigilantia ad detectionem paginae nexus externae cuiusque website.

Nihilominus, crescente numero externorum vinculorum et amici vinculis, suggestum nubis Uptime roboti limitem in numero vigilantia habet, et upgrade ac reddere debetis ut plura nubes vigilantia items additis.

Unde aperto fonte uti possumusLinuxCloud servo magna软件Instrumenta - Uptime Kuma.

Quid est Uptime Kuma software?

Uptime Kuma fons apertus est instrumentum monitoris Linux cum similibus muneribus ad Robot Uptime.

Cum aliis instrumentis magnae website similes comparatis, Uptime Kuma adiuvat officia auto-remediata cum paucioribus restrictionibus.

Hic articulus institutionem et usum Uptime Kuma introducet.

Quomodo installare Uptime Kuma vigilantia instrumentum?

Uptime Kuma sustinet Docker institutionem.

Sequens est tutorialis in gradibus institutionis Uptime Kuma.

Hoc mandatum estInstaller via CLI [Ubuntu/CentOS] Interactive CLI installer, cum aut sine auxilio Docker ▼

curl -o kuma_install.sh http://git.kuma.pet/install.sh && sudo bash kuma_install.sh

• Non commendatur uti praecepto institutionis praedictae: quia Uptime Kuma in non-Docker modo installatur, institutionem facile deficiet.
• (Monemus institutionem imperii infra)

Cum opus est ut Docker installare priusquam Uptime Kuma utens Docker inaugurare, Docker primum inaugurare.

Install Docker et Docker-componere

Update et install necesse software ▼

apt-get update && apt-get install -y wget vim

Si 404 error in renovatione incidit, solutionem infra ▼* obsecro reprehendo

Solve yum update Repodata repomd xml Errno XIV HTTPS Error CDIV - Not Found

Cum CWP tabulam inclusam inaugurari, quaestio "yum renovationis Repodata repomd xml Errno 14 HTTPS Error 404 - Not Found" videtur.Item, cum Uptime KumaLinux inaugurat vigilantia programmata servo vel MariaDB 10.3 utendo vel ...

install Docker

Si minister externus est, quaeso utere sequenti mandato

 curl -sSL https://get.docker.com/ | sh 

Si minister domesticus in Sinis est, hoc mandatum utere quaeso

 curl -sSL https://get.daocloud.io/docker | sh 

Set Docker incipere automatice in tabernus ▼

systemctl start docker 

systemctl enable docker

Install Docker-componere 

Si minister externus est, quaeso utere sequenti mandato

sudo curl -L "https://github.com/docker/compose/releases/download/1.24.1/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose

Si domesticus in Sinis est ministrans, sequenti praecepto utere quaeso

curl -L https://get.daocloud.io/docker/compose/releases/download/v2.1.1/docker-compose-`uname -s`-`uname -m` > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose

Sileo docker ministerium mandatum ▼

service docker restart

Quomodo installare Uptime Kuma liberum website status adipiscing instrumentum?

🐳 Instrue in Docker modum, vas creare nomine uptime-kuma ▼

docker volume create uptime-kuma

docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1

• Deinde transire potesIP:3001Visita Uptime-Kuma.

Si firewall CSF vales facere, debes portum aperire 3001 in CSF firewall ▼

vi /etc/csf/csf.conf
# Allow incoming TCP ports
 TCP_IN = "20,21,22,2812,25,53,80,110,143,443,465,587,993,995,2030,2031,2082,2083,2086,2087,2095,2096,3001" 

Sileo CSF ​​firewall ▼

csf -r

Install Nginx Proxy Manager

Nginx Proxy Procurator est Docker-substructio e contrario proxy.

Cum Nginx Proxy Procurator non est necessarius, si tempus terere non vis, non potes procuratorem Nginx proxy inaugurari.

Create Directory ▼

mkdir -p data/docker_data/npm
cd data/docker_data/npm

Create docker-compose.yml file ▼

nano docker-compose.yml

Imple sequenti tabella contentum, deinde CtrlTab + X servare, torcular Y exire ▼

version: "3"
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      # These ports are in format :
      - '80:80' # Public HTTP Port
      - '443:443' # Public HTTPS Port
      - '81:81' # Admin Web Port
      # Add any other Stream port you want to expose
      # - '21:21' # FTP
    environment:
      DB_MYSQL_HOST: "db"
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: "npm"
      DB_MYSQL_PASSWORD: "npm"
      DB_MYSQL_NAME: "npm"
      # Uncomment this if IPv6 is not enabled on your host
      # DISABLE_IPV6: 'true'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
    depends_on:
      - db

  db:
    image: 'jc21/mariadb-aria:latest'
    restart: unless-stopped
    environment:
      MYSQL_ROOT_PASSWORD: 'npm'
      MYSQL_DATABASE: 'npm'
      MYSQL_USER: 'npm'
      MYSQL_PASSWORD: 'npm'
    volumes:
      - ./data/mysql:/var/lib/mysql

currere ▼ *

docker-compose up -d

Si nuntius erroris sequentis similis apparet: "Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use"▼

[root@ten npm]# docker-compose up -d
npm_db_1 is up-to-date
Starting npm_app_1 ... error

ERROR: for npm_app_1 Cannot start service app: driver failed programming external connectivity on endpoint npm_app_1 (bd3512d79a2184dbd03b2a715fab3990d503c17e85c35b1b4324f79068a29969): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use

ERROR: for app Cannot start service app: driver failed programming external connectivity on endpoint npm_app_1 (bd3512d79a2184dbd03b2a715fab3990d503c17e85c35b1b4324f79068a29969): Error starting userland proxy: listen tcp4 0.0.0.0:443: bind: address already in use
ERROR: Encountered errors while bringing up the project.

• Significat portum illum 443 iam occupatum et docker-compose.yml fasciculus mox creatus emendandum est.

Port 443 mutari debet ad 442 ▼ .

      - '442:442' # Public HTTPS Port

Deinde iterum currunt imperium docker-compose up -d

Error nuntius apparebit:“Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use"

Etiam opus est portum mutare 80 usque ad 882 ▼

      - '882:882' # Public HTTP Port

per foramen http:// IP:81 Visita Nginx Proxy Procurator.

Ad primum login utere defaltam rationem initialem et tesseram ▼

Email: [email protected]
Password: changeme

• Post colligationem in, cave, quaeso, tuam electronicam et tesseram statim mutare.

Reverse procuratorem Uptime Kuma

Post Uptime Kuma insertis, default utendum estIP:3001Visita Uptime Kuma.

Nomen dominii accedere possumus et testimonium SSL configurare per procuratorem contrarium, sicut domicilium superius demonstratum est.

Deinde operationes generationis adversas praestabimus, utentes Proxy Procurator Nginx antea aedificavit.

a http:// IP:81 Open Nginx Proxy Manager.

Post primum colligationem, debes mutare nomen et tesseram usoris, te ipsum configurare placet.

Deinceps gradus operationis Nginx Proxy Procurator haec sunt:

1conversus Proxy Hosts ▼

2Click in vertice anguli recti Add Proxy Hosts▼

Gradus III: Configurare secundum figuram;click Save salvare ▼ 

4ClickEidtAperire configurationem paginam ▼

Step V: Ede SSL certificatorium et enable amet Https accessum ▼

• Hic, generatio inversa perficitur, et tunc uti potes nomine regio cui modo placuit Uptime Kuma accedere.
• Uptime Kuma configuration est valde simplex.
• Interface Sinenses habet, credo mox uti poteris.

Uptime Kuma utile PM2 mandata

Initium, desine, ac sileo mandata Uptime Kuma (hoc mandatum ad institutionem non Docker non-dedicatum) ▼

pm2 start uptime-kuma
pm2 stop uptime-kuma
pm2 restart uptime-kuma

Videre hodiernam consolatorium de Uptime Kuma (hoc mandatum est institutioni non-Docker dedicatum) ▼

pm2 monit

Run Uptime Kuma at startup (hoc mandatum est dedicatum non-Docker officinae) ▼

pm2 save && pm2 startup

Quomodo amoveas Uptime Kuma vigilantia software?

Si non installed a DockerUptime Kuma,Quomodo amoveas?

Exempli gratia, si hoc mandatum uteris, ut instituas in via non Docker ▼

curl -o kuma_install.sh http://git.kuma.pet/install.sh && sudo bash kuma_install.sh

Ut amoveas Uptime Kuma utere hoc mandatum ▼

1. ex servitio  pm2 stop uptime-kuma
2. delete Directory rm -rf /opt/uptime-kuma

Quomodo ut Uptime Kuma amoveas, si Docker utens instituas?

Sequens run query imperium ▼

docker ps -a

• scribentes injustitiam tuam kuma Nomen continentis, quod potest esse uptime-kuma

nolite mandatum ▼ *

• 请将container_nameMutare ad superius querykuma Nomen continens.

docker stop container_name
docker rm container_name

Uninstall Uptime Kuma ▼

docker volume rm uptime-kuma
docker rmi uptime-kuma

conclusioni

Interface Uptime Kuma purum et simplex est, et ad explicandum usumque facillime est.

Uptime Kuma valde bona est electio si non habes magna requisita pro magna website.