dsh-reverse-proxy-xc

DSH's Web GUI is built for local loopback access. The moment you reach it through a reverse proxy on another LAN device, the frontend detects a non-loopback origin and locks down the settings panel, randomUUID throws under plain HTTP, and WebSocket streams silently drop. dsh-reverse-proxy-xc was written to fix that entire class of breakage in one go.

Under the hood the plugin spins up a standalone proxy on 0.0.0.0:3090 that forwards every request to the DSH main service at 127.0.0.1:3080. It rewrites Host and Origin headers back to loopback, injects the isLoopback=true flag into the HTML so the settings panel and credential manager unlock, ships a randomUUID polyfill for non-secure contexts, and handles WebSocket via streaming pass-through. The net effect is that a phone or tablet browser sees the exact same sidebar, session list, settings, and real-time event stream as a desktop session on localhost.

The intended audience is anyone who wants a DSH touchpoint outside the primary machine: checking conversations from a tablet in the living room, tweaking API credentials from a second workstation, or sharing a read-through entry point with a small team over a trusted intranet or VPN. It is deliberately restricted to LAN and VPN use, ships disabled by default, and requires a single toggle in the DSH settings panel to go live.