Troubleshooting

Clash Verge Port Already in Use (7890/7897): Find the PID and Free It

Port-in-use almost always means another local listener owns the mixed port—old Clash, v2rayN, NekoRay, boosters, browser proxy extensions, or a leftover core. 7890/7897 are common defaults; trust the port shown in the client.

Find the occupant, then kill it or change Clash Verge Rev’s port—and sync every place that hardcodes the old port.

Order of operations

  1. Quit other proxy apps, including tray leftovers.
  2. End leftover clash/mihomo/verge processes.
  3. If still busy, change the mixed port (e.g. 17890).
  4. Sync system proxy, extensions, Git/npm/env, IDE proxies (CLI proxy, Cursor).

Who usually holds the port

Occupant Typical port Fix
Old Clash / Clash Verge core 7890 / 7897 End the process, then start fresh
v2rayN / NekoRay 7890 / 10809 Quit from tray, not just the window
Browser proxy extension 7890 / 1080 Disable its local proxy listener
Leftover service from a prior build mixed port Uninstall or repair Service Mode

Find the PID

Map port → PID → process, then end only the confirmed occupant.

netstat -ano | findstr :7890
tasklist /fi "PID eq 12345"

lsof -iTCP:7890 -sTCP:LISTEN -n -P
kill -9 12345

Resource Monitor → Listening Ports is the GUI equivalent on Windows. If it won’t die, reboot, start Verge Rev, and keep the new port before old autostart tools return.

Allow LAN phones

Update the phone Wi‑Fi proxy port too (LAN share).

When it isn’t a port fight

system proxy, firewall, logs.

Stop

Don’t keep multiple proxy clients “just in case.” Builds: download center.

Port fixed? Check your client build too

Older builds are more likely to leave proxy services and stale port settings behind. Confirm you are on the latest release, then re-enable the system proxy.