dsh-wsl-port

You have a server running inside WSL 2, yet Windows simply will not reach it on 127.0.0.1. Is the port even listening? Should you be hitting the eth0 IP instead? Is a firewall rule in the way? port_doctor answers all of that in one shot.

Under the hood it does three things: it reads hostname -I to surface the real WSL IP, checks the target TCP port with ss to confirm a LISTEN state, and then walks you through Windows-side localhost-forwarding recommendations—when a wsl --shutdown reset is needed, which firewall rules to add, and how to bridge the two networks. The default port is 3080, the common DeepSeek Harness web endpoint, but you can pass any port you need.

Built for engineers who develop in WSL2 and debug services from the Windows host browser. It ships as part of the dsh-wsl-kit suite and slots neatly into the daily, llm, and github scenario presets so you can verify connectivity before diving into application-level issues.