Port 8787: Cloudflare Workers (Wrangler Dev) — Cloudflare Wrangler Local Edge Runtime (workerd)
Default local development port when running `npx wrangler dev` for Cloudflare Workers and Pages Functions.
How to Check & Kill Process on Port 8787 (EADDRINUSE Fix)
# Find process using port 8787 sudo lsof -i :8787 # Instantly kill process on port 8787 lsof -ti:8787 | xargs kill -9
# Find PID listening on port 8787 netstat -ano | findstr :8787 # Force kill by PID taskkill /PID <PID_NUMBER> /F
# Kill port 8787 via npx npx kill-port 8787 # Or diagnose via Castov CLI npx castov fix "EADDRINUSE :::8787"
# Test if port 8787 is reachable nc -zv localhost 8787 # Allow or deny port 8787 in UFW sudo ufw allow 8787/tcp
Deploying High-Availability Cloud Servers, VPCs, or Managed Databases?
Reach backend engineers and SREs actively debugging ports, CIDR subnets, and production infrastructure.
Frequently Asked Questions about Port 8787
What is Port 8787 used for?
Port 8787 is the standard network port for Cloudflare Workers (Wrangler Dev) (Cloudflare Wrangler Local Edge Runtime (workerd)) operating over TCP. The typical system daemon or process is workerd / node.
How do I kill a process running on Port 8787 (EADDRINUSE)?
On macOS and Linux, run: lsof -ti:8787 | xargs kill -9 (or npx kill-port 8787). On Windows PowerShell/CMD, run: netstat -ano | findstr :8787 and then taskkill /PID <PID> /F.
Is it safe to expose Port 8787 to the internet?
Port 8787 has a Low security risk profile. Default local development port when running `npx wrangler dev` for Cloudflare Workers and Pages Functions.