openhands-enterprise-troubleshooting skillA
openhands-enterprise-troubleshooting is agent-read markdown (skill) from openhands/extensions: This skill should be used when a user reports an issue with OpenHands Enterprise (OHE) on a self-hosted (Replicated VM-based) installation. Use for diagnosing sandbox startup failures, auth issues, certificate errors, LLM connectivity problems, Keycloak login issues, Replicated Admin Console access, upgrade failures, or resource exhaustion. Helps triage symptoms, run diagnostic commands, guide through recovery steps, generate and analyze Replicated support bundles offline, and produce escalation.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# OpenHands Enterprise Troubleshooting This skill helps diagnose and resolve common issues on OpenHands Enterprise (OHE) self-hosted installations using Replicated. It covers triage, guided recovery, support bundle generation, and escalation handoffs. ## Diagnostic Workflow When a user reports an OHE issue: 1. **Collect symptoms** - Ask user to describe what they see, error messages, when it started 2. **Identify failure mode** - Match symptoms to one of the common issues below 3. **Run targeted diagnostics** - Use commands in `references/diagnostics.md` 4. **Guide recovery** - Follow resolution steps for the identified issue, one at a time 5. **Verify fix** - Confirm the original symptom is gone, not just that the last command succeeded 6. **Generate handoff** - If unresolved, produce a clear summary for the OpenHands team Take recovery one step at a time. Before each step, state what it will change and what you expect to see afterwards; after it, run the check that confirms it before moving on. If the check fails or shows something unexpected, stop and re-diagnose — a step applied on top of a failed one buries the …
Read the whole file at its exact version.
How to install
mdr add openhands/extensions/openhands-enterprise-troubleshooting@git:20260911.ce62975mdr add openhands/extensions/openhands-enterprise-troubleshooting@sha256:b7baa048b8fbcbb9Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_zdd4mbuzcgjwlv6h)
0 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15206 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
openhands/extensions · 150 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zdd4mbuzcgjwlv6h GET https://markdownregistry.com/api/v1/resolve?ref=openhands/extensions/openhands-enterprise-troubleshooting GET https://markdownregistry.com/api/v1/blob/b7baa048b8fbcbb971dd0be8d96104689091b58304ffea276819ad0fabd51382
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.