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