Ports

Find listening ports, inspect process and related resources, and run allowlisted actions.

What this is

PortPilot’s core object is a listening binding: protocol, bind address, and port, plus the process that owns it.

Port detail
Port detail

You see what is actually listening instead of guessing from config files — including Docker publishes and reverse-proxy routes when they are detected.

Prerequisites

Agent running. Pairing required only for the website fleet view.

Where to look

  • Desktop: Ports
  • Website: Ports (fleet table) and Machines → port detail
  • CLI: portpilot ports and portpilot port <n>

Search from the website search box or Cmd+K filters (for example port:3000, docker:yes). Diagnose and filter work when the machine is online.

Port detail includes process, service (when identified), health, history, Docker/proxy/tunnel relations, and controls you are entitled to run.

Port actions

Only these controls exist. There is no arbitrary shell. Confirmation depends on your automation preference (Safe / Smart / Developer) on the website.

ActionLabelWhen to useRiskConfirmation
KillKill processStop the owning processHigh — the process exitsUsually yes
Restart serviceRestart serviceBounce an identified OS serviceMediumOften
Start / stop serviceStart service / Stop serviceService mapped to the portStop is high impactStop usually yes
Firewall allowAllow TCP inboundOpen inbound TCP (Pro)Medium — exposes the portOften
Firewall blockBlock TCP inboundBlock inbound TCP (Pro)High — can cut remote accessUsually yes
Remove PP ruleRemove PortPilot ruleUndo a PortPilot firewall ruleMediumOften
ExposeExpose (tunnel)Public ngrok URL (Pro)High — public internetUsually yes
Stop / restart tunnelStop tunnel / Restart tunnelTear down or recycle ngrokMediumOften

Bare PID restart without a service identity is not supported. Docker containers cannot be started or stopped from PortPilot.

Expected result

Bindings refresh while the agent is running. History survives agent restarts in local SQLite.

Common problems

SymptomRecovery
Port not appearingProcess not listening; rescan; portpilot ports on the host
Stale rowsMachine offline — controls will not queue
Action missingEntitlement (firewall/tunnel are Pro/Cloud) or helper down
Kill failedProcess already exited, or ProcessGuard mismatch — rescan

Related: Processes, Services, Firewall, Tunnels, Docker, Reverse proxies, Diagnostics.

Download PortPilot · FAQ · Support