ligbox/obsidian-vault
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
obsidian-vault/Infra-Network/RENTCHARGE_CLOUDFLARE_TUNNEL.md

1.6 KiB
Raw Permalink History

Rentcharge Cloudflare Tunnel (BIG)

Atualizado: 2026-09-08 Host: BIG (wardrobe) ig-proxmox URL: https://rentcharge.itecnologys.com/

Causa do Error 1033 (recorrente)

O DNS publico esta certo (Cloudflare). O 1033 aparece quando o connector do tunel itecnologys nao esta ligado.

Dois tuneis no mesmo host:

Servico Config Metricas (unico) Zona
cloudflared.service config-mycloud.yml 127.0.0.1:20241 myvexx.com
cloudflared-itecnologys.service config-itecnologys.yml 127.0.0.1:20243 rentcharge.itecnologys.com

Em 2026-09-08 o tunel itecnologys crash-loopava porque:

  1. Porta de metricas 20242 ja estava ocupada (conflito com o tunel mycloud).
  2. DNS Tailscale 100.100.100.100 nao resolve cfd-features.argotunnel.com.

A app no Traefik CT120 (10.10.10.120:80) estava OK o tempo todo.

Blindagem aplicada

  • Metricas fixas e distintas (20241 / 20243).
  • Drop-in DNS BindReadOnlyPaths /etc/cloudflared/resolv.conf (1.1.1.1 + 8.8.8.8) nos dois units.
  • StartLimitIntervalSec=0 no tunel itecnologys.
  • Watchdog a cada 2 min: cloudflared-itecnologys-watchdog.timer Reinicia o tunel so se o origin estiver 200 e o /ready local (127.0.0.1:20243/ready) falhar. Nao reinicia o cloudflared mycloud (R630/boiler).
  • Log: /var/log/rentcharge-watchdog.log
  • README no host: /etc/cloudflared/README-TUNNELS.txt

Comandos

systemctl is-active cloudflared cloudflared-itecnologys
tail -20 /var/log/rentcharge-watchdog.log
curl -sI -H Host: rentcharge.itecnologys.com http://10.10.10.120:80/
curl -s http://127.0.0.1:20243/ready

Nao alterar /etc/network/interfaces para este problema.