Support for installation, permissions, and local troubleshooting.

This page is for real support work: installing the app, handling operating-system warnings, understanding permission failures, and knowing what details help us reproduce a problem.

  • Scope: local desktop use
  • Public binaries: Windows and macOS
  • Last updated: 2026-03-09

Install on Windows

  • Download the .exe from the home page or release notes page.
  • If Windows SmartScreen appears, verify the SHA-256 hash listed on the release notes page before deciding whether to continue.
  • Start the app and run a first scan before assuming a port is free.

Install on macOS

  • Open the universal .dmg and move the app to Applications if that is your preferred workflow.
  • If macOS warns that the app was downloaded from the internet, review the source and allow it through Privacy & Security only if you trust the file.
  • Use the support email if the build opens but shows no data after launch.

Permission model

  • Basic local inspection can succeed without elevated rights.
  • Protected or cross-user processes may require administrator approval before termination works.
  • Failure to kill a process does not always mean the app is broken; the operating system may be doing the right thing.

What to check before emailing support.

Most local port problems become much easier to diagnose when you narrow them down to one reproducible case.

The app starts but no ports appear

  • Make sure there are active local services to inspect.
  • Clear filters and search terms.
  • Run a manual refresh.
  • If you expected a protected process, try launching with the permissions your OS requires.

A port still appears occupied after you stopped the app that used it

  • Check the socket state. A lingering entry is not always the same as an active listener.
  • Refresh once or twice before killing another process.
  • Read the command line to see whether a helper process or watcher restarted the service.

The terminate action fails

  • The target process may have already exited.
  • The OS may require elevated rights or block the action because the process belongs to another user or is protected.
  • Restarting the parent service gracefully is often safer than forcing a kill.

Security warning during download or first launch

  • Confirm the file name, size, and hash from the release notes page.
  • Check that you downloaded from the canonical domain whousemyport.com.
  • Do not bypass a warning unless the file matches the published build details.

Need a second pass from OpenClaw?

If you are using the current source build with Export for OpenClaw, copy the structured report before emailing support or asking an agent for help. It is easier to reason about than a screenshot because it includes search filters, socket state, PID, and command fields in plain text.

  • If OpenClaw uses this repository as its workspace, the bundled skill can be discovered directly from skills/whousemyport-port-diagnostics.
  • You can also download whousemyport-port-diagnostics.SKILL.md directly from this website and place it in the expected skill folder.
  • If not, run npm run openclaw:install-skill or bash scripts/install-openclaw-skill.sh from the repository root.
  • If your public binary does not have the export button yet, include the same rows manually when you ask for help.

Known limits of the current public website build

  • The app is for inspecting the local machine. It is not a remote asset scanner or network mapping platform.
  • This site currently publishes Windows and macOS binaries only.
  • Process termination depends on operating-system permissions and the state of the target process.
  • The documentation on this site tracks the public binaries linked here, not unreleased development builds.

Contact support

Email timesrunback@gmail.com and include enough detail for the problem to be reproduced on a real machine.

  • Your operating system and version.
  • The port number you expected to inspect or free.
  • Whether the issue happened during scan, filtering, or termination.
  • An OpenClaw report from the app if your build supports it, or a screenshot if it does not.
  • Any security prompt or permission error you saw.

FAQ

Can support log into my machine or debug remotely?

No. Support is limited to email-based troubleshooting using the information you provide.

Does the app expose remote host scans or host discovery?

No. The current public build focuses on local socket ownership and process inspection.

Where should I look for version numbers and file hashes?

Use the release notes page. It lists the current public version, file sizes, and SHA-256 hashes for the linked binaries.

Can I use OpenClaw instead of sending screenshots?

Yes, if your build includes the export button. The setup and supported install paths are documented on the OpenClaw page.

Where are data use and advertising disclosures documented?

Those live in the privacy page, which covers both the desktop app and the website.