DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in
All documentation

Get started

Distribute a Carefully Tuned Agent Harness with PresetsWrite Your First DSH Plugin

Architecture

The Cordis Plugin Model Behind DSHFrom a Service to a Complete Agent CapabilityHow Bundles, Profiles, and Patches Compose DSHWhy DSH + Cordis Is Different

Build and publish

Plugin HMR Not WorkingPlugin Not Showing Up After Publishing

Troubleshooting

Troubleshooting Plugin Install FailuresDSH Version IncompatibilityResolve ERR_PNPM_IGNORED_BUILDSTroubleshoot Cordis Startup FailuresPreset Not Found or Cannot Be ResolvedTroubleshoot a Blank DSH Web UIlocalhost:3080 Is Unreachable
Plugin Hub/Documentation/Troubleshooting

Troubleshooting

localhost:3080 Is Unreachable

Check the listener, port conflicts, container mapping, and remote-access boundary.

Maintained by the Plugin Hub community2 sections
What you will learn

Check the listener, port conflicts, container mapping, and remote-access boundary.

Confirm the listening process

After starting DSH, inspect port 3080 on the same machine. No listener means the service has not bound the port, so review the earliest startup error. If another process owns the port, identify it before stopping a stale instance or selecting another port. Do not terminate an unrecognized system process.

bash
lsof -nP -iTCP:3080 -sTCP:LISTEN
curl -v http://127.0.0.1:3080/
ps -p <pid> -o pid,ppid,command

Check container and remote-access boundaries

A container service bound only to 127.0.0.1 can remain unreachable through host port mapping. Bind to an appropriate interface and publish the port when host access is required. Add authentication, a firewall, and a trusted reverse proxy before internet exposure; keep development servers off the public internet.

text
container listener: 0.0.0.0:3080
host mapping: 127.0.0.1:3080 -> container:3080
remote access: authenticated reverse proxy or SSH tunnel

Continue reading

Continue reading

TroubleshootingTroubleshooting Plugin Install FailuresGetting errors when installing a plugin? Follow this checklist to diagnose package name, manifest, version format, and network issues.TroubleshootingDSH Version IncompatibilityHow to diagnose and fix version range mismatches between a plugin's declared compatibility and your DSH environment.TroubleshootingResolve ERR_PNPM_IGNORED_BUILDSReview dependency build scripts blocked by pnpm and approve only the packages required for installation.

On this page

OverviewConfirm the listening processCheck container and remote-access boundaries