Back to issues
Low priorityTested by MilanVerified fix

VPS Deploy: Port Already In Use

If you are seeing this exact OpenClaw issue, the fastest path is to confirm the likely cause, then work the recovery steps in order without skipping the full restart and retest sequence.

MilanLast updated Mar 3, 2026Verified recovery sequence documented in this repo

Likely Cause

A previous OpenClaw process is still running or another service already owns the configured port.

Tags

VPSDeploy

Recovery Steps

  1. 1Run lsof -i :3000 to find the process using the port.
  2. 2Stop or kill the old process cleanly.
  3. 3Change the configured port if another service should keep using 3000.
  4. 4Delete stale PM2 processes if you use PM2.
  5. 5Restart with the updated port and verify the reverse proxy target.

Issue FAQ

These answers are written to be self-contained, so you can confirm the likely problem before you start changing your setup.

After deploying to a VPS, OpenClaw fails with 'EADDRINUSE: address already in use :::3000'. In most cases, the underlying issue is a previous OpenClaw process is still running or another service already owns the configured port.

Work through the recovery steps in order and fully restart OpenClaw before retesting. Skipping the restart or leaving stale auth/config state in place usually causes the issue to return.

Move to the related guide or service link below so you can rule out adjacent configuration problems instead of repeating the same failed steps.

Still blocked?

If the steps above do not clear it, review the full fixes index or book direct troubleshooting help.