dsh-remote-gateway

DSH intentionally keeps its privileged browser capabilities on loopback, so a plain reverse proxy that lets a remote browser render the page will immediately run into broken settings, failed plugin-bundle loads, dropped WebSockets, and host-directory-selection errors. dsh-remote-gateway slots in between your authenticated reverse proxy and the internal DSH server as a narrow compatibility layer, passing through unrelated plugin assets byte-for-byte while patching only the exact connection probe so the remote UI stays fully functional.

The gateway proxies HTTP, SSE, and WebSocket traffic in parallel, rewrites the upstream Host and Origin to the loopback authority, and strips every edge-authentication and forwarded-client-identity header before a request reaches DSH. When a remote user needs to pick a workspace directory, the native OS file dialog is transparently replaced by DSH's in-app filesystem browser, removing a common source of privilege leakage. The gateway also starts and stops with the DSH plugin lifecycle, so an existing systemd, launchd, or other supervisor handles it automatically.

If you already run DSH locally under a process supervisor and want a small trusted team to reach it over an authenticated, TLS-terminating reverse proxy, this plugin is the lowest-friction bridge. The source-IP allowlist adds a second, independent gate on top of the proxy's own access control, making sure only the single gateway address you designate can ever speak to the loopback-bound DSH server.