برای من ران نمیشه و این خطا رو میده

[vahid20162016]

2026-05-04T07:47:33.891480200Z [ui] proxy stopped
2026-05-04T07:47:34.986138000Z [ui] starting proxy...
2026-05-04T07:47:34.986717Z INFO Loaded MITM CA from C:\Users\pc\AppData\Roaming\mhrv-rs\config\ca/ca.crt
2026-05-04T07:47:34.986749200Z [ui] listening HTTP 127.0.0.1:8085 SOCKS5 127.0.0.1:8086
2026-05-04T07:47:34.986754Z INFO tunnel mux: 1 deployment(s), 30 concurrent per deployment
2026-05-04T07:47:34.986756Z INFO batch coalesce: step=10ms max=1000ms
2026-05-04T07:47:34.986989800Z [ui] proxy error: io: Only one usage of each socket address (protocol/network address/port) is normally permitted. (os error 10048)
2026-05-04T07:47:34.986992900Z [ui] proxy stopped

[therealaleph]

@vahid20162016 — Only one usage of each socket address (os error 10048) is Windows reporting that port 8085 or 8086 is already in use by another process. Two common causes:

1. Another instance of mhrv-rs is still running. Even after you closed the UI, the background process may have lingered. Check Task Manager for mhrv-rs.exe or mhrv-rs-ui.exe — kill any lingering instances, then restart.

2. Another app on your machine is using those ports. Run in PowerShell or cmd:

netstat -ano | findstr ":8085 :8086"

If you see another PID, look it up in Task Manager (View → Select Columns → PID). Common culprits: a previous Python upstream client, another local proxy (Shadowsocks, Xray-Windows-GUI), or a development tool (Node.js dev server, WebpackDevServer).

3. After kill, reboot if persistent. Sometimes Windows holds the port in TIME_WAIT after a crash for ~2 minutes. If neither step 1 nor 2 finds the culprit, just reboot.

Workaround if ports are needed: change the proxy ports in config.json:

"listen_port": 18085,
"socks5_port": 18086

Then point your browser at 127.0.0.1:18085 instead.

می‌بندم — اگه بعد از kill کردن instances + check netstat همچنان error می‌گیری، خروجی netstat -ano | findstr ":8085 :8086" رو paste کن.

---

_{[reply via Anthropic Claude | reviewed by @therealaleph]}