Tag: Port Binding

Conflicts or failures when applications attempt to bind to ports.

ID	Title	Description	Category	Technology	Tags
CRE-2025-0130 High Impact: 9/10 Mitigation: 3/10	Supabase Self-Hosted: Postgres Container Fails to Start Due to Port Conflict	Detects when Supabase self-hosted Postgres container fails to start because another service is already using port 5432. This is a common issue during initial setup or when multiple Postgres instances are running on the same host. The failure prevents the entire Supabase stack from starting properly.	Database Problems	supabase	Supabase PostgreSQL Port Binding Configuration Startup Failure Self-Hosted Container Crash Public
CRE-2025-0136 Medium Impact: 8/10 Mitigation: 3/10	Supabase Self-Hosted: Auth Service Fails Due to Port Binding Conflict	Detects when Supabase Auth service (GoTrue) fails to start because the configured port is already in use by another service. This prevents user authentication, registration, and all auth-related operations from functioning in the self-hosted Supabase deployment.	authentication	docker	Supabase Authentication Port Binding Configuration Startup Failure Self-Hosted GoTrue Public