Troubleshooting
Diagnose and resolve Ludus deployment, networking, template, WireGuard, Proxmox, and Ansible issues. Use when users report failures, errors, unreachable systems, failed joins, or unexpected behavior during build or deploy.
Install
$ agentstack add skill-badsectorlabs-ludus-skills-troubleshooting ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-badsectorlabs-ludus-skills-troubleshooting) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Ludus Troubleshooting
Use this skill to triage user-reported failures quickly, categorize errors, and provide targeted remediation steps.
Diagnostic Workflow
- Gather context and exact error output.
- Check range deployment status and recent errors.
- Review deployment logs for failure details.
- Identify the failure category using the known error catalog.
- Inspect the current range config for misconfigurations.
- Provide targeted fixes with concrete steps.
- Define clear verification steps to confirm recovery.
Key Diagnostic Information
When triaging, gather these in order of usefulness:
- Range status — is the deployment running, failed, or complete?
- Deployment errors — the most recent error output from a deploy.
- Deployment logs — full log stream for tracing failure context.
- Template status — are required templates built and available?
- Range config — does the YAML match what the user intended?
- Testing mode status — is testing mode active, and are network rules in effect?
Common Patterns
- Network issues often trace back to dnsmasq or NAT bridge state.
- Ansible failures often involve WinRM (Windows) or SSH reachability (Linux).
- Domain join failures usually involve DNS ordering or timing.
- Template failures are commonly ISO download or disk-space related.
References
- Use
references/common-errors.mdfor known errors, root causes, and fix procedures. - Use
https://docs.ludus.cloud/docs/troubleshooting/clientfor client and CLI troubleshooting details. - Use
https://docs.ludus.cloud/docs/troubleshooting/network/andhttps://docs.ludus.cloud/docs/troubleshooting/wireguard/for network and connectivity issues. - For uninstalling Ludus, direct users to the official guide at
https://docs.ludus.cloud/docs/troubleshooting/uninstallrather than performing the steps yourself.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: badsectorlabs
- Source: badsectorlabs/ludus-skills
- License: MIT
- Homepage: https://docs.ludus.cloud/docs/using-ludus/mcp
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.