dsh-Webroad

DSH Web is intentionally bound to 127.0.0.1, which means accessing it from a phone or a remote network requires manual config edits, ad-hoc tunneling, and constant fights with trust fences. dsh-Webroad collapses that entire workflow into one built-in panel on the DSH settings page called Mobile Access: a QR code, a PIN, and a toggle — scan and you are in, no terminal required.

Under the hood the plugin handles the full mobile and remote pipeline. For LAN use the proxy binds to 0.0.0.0:3081 automatically; a phone on the same Wi-Fi simply scans the local QR, types the 8-digit PIN, and connects. For public access a single click launches a cloudflared quick tunnel with no account or domain; every activation rotates the PIN and instantly invalidates the previous link. Long-lived sessions are protected by full WebSocket passthrough and a protocol-level heartbeat that survives NAT timeouts and mobile power-saving disconnects, with automatic reconnection. Large JSON responses are transparently compressed with gzip or brotli, turning a 17 MB conversation into about 1 MB of traffic. Security is multi-layered: separate LAN and public PINs, per-IP login rate limiting (5 attempts per 60 seconds), HttpOnly session cookies scoped to the dsh web process, and a header-rewrite reverse proxy so DSH trust fences always see a loopback address with zero changes to DSH configuration. Phone-specific patches add a browse directory picker, polyfills for crypto.randomUUID and AbortSignal.any, and a first-visit redirect straight into the current session for a near-native browser feel.

The sweet spot is everyday convenience: glancing at DSH sessions from bed on a phone, or jumping in over 4G while out and about. Power users who want a permanent domain can drop a Cloudflare named tunnel config into the plugin folder, or follow the included Tailscale Funnel guide for a fully manual path. In every scenario the setup is effectively install-and-forget: restart dsh web, open the settings panel, scan the QR, and the phone works.