Service directory and comparison

Localhost ports hub

A port is a numbered connection point, not an application identity. Use this directory to form a hypothesis, then confirm it from the process, startup log, protocol, and HTTP response.

9 maintained port guides6 free browser toolsUpdated September 6, 2026

Localhost developer tools

Generate

Port Command Generator

Build copy-ready listener, process, HTTP, WSL, and Docker checks.

Parse

Port Output Parser

Turn netstat, PowerShell, ss, lsof, and Docker output into a readable table.

Visualize

Docker Port Mapper

Map Compose host ports to services and find conflicts or exposed bindings.

Diagnose

CORS Header Analyzer

Check origins, credentials, methods, request headers, and preflight responses.

Understand

Localhost URL Explainer

Break down origins, effective ports, paths, queries, fragments, IPv4, and IPv6.

Review

Framework Config Linter

Check common framework ports, bind addresses, overrides, and risky settings.

Choose a port guide

Frontend · Node

:3000

React, Next.js, Express, and other configurable development servers.

Python · APIs

:5000

Flask and other local backends; verify the route and bind address.

Frontend · Vite

:5173

Vite’s documented default, automatic fallback ports, and host configuration.

Python · Django

:8000

Django’s development default plus FastAPI and file-server distinctions.

Java · Proxies

:8080

Spring Boot, Tomcat, reverse proxies, containers, and GeoServer contexts.

TLS · Admin

:8443

A common HTTPS alternative used by Java and network-management tools.

Data science

:8888

Jupyter token URLs, fallback ports, kernels, and secure remote access.

Tools · Services

:9000

A shared convention used by SonarQube, MinIO consoles, Portainer, and custom apps.

Elasticsearch

:9200

Authenticated HTTPS checks for Elasticsearch’s HTTP API.

Port comparison

PortCommon associationUsually open withImportant distinction
3000Next.js, React tooling, Node appshttp://localhost:3000Frameworks can be configured to any free port.
5000Flask and custom APIshttp://localhost:5000An API may return JSON or 404 at the root.
5173Vitehttp://localhost:5173Vite may move to 5174 when 5173 is busy.
8000Django development serverhttp://localhost:8000/admin/ exists only when the project maps it.
8080Spring Boot, Tomcat, proxieshttp://localhost:8080A 404 can mean the context path, not the server, is wrong.
8443Alternative HTTPShttps://localhost:8443HTTP sent to a TLS endpoint produces misleading failures.
8888Jupyter ServerTokenized URL from jupyter server listAuthentication is separate from kernel startup.
9000Multiple unrelated servicesCheck the product log firstNever infer SonarQube, MinIO, or PHP-FPM from the number alone.
9200Elasticsearch HTTP APIOften authenticated HTTPS9300 is node transport; 5601 is commonly Kibana.

One diagnostic sequence for any port

  1. Read the application’s startup log

    Use the exact address, port, protocol, and base path printed by the process.

  2. Confirm the listener

    # Windows PowerShell — replace 3000 with the target port
    Get-NetTCPConnection -LocalPort 3000 -State Listen
    
    # macOS or Linux
    lsof -nP -iTCP:3000 -sTCP:LISTEN
  3. Probe the protocol directly

    Use curl -i for HTTP, but do not force HTTP onto a known HTTPS service. A status response proves more than a browser’s generic error page.

  4. Inspect the application layer

    Once connected, use the response status and server logs to distinguish a missing route, rejected credentials, proxy failure, or application exception.

Focused troubleshooting

Connection errors

localhost:3000 not working

Resolve connection refused, port conflicts, Docker/WSL binding, and blank-page failures.

GeoServer

GeoServer on port 8080

Check the application context, account configuration, and data directory.

WordPress

Local wp-admin access

Separate web-server reachability, the WordPress path, and login recovery.

How this directory is maintained

Associations are presented as conventions, not guarantees. Each maintained guide links product defaults to official documentation and starts with a process-level check. See our editorial and correction policy.