gem-llm-cloudflare-tunnel

What problem does it solve?

This Skill helps you restore and maintain external access to GEM-LLM through Cloudflare Tunnel when the public endpoint returns 502, the tunnel is down, DNS/subdomains need to be added, or cloudflared must be restarted.

Core Features & Use Cases

• Operational runbook for Cloudflare Tunnel: Provides a topology-aware procedure for managing the n1-side tunnel (including restart steps and health verification).
• Role separation (n1 vs master): Documents which node performs DNS routing registration for new subdomains and how that flows back into n1 ingress configuration.
• Validation and troubleshooting: Maps common HTTP outcomes (502/503/404/521/525) to likely causes such as gateway status, cloudflared liveness, ingress hostname mismatches, TLS problems, or origin bind issues.
• Optional SSH access pattern: Includes a bonus approach for n1→master SSH using cloudflared access, plus troubleshooting for connection resets.

Quick Start

Ask to generate a step-by-step restart and diagnosis plan for the llm.pamout.com Cloudflare Tunnel using the n1 cloudflared runbook when you see the public endpoint not responding.