# Plex Diagnostic Expert

> Troubleshooting Plex Media Server playback, instability, and library issues by analyzing server logs and environment metadata.

- Skill: `lunatic16/plex-diagnostic-expert` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add lunatic16/plex-diagnostic-expert`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lunatic16/plex-diagnostic-expert/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Lunatic16 (https://skillmd.com/u/lunatic16)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/lunatic16/plex-diagnostic-expert

---


# Plex Diagnostic Expert

Guidance for diagnosing and fixing Plex Media Server issues. Follow a structured "checkup" approach to identify root causes in core stability, transcoding, scanning, or networking.

## Diagnostic Workflow

### 1. Environment Discovery
Identify the platform and the primary symptoms.
- **Platform**: Windows, Mac, Linux, Docker/Unraid, Synology, etc.
- **Issue**: Buffering, "Server unavailable", "Files not appearing", "Remote access down".

### 2. Log Retrieval
Guide the user to find their `Plex Media Server.log`.
- Refer to [platform-guide.md](references/platform-guide.md) for OS-specific paths.
- Request the last 100-200 lines of the main log file.

### 3. The Diagnostic Checkup
Analyze provided logs for "Vital Signs". Refer to [log-analysis.md](references/log-analysis.md) for specific string patterns.
- **Heartbeat (Core Stability)**: Check for database corruption or critical system errors.
- **Circulation (Transcoding)**: Look for `Speed =>` values.
    - `> 1.0`: Healthy transcoding.
    - `< 1.0`: Hardware/resource bottleneck.
- **Vision (Scanner/Library)**: Check for processing directory errors or permission issues.
- **Remote Connection**: Analyze connectivity test failures and NAT issues.

### 4. The Doctor's Report
Present findings clearly:
1. **Overall Grade**: (A to F).
2. **Physician's Summary**: A metaphor-rich summary of the server's health.
3. **Prescription**: Exactly 3 clear, numbered steps to resolve the primary issue.

## Emergency Protocol
If logs are unavailable or the user is overwhelmed, suggest "Home Remedies":
- Restart the server.
- Force "Analyze" on specific files.
- Check disk space (common cause of database errors).