node-static-proxy-cloudflare

Start a Node.js static server and Cloudflare tunnel in correct sequence.

2|Updated May 10, 2026
One-click install
npx skills add https://github.com/freedomw1987/tree_monstor --skill node-static-proxy-cloudflare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: node-static-proxy-cloudflare
Source: https://github.com/freedomw1987/tree_monstor/tree/main/skills/devops/node-static-proxy-cloudflare
Command: npx skills add https://github.com/freedomw1987/tree_monstor --skill node-static-proxy-cloudflare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates common failures when starting a Node.js static file server with API proxy functionality and a Cloudflare tunnel, including EADDRINUSE errors, connection refused issues, and zombie lingering processes caused by incorrect startup sequencing or poor process management.

Core Features & Use Cases

  • Sequential Startup Workflow: Enforces the correct order of operations (kill existing processes → start backend → start static proxy → start Cloudflare tunnel) to prevent port conflicts.
  • Process Management Best Practices: Guides proper use of background process handling and log redirection to avoid orphaned processes.
  • Troubleshooting & Edge Case Handling: Includes fixes for common errors like Vite config loading issues, custom hostname authentication requirements, and NAT server detection.
  • Use Case: When deploying a full-stack web app with a separate backend API, use this Skill to expose the frontend and proxy API calls publicly via Cloudflare Tunnel without running into process or port conflicts.

Quick Start

Use the node-static-proxy-cloudflare skill to start your static proxy server and Cloudflare tunnel in the correct sequence to avoid port conflicts and process errors.

Frequently Asked Questions about node-static-proxy-cloudflare

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

FAQPage Schema
How do I fix EADDRINUSE errors when starting a Node.js static server with a Cloudflare tunnel?

To fix EADDRINUSE errors when starting a Node.js static server, you must kill lingering processes and enforce a sequential startup workflow to clear port conflicts. This Skill implements that exact port conflict resolution process.

Why does my Cloudflare tunnel show connection refused issues with my Node.js API proxy?

Connection refused issues occur because the backend API starts out of sequence. Starting the backend first, then the static proxy, and finally the Cloudflare tunnel with readiness verification ensures the API is listening before the tunnel connects.

What is the correct startup sequence for a Node.js full-stack app using a Cloudflare tunnel?

The correct startup sequence for a full-stack Node.js app is killing existing processes, starting the backend, starting the static file proxy, and finally starting the Cloudflare tunnel. Sequential readiness verification prevents process errors.

Can I use a Node.js static file server to proxy API calls publicly through a Cloudflare tunnel?

Yes, you can use a Node.js static file server to proxy API calls publicly via a Cloudflare tunnel. This Skill handles the sequential process startup and tunnel URL extraction needed to expose your full-stack web application without port errors.

How do I prevent orphaned zombie processes when running a Node.js static proxy and Cloudflare tunnel?

Orphaned zombie processes are prevented by applying proper background process handling and log redirection. This Skill provides process management best practices to ensure clean teardown and sequential startup of the Node.js server and tunnel.