DSH Management ConsoleStandalone console
Reconnecting

DSH lifecycle

Start, stop, or restart DSH while the container and management console remain running.

Reset runtime

Rebuild the runtime from verified DSH files and current platform patches without deleting user data.

Live logs

View runtime logs from DSH and platform modules.

Connecting

No logs yet

Restore Stable state

The following data snapshot will be restored and newer data will be lost: -

Restart DSH?

The current DSH connection will be interrupted briefly. This console remains available.

Stop DSH?

DSH remains stopped until it is started here or the container restarts. The management console remains available.

Destination already exists

Choose how to handle:

Edit file

Proxy scope guide

How managed network sources are classified.

Outbound proxy component unavailable

The DSH Docker outbound proxy component is unavailable. Settings can still be saved, but managed proxy traffic and connection tests may fail. This does not indicate whether the configured external proxy is reachable.

Built-in direct rules

These platform-managed local destinations are always direct and do not need to be entered again.

Connection test

Tests the form values without saving or activating them.

    Set up two-factor authentication

    Scan the QR code with an authenticator app, then enter its current code.

    Management isolation comparison

    Both modes require authentication and final-execution authorization. A separate origin additionally isolates the full Management session from DSH client plugins.

    CompatibilitySeparate originSeparate DSH and Management sessionsYesYesProtect from same-origin DSH client pluginsNoYesFinal-execution capabilitiesYesYesProtection after DSH obtains container RootNoNo

    Enable separate Management origin?

    Publish container port 3081 or route a separate address to it. The platform verifies the candidate before changing the current mode.