gem-llm-cloudflare-tunnel

Restore external GEM-LLM access via Cloudflare Tunnel with llm.pamout.com routing.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/saintgo7/claude-skills --skill gem-llm-cloudflare-tunnel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gem-llm-cloudflare-tunnel
Source: https://github.com/saintgo7/claude-skills/tree/main/gem-llm-cloudflare-tunnel
Command: npx skills add https://github.com/saintgo7/claude-skills --skill gem-llm-cloudflare-tunnel

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about gem-llm-cloudflare-tunnel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a 502 error on my Cloudflare Tunnel endpoint?

To fix a 502 error on a Cloudflare Tunnel, you must validate HTTP and DNS outcomes to pinpoint whether the failure originates from the gateway, origin service, tunnel downtime, or TLS issues. A controlled cloudflared restart resolves tunnel liveness problems.

How do I add a new subdomain DNS route to an existing Cloudflare Tunnel?

Adding a new subdomain DNS route requires registering the DNS route on the master node, then updating the ingress configuration on the n1 node to match the new hostname before validating the HTTP routing path.

Why does my Cloudflare Tunnel return a 521 or 525 HTTP error?

Cloudflare Tunnel 521 and 525 HTTP errors typically indicate origin bind issues or TLS handshake failures between the tunnel and the backend service, requiring ingress configuration validation to ensure hostname and certificate alignment.

Do I need separate configurations for n1 and master nodes when managing Cloudflare Tunnel?

Managing Cloudflare Tunnel requires role separation where the master node handles DNS route registration for new subdomains, while the n1 node manages the cloudflared ingress configuration and executes controlled service restarts.

What is the best way to restart cloudflared without dropping active connections?

The best way to safely restart cloudflared involves following a topology-aware operational runbook that executes controlled restart steps on the n1 node, followed by HTTP and DNS validation to verify external access is successfully restored.

Can I use Cloudflare Tunnel for SSH access between n1 and master nodes?

Yes, you can establish n1 to master SSH access using cloudflared access, which provides a secure tunnel pattern, though you may need specific troubleshooting steps to resolve potential connection reset issues.