WHOSEPORT
Investigations · guide

A setting points at the wrong place

A URL or port in .env that does not match anything running. Compare where it points with what actually listens.

Ask

bash
whoseport ask "the frontend cannot reach the API"

What WhosePort checks

  • Host and port targets of URL-like variables in each project .env
  • The listeners and services actually running
  • Recent logs of the service that fails

Typical root cause

The .env points at an old port, or the process started before the file was changed and never picked it up.

Proposed fix

  • update_runtime_config on the one key (approval required, original backed up)
  • restart_process so the new value is read (approval required)
Approval
Every step that changes your machine is a typed action classed by the policy engine. It waits for your approval in the dashboard, which shows the target, risk and expected effect first. A changed .env file is backed up before it is written. See /docs/policy.

Verification

  • The target port is listening
  • The failing request now succeeds