Cloudflare Tunnel (cydu.net)

Notes for the Cloudflare Tunnel running on this host: config location, safe edits, and service control.

Layout

• Config: /etc/cloudflared/config.yml
• Credentials: /usr/local/etc/cloudflared/<tunnel-id>.json
• Service unit: /etc/systemd/system/cloudflared.service
• Exec: /usr/bin/cloudflared --config /etc/cloudflared/config.yml --no-autoupdate tunnel run

Config rules

• The last ingress rule must be a catch-all with no hostname/path.
• Minimal example: ```yaml tunnel: credentials-file: /usr/local/etc/cloudflared/.json

ingress: - hostname: demo.cydu.net service: http:// # catch-all, MUST be last and have no hostname/path - service: http_status:404 `` - After edits:sudo cloudflared tunnel validate --config /etc/cloudflared/config.yml- To test interactively:sudo cloudflared --config /etc/cloudflared/config.yml tunnel run` (Ctrl+C to exit).

Service control

• Restart: sudo systemctl restart cloudflared
• Status: sudo systemctl status cloudflared
• Stop/Start: sudo systemctl stop cloudflared / sudo systemctl start cloudflared
• If you change the unit file itself: sudo systemctl daemon-reload then restart.

Debugging

• Tail logs: sudo journalctl -u cloudflared -f (or -n 200 --no-pager for recent entries)
• Foreground run (bypasses systemd): sudo cloudflared --config /etc/cloudflared/config.yml tunnel run
• Check version: cloudflared --version
• Common issues:
• Catch-all rule not last: fix ingress order.
• Bad credentials: re-run sudo cloudflared login and refresh the JSON cred file path.
• Port target down: ensure the local service (e.g., Minikube Ingress) is reachable.