Port 54322: Supabase Local PostgreSQL — Supabase CLI Local PostgreSQL Database Instance
Default local PostgreSQL port exposed by `npx supabase start` (`postgresql://postgres:postgres@127.0.0.1:54322/postgres`).
How to Check & Kill Process on Port 54322 (EADDRINUSE Fix)
# Find process using port 54322 sudo lsof -i :54322 # Instantly kill process on port 54322 lsof -ti:54322 | xargs kill -9
# Find PID listening on port 54322 netstat -ano | findstr :54322 # Force kill by PID taskkill /PID <PID_NUMBER> /F
# Kill port 54322 via npx npx kill-port 54322 # Or diagnose via Castov CLI npx castov fix "EADDRINUSE :::54322"
# Test if port 54322 is reachable nc -zv localhost 54322 # Allow or deny port 54322 in UFW sudo ufw allow 54322/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 54322
What is Port 54322 used for?
Port 54322 is the standard network port for Supabase Local PostgreSQL (Supabase CLI Local PostgreSQL Database Instance) operating over TCP. The typical system daemon or process is docker-proxy (postgres).
How do I kill a process running on Port 54322 (EADDRINUSE)?
On macOS and Linux, run: lsof -ti:54322 | xargs kill -9 (or npx kill-port 54322). On Windows PowerShell/CMD, run: netstat -ano | findstr :54322 and then taskkill /PID <PID> /F.
Is it safe to expose Port 54322 to the internet?
Port 54322 has a Medium security risk profile. Default local PostgreSQL port exposed by `npx supabase start` (`postgresql://postgres:postgres@127.0.0.1:54322/postgres`).