dsh-web-advanced-settings: LAN Listening and NIC Exposure Control for DeepSeek Harness

What Does It Do?

It is a DSH plugin for DeepSeek Harness that adds a dedicated "Advanced Listening Settings" section to the DSH Web GUI settings, exposing the web service to the local network with per-NIC IP control. It solves the problem of host-side restrictions breaking under remote access without requiring an extra reverse proxy, covering both 0.0.0.0 global listening and direct per-IP passthrough. Maintained by jcjyids under the MIT license, it is a standard DSH bundle plugin with separate host-side and browser-side halves, targeting the web profile and Node ≥ 22.6.

Core Features

• Global listening and NIC selection: bind all interfaces via 0.0.0.0, or listen only on checked local IP addresses, with nothing checked meaning loopback only.
• Port and auth toggle: the service port defaults to 3080, with the command-line --port taking priority and graying out the input; token (401) validation can be removed so IP:port works directly.
• Entry header normalization: only requests whose Host is a local non-loopback IPv4 are rewritten, so remote pages look like loopback pages to the host.
• Access URLs and cleanup: a secondary page lists every usable entry URL with one-click copy and omits tokens when auth is off; another page shows managed blocks and file locations and cleans up legacy entries.
• Zero residue and one-click restart: nothing is written until configured, everything can be reclaimed, and the panel can relaunch a new instance in the background after confirmation.

How to Use This Plugin?

After enabling it in DSH and restarting once, open Settings → Advanced Listening Settings to begin. For LAN access, check the relevant NIC IPs or turn on global listening and adjust the port as needed; to let remote clients connect directly, disable authentication, but note that anyone who can reach the address can then control your DSH, so keeping token auth or restricting it to a fully trusted network is advised. A self-check endpoint confirms whether entry rewriting is active, and before uninstalling you should run the full cleanup so no state files or managed blocks are left in the profile.

How to Troubleshoot This Plugin?

If startup fails, the plugin already guards against initialization errors, skipping only itself without affecting the host, so it can be removed first while you investigate. If the harness cannot start at all, manually delete the plugin's managed block from the composition-layer patch file as described in the official instructions. A firewall prompt on Windows when first binding a non-loopback address is operating-system behavior, not plugin behavior. After upgrading DSH, re-run the test suite and confirm the panel still opens.