Cloudflare Tunnel

Observed on relik-vps:

• Tunnel name in process: relik
• Tunnel ID / target: db4955bd-64e8-40bc-89d4-90cd39c0c8a9
• Config path: /root/.cloudflared/config.yml
• Credential file path exists under /root/.cloudflared/; do not copy it into git.
• systemctl is-active cloudflared returned inactive and systemctl is-enabled returned not-found, but a live process was running:

/usr/bin/cloudflared tunnel run relik

Current ingress observed from the sanitized config:

ingress:
  - hostname: relik.africa
    service: http://localhost:80
  - hostname: www.relik.africa
    service: http://localhost:80
  - hostname: slates.relik.africa
    service: http://localhost:80
  - hostname: slates-sandbox.relik.africa
    service: http://localhost:80
  - hostname: jellyfin.relik.africa
    service: http://100.120.38.37:8096
  - hostname: ersatztv.relik.africa
    service: http://100.120.38.37:8409
  - hostname: xn--4lja6dtb1de.relik.africa
    service: http://localhost:8000
  - service: http_status:404

Relevant DNS records from the FROM House feed:

• relik.africa CNAME -> db4955bd-64e8-40bc-89d4-90cd39c0c8a9.cfargotunnel.com
• www.relik.africa CNAME -> same tunnel target
• docs.relik.africa CNAME -> same tunnel target
• docs-sandbox.relik.africa CNAME -> same tunnel target
• slates.relik.africa CNAME -> same tunnel target
• slates-sandbox.relik.africa CNAME -> same tunnel target
• jellyfin.relik.africa CNAME -> same tunnel target
• ersatztv.relik.africa CNAME -> same tunnel target
• xn--4lja6dtb1de.relik.africa CNAME -> same tunnel target

Token handling:

• Cloudflare token references exist in the FROM House feed / runtime secrets.
• Do not paste token values into this repo.
• For deployment automation, use external secret injection or a locked local environment file ignored by git.