AI Agent Hub
Back to plugins
🧰

dsh-https-fix

Web Tools Updated 2026.09.15

Run the following command in DeepSeek Harness:

dsh plugin install MingYU-kalo/dsh-https-fix

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install MingYU-kalo/dsh-https-fix in a DeepSeek Harness terminal to install this plugin; the full source is available at https://github.com/MingYU-kalo/dsh-https-fix

About this plugin

dsh ships its Web GUI bound to 127.0.0.1 with no official extension API, so accessing the agent settings page from another machine is essentially out of the question. dsh-https-fix solves all of that in a single plugin install: it stands up a built-in TLS reverse proxy, registers trusted domains at runtime against trustedHosts, and hot-patches the dsh client-connection layer to lift the loopback restriction — no nginx, no extra startup flags required.

On the certificate front, a self-signed cert for a public IP is generated automatically when no domain is available; if you do have one, simply point the plugin at your Let's Encrypt or internal CA cert and key. Security defaults to a username-and-password login gate (passwords stored as SHA-256, sessions last seven days), and the plain-HTTP external route can be switched off with one click. After installation, run the 12-point health check and confirm every item goes green.

This plugin is aimed at self-hosters who want their dsh agent reachable over a LAN or the internet without maintaining a separate reverse-proxy stack. One critical caveat: the patch is applied to dsh source files at runtime, so the plugin version must exactly match the installed dsh release. Always disable the plugin or switch to the corresponding branch before upgrading dsh, or the application will fail to start.

Use Cases

  • Access the dsh Web GUI securely from other devices on the LAN or internet
  • Enable HTTPS via self-signed cert on a public IP without a domain name
  • Add an encrypted, login-gated channel for the dsh agent settings page in a self-hosted setup

Best For

  • Individual developers self-hosting dsh who need remote device access
  • Lightweight ops users who want built-in TLS instead of a separate nginx stack
  • Team leads who need to enforce authenticated, encrypted access to their dsh agent