43dcec8bd9
WHAT WAS DONE: Created comprehensive task documentation for fixing Whitelist Manager after Panel v1.12.1 API breaking changes PROBLEM IDENTIFIED: - Whitelist Manager built against Panel v1.11.x API (February 2026) - Panel upgraded to v1.12.1 on March 13, 2026 - API response format changed between versions - All servers showing "UNKNOWN" status - Server grouping broken (wrong counts, unknown servers) - Status detection completely broken ROOT CAUSE: Python code still parsing old v1.11.x API format. Panel v1.12.1 changed: - feature_limits → limits - whitelist → whitelist_enabled - Possible: environment variable structure - Possible: nested object changes IMPACT: - ❌ Status detection broken (all servers show UNKNOWN) - ❌ Server grouping broken (TX1 wrong count, unknown group appeared) - ✅ Core functions likely still work (add/remove player) - ✅ Workaround exists (use Panel console) TASK DETAILS: - Time estimate: 1-2 hours - Priority: Tier 3 (workaround exists) - Status: TO DO - BROKEN (needs fix when home) FIX PROCEDURE DOCUMENTED: 1. SSH to Billing VPS (38.68.14.188) 2. Check service logs for API errors 3. Test Pterodactyl API manually to see new format 4. Update Python code to parse v1.12.1 format 5. Add fallback support for v1.11.x (backward compatibility) 6. Test with live servers 7. Restart service 8. Verify all servers show correct status CODE CHANGES NEEDED (EXAMPLE): Before: server['attributes']['feature_limits']['whitelist'] After: server['attributes']['limits']['whitelist_enabled'] Plus: Add .get() safety, fallback to old format, better error handling CRITICAL REMINDER ADDED: **ALWAYS check Whitelist Manager after Panel or Wings updates!** Pterodactyl API can change between minor versions. After ANY Panel/Wings update: 1. Visit whitelist.firefrostgaming.com 2. Verify server statuses (not all UNKNOWN) 3. Check server grouping (correct counts) 4. Test add/remove player 5. If broken → Task #86 fix procedure PREVENTION DOCUMENTATION: - Post-update checklist created - Version compatibility matrix started - Health check endpoint design - API versioning notes - Best practices for defensive coding WORKAROUND UNTIL FIXED: Use Pterodactyl Panel console directly: 1. panel.firefrostgaming.com 2. Select server → Console tab 3. Commands: whitelist add/remove <username> FUTURE ENHANCEMENTS: - Panel version detection - API format auto-detection - /health endpoint for monitoring - Better error messages - Retry logic for failed API calls WHY THIS MATTERS: Whitelist Manager saves 96.7% time (15 min → 30 sec). That value is lost while broken. Fix is probably trivial (2-5 lines of code) but critical for operational efficiency. This also establishes pattern: Any Panel/Wings update can break integrations. Must test ALL custom tools after updates. FILES CREATED: - docs/tasks/whitelist-manager-v1-12-compatibility/README.md (10,500+ words) FILES MODIFIED: - docs/core/tasks.md (added Task #86) RELATED TASKS: - Task #7: Whitelist Manager (original deployment) - Task #47: Whitelist Manager Refinements (Mayview grouping) - Task #3: Pterodactyl Panel Update v1.12.1 (what broke it) Signed-off-by: The Versionist (Chronicler #49) <claude@firefrostgaming.com>
🔥❄️ Firefrost Gaming — Operations Manual
Document ID: FFG-ROOT-001
Version: 2.0
Last Updated: February 12, 2026
Status: 🟢 CURRENT
What This Is
The complete operational repository for Firefrost Gaming — a subscription-based Minecraft server network built on the philosophy of Fire + Frost = Where Passion Meets Precision.
This repository contains infrastructure documentation, deployment guides, planning documents, branding assets, consultant archives, and the relationship context that makes Firefrost more than just servers.
Current Infrastructure
6 Servers — 2 dedicated (Dallas, Charlotte) + 4 VPS (Dallas, Charlotte, Chicago x2)
12 Game Servers — 6 on TX1 (Dallas), 6 on NC1 (Charlotte)
8 Management Services — Gitea, Uptime Kuma, MkDocs, Code-Server, Automation, NextCloud, Wiki.js (Subscribers), Wiki.js (Staff)
Repository Structure
├── docs/core/ — Critical living documents (scope, manifest, tasks)
├── docs/relationship/ — Partnership context, consultants, legacy
├── docs/deployment/ — Service deployment guides
├── docs/planning/ — Strategy, design, roadmap, ideas backlog
├── docs/reference/ — Technical reference, architecture decisions
├── docs/external/ — Provider communications, friend assistance
├── docs/sandbox/ — Brainstorming sessions (Gemini, Claude)
├── docs/archive/ — Historical session logs and completed plans
├── automation/ — Deployment automation system
├── branding/ — Logos, backgrounds, visual assets
├── photos/ — Consultant photo archive (249 photos by year)
└── web/ — Nginx configurations
Key Documents
Start here: SESSION-HANDOFF-PROTOCOL.md → DOCUMENT-INDEX.md
For current server inventory, see docs/core/infrastructure-manifest.md (FFG-CORE-002).
For project scope and roadmap, see docs/core/project-scope.md (FFG-CORE-001).
The Team
- Michael "Frostystyle" Krause — Owner/Operator, Technical Lead (The Wizard)
- Meg "Gingerfury" — Community Manager (The Emissary)
- The Five Consultants — Jack, Oscar, Jasmine, Butter, Noir (They're family, not pets)
Document Standards
All documents follow FFG-STD-001 — the Firefrost Revision Control Standard. See docs/core/revision-control-standard.md.
Maintained By: The Wizard & The Chronicler
Fire + Frost + Foundation = Where Love Builds Legacy 💙🔥❄️
Revision History
| Version | Date | Author | Change Type | Description |
|---|---|---|---|---|
| 1.0 | 2026-02-08 | Michael + Claude | Initial | Basic Phase 0 readme |
| 2.0 | 2026-02-12 | The Chronicler | Rewrite | Complete rewrite reflecting current state (8 services, 6 servers, 12 game servers). Updated repo structure. Applied FFG-STD-001. |